xelamonster

Well this explains why every time I get payment autofill suggestions from Google it's a random one of four or five possible auth flows, and pulls from an arbitrary one of at least two separate data sources with different sets of cards saved...

I let my password manager handle it now.

I like NordVPN still. If there's any reason I shouldn't I'm all ears but haven't had an issue so far. I travel a lot and I definitely do feel better having my traffic routed through a VPN vs opening it up to whatever random entity happens to control the wifi I'm connected to, despite all the issues with them

Unless you were actively using port forwarding before it wouldn't be any different. If you need a VPN for your torrents, despite these faults I don't know of a better one myself. I use the Firefox VPN (which is Mullvad under the hood and it's worked at least as well if not better than any alternatives for me so far.

That's not really how biometric app login works here. Credentials are configured locally and used as an alternative to the existing login method. Nothing changes about how you login with other devices, you can still choose to use your username and password on the device with biometrics enabled even.

For some definitions of works. It's frustratingly inconsistent for me, very often it'll give me no suggestions on apps it's filled many times before and I have to go open it and manually copy out passwords.

It does but you need to run commands through uv to use it, I assume this means if you run bare python commands in the task runner or whatever mise will use the venv.

I'm not a fan of forcing single or double quotes because escape codes are such a pain to deal with and to me make things significantly harder to read than an inconsistent quoting style ever could.

Well what's more readable, .8675309 that is understood to have an implicit zero, or the parser giving up and unexpectedly making it a string? Maybe it's not your preference but I can't see any problem with making this more robust. The trailing one is strange to me but leaving off a leading zero isn't unusual at all for written numbers in my experience.

Ah cool, maybe I'll check it out someday. JVM isn't a huge part of my daily work though so I'm pretty happy having it managed the same way as everything else for now. I like the intuitive simplicity of a .tool-versions file in a repo that supports a huge variety of tools.

I tried to use the Find My Phone feature with my Samsung account a couple days ago. Log into Samsung with Google, on my friend's device as I've lost my phone, and Google says "we've sent a prompt to your phone to log in"... the phone that I'm trying to find. No alternative options, I just got frustrated and gave up and luckily found it on my own. Still not over how incredibly stupid that was.

This made me think I'd somehow not saved my MS password because it wouldn't show up if you searched "microsoft". I know you can combine them like the other comment mentioned but what an awful default experience.

It supports most OSes rather nicely, check the docs for a long list of config options. It creates a local package store and configures your user's path for it, each tool is managed with a custom plugin that IME works flawlessly and versions are handled better than anything else I've ever used. It's the only way I'll install Golang or NodeJS lately, and I had good luck with it for Java too.

Yep that's the issue, I'm just saying I'd rather have that problem than the one where I can't register a clean looking personal domain because every idea I have is already registered (with 95% of them leading to a parking page untouched for years except to pay the bill). Feels like we just need more names available and I don't see how else we could get them.

The implication that gTLDs are bad and new ones shouldn't be introduced because of this is a bit silly to me. The argument that they somehow have lower registration requirements makes no sense, .shop .top and .xyz registrations involve the exact same amount of verification as .com (none). Prices aren't really that different and plenty of gTLDs are more expensive than traditional ones.

Registering a domain is frustrating these days, too many already taken and a lot of them by squatters not even intending to use it. I'd love to see more options personally even if it makes it slightly easier to create a phishing domain. We need better tools than memorizing a domain name to deal with that anyways.

They don't differentiate. They just make it too expensive to be worth paying for the resources required to carry out a spam attack at any meaningful scale.

Interestingly enough I've had the opposite experience. If I'm having a nightmare, usually at some point I realize it's a dream, and from there I can almost always force myself to wake up immediately. It rarely happens for me in a regular dream but when it does I can start to control the scenario to some degree.

No? I mean I'm with you that it sounds like a really bad idea and would probably not end well, but laying on a table so someone can implant a device that handles it for you forever does sound a whole lot easier than having to actively balance your intakes for your entire life.

I totally understand the appeal, hell I'd do it myself if you could give me a guarantee, my problem with it is there is no guarantee and it's 99.9% likely to not actually be safe.

Yeah wow, I love that this is forever encoded into the standard now. A lovely tribute. It's always been one of the few CSS default colors I actually like too (alongside "cornflowerblue").

How does that mean anything to the people who need to be employed to continue living? We're not the ones with the ability to change this.

Makes sense, thanks! I first heard about crush syndrome from an episode of House, and IIRC it ended up being a cause of death so didn't exactly learn how to manage it. Though I want to say the woman there was pinned from the waist down, which I'd imagine complicates things.

So what does that actually look like in practice, lifting the piece of rubble an inch at a time? How slowly would you release a tourniquet in that situation?

You might just be convincing me to switch, I generally love docker and compose but the firewall thing still blows my mind and that there still just is not a solution.

My workaround has been to bind all docker port forwards to localhost and only ever expose them externally via reverse proxy. Which is annoying because that means I can't run the reverse proxy itself in docker.

This depends on your use case of course, compose autoscaling is maybe harder but I don't personally need that.

I migrated several services from Kubernetes to compose and couldn't be happier. K8s was a maintenance nightmare, constantly breaking in ways that were difficult to track down and unclear how to fix once you did. Compose configs are simple and readable with all the flexibility I need and I've literally never had an issue caused by the platform itself.

That's super interesting and I love the idea of physically destructive GC. But to me that calculation and tracking sounds a lot harder than simply fixing the leaks :)

This makes sense to me and other comments have covered why plenty well, but what does frustrate me is the constant insistence that nothing should ever be discussed in public and you must consult your own lawyer privately for every bit of basic information. That's just not realistic for the majority of people and even plenty of small businesses with how much lawyers cost.

I'm not sure where you got the idea my post was claiming taxis were superior in any way, I explicitly said Uber was better. Taxis weren't practical but they at least they existed. I have lived in cities that used to have taxis which were annoying and unreliable, but after Uber came and left there was literally no way at all to get from point A to point B without getting a ride from a friend.

Regardless I will admit I misread the issue stated in the article a bit and addressed that more here: https://news.ycombinator.com/item?id=42097052

I'm a bit unclear what you're trying to say re BHH or if that actually is a different reason. Totally fair point on Uber though, I didn't read that one closely enough, but I'll still argue that's unethical for a more relevant reason: surge pricing reinforces inequality by blocking less wealthy people from access to services while those who can afford it are unaffected. The distribution of who is able to use the service under heavy demand is massively skewed towards the class of people that most likely would be just fine without it while the ones most heavily impacted by a missed appointment or being late to work or whatever are the ones left out to dry.

I think I agree with you in this case, but I'm not so sure about a lot of the examples given in that linked article.

BHH Labs: pretty obvious to me it's ethically wrong to find the most desperate people around and pay them less than minimum wage to staff your event...

Uber: yes there was a need here, yes the experience offered by traditional taxis is awful and their service is strictly better where available, that really is not related to the ethical concerns I have with them. They're cheaper because they underpay drivers, and quite often they'll come into an area and drive out all the taxis then all but disappear themselves, leaving the town with zero practical transport options.

I agree, but I also appreciate this because missing map/filter/reduce is probably my biggest pain point when writing Go. Nested for loops and explicit filters are so ugly and hard to read, for me that alone undoes any of the appeal of the language's "simplicity".