433 karma · joined August 12, 2020
> Hey Siri, please play Emerald Rush, by Jon Hopkins on Youtube Music.
> Sorry, you'll need to continue in Youtube Music.
Then yes - I want AI on my phone
No doubt the recipient will also be using some form of AI summarization that strips away all that added "polish" - making the whole exercise entirely redundant!
It just feels absurd.
Are there actionable consequences if these numbers get too high? If they're merely published, as a parent, I would see high numbers as a positive signal if anything...
I'm thankful to know that when its my time to go, I'll have the choice to skip enduring several days of torture should I wish.
> This approach is good for now. But, it will limit you later. Your code will quickly get out of control.
Will it? If we need to be able to “delete via X”, it sure feels more maintainable to have this feature supported via an explicit, named method vs. inlining it as an anonymous closure (as recommended by the “balanced” solution).
It is a query builder (not an ORM), that (ab)-uses the Typescript type system to give you full type safety, intellisense, autocomplete etc.
Crucially it doesn’t require any build/compile step for your queries which is fantastic.
Is this a dumb take?
No such luxury is granted to the driver using FSD who has just collided with another vehicle.
Thus I would've expected the radius of the black hole to be necessarily smaller than the dimensions of the butter cube.
However, I now realize my mistake - in examples like squashing mount Everest or earth or a neutron star into a black hole, we're starting with masses that are stable/in equilibrium. This would not be the case for a cubic light year of butter!
Further, it looks like the radius is directly proportional to the mass. Given that mass grows cubic with respect to dimension, it's expected the radius of the black hole would eventually outgrow the cube of butter if made sufficiently large...
Instead of having to type "poetry shell" to activate the virtualenv, I use a tool called direnv that automatically modifies envars when you enter a directory - undoing the changes when you leave.
In my direnv config (.envrc) for the directory I write:
PATH_add .venv/bin
To add all the virtualenv executables to PATH. Now I can just call "python/pip" directly and never have to worry if I'm inside my virtualenv or not.N.B. for this you need to update poetry config to ensure virtualenvs are placed in the project directory vs. the default centralised location
Its only after I bought it (and the free trial expired) that I discovered that an additional subscription is required to use the integrated "cooking recipe" service that guides you through cooking various dishes - insanely cheeky given how much it cost!
To top it off, I'm constantly nagged to connect the thing to WiFi so it can update god-knows-what. Never. Again.
In my head, this completely decapitates scalping as a business. Why can't this also be applied in other sectors (i.e. restaurant reservations)
Have you heard of Factorio :)
If I search for "foo.io", it tells me that "foo.io.io" is available
The final straw for me was discovering that vscode automatically updates packages and imports when moving files around a java project - something that doesn't seem possible in neovim despite hours of research and lua tinkering.
Doesn't federation require admins of both instances to agree to federate?
If so, I could imagine it not scaling for larger instances that could receive 100+ federation requests a day.
Further, you would have to repeat this step each time to encountered a new instance you wished to participate on.
Is my understanding of the federation process correct or have I totally missed the mark? :D
I was toying with an idea/protocol where:
1. You add a TXT/CNAME that points to a trusted "authentication provider".
2. When you try and login to a website that supports the protocol, it checks the DNS record and redirects you to your provider.
3. You then "prove" that you own the domain to the provider - how this is done would be specific to each provider, but one possible method could be by providing a signed message that can be verified vs. a public key stored in a DNS record.
4. The provider redirects you back to the original website with a token.
5. Finally the original website consumes this token by sending it in a request to the provider. The response contains the domain as confirmation of the user's identity.
This approach removes the need for self-hosting as users can point and setup their names with third party providers.
Users can also trivially switch to a different/self-hosted provider by changing the CNAME.
Communities could also allow direct registration by hosting their own provider instance and pointing a wildcard subdomain at it: (i.e. *.users.ycombinator.com).
Users could then sign up to said provider using traditional email/password and claim a single subdomain: (i.e. tlonny.users.ycombinator.com)
Thoughts?
God help whoever is on trial if you're on the jury!