jj4211

Been starting to see more randomly picky apps. Based on vintage and rooted device.

Uninstalled the FedEx app, since every time I tapped on a tracking number, it would divert to the app which would promptly shame me for having a rooted device and refuse to run.

So I saw that my car offered up all sorts of useful diagnostic information for self diagnosing stuff. Was very excited and went to look at it for a generic fault without having to get software to tell me what the fault is. I thought "it's stupid it has fully functional computer display yet tells me basically "contact a dealer, but it's safe to drive" instead of what the problem is. Then I find out that because I'm in the USA, the company keeps it to themselves...

So if they see value in treating regions differently, they will absolutely go out of their way to screw over the regions that will let them.

Heh, the dryer stopped working at home and my spouse was bracing to buy a new one. So nice to break out the multimeter, find the issue, and 10 dollar part later, good as new.

Think of all the waste avoided by repairing a tiny part in a gigantic appliance.

Depends on how the network services are designed/configured.

If the service is allowed to just bind '::', then generally, sure, start it up and more proper networking bringup can happen asynchronously.

But folks often have it bind a specific address/interface, in which case those binds will error and cause the service to error because it was asked to bind to something it could not. This is the use case I think the online target is designed to take the race conditions out of. It's not that the service is not really useful without networking, it's that the service will exit with error if the networking isn't exactly as expected.

Of course, in this world of genericizing things around the worst cases, they end up blocking everything just in case, because they have no idea of the user has done something like make the service only work through one interface.

What I would call out systemd for is that it can make it difficult to know precisely what thing it isn't happy with. Abstracting a mishbehaving process to "user session" when it could call out the offending process by name.

Similarly, when it's trying to decide the network is 'online', and by all appearances the network interface was configured, but systemd isn't so sure, sometimes it's hard to tell why.

A lot of the bad experience with Windows similarly could be attributed to something workable, but the design obfuscates the underlying behavior. Systemd has been bringing some of that sentiment over, and that can be more aggravating.

The good old 'network-online' can just be a ton of fun. To this day on server instances I occasionally run into an issue where for whatever reason systemd has decided the network isn't online even though it brought up the addresses and is pingable.

Sometimes this just happens with systemd, it wants to manage every thing as a session and sometimes things running in the session don't exit like systemd expects.

Also, sometimes logging into a headless ssh session takes quite a while, because systemd is not super responsive to setting up the user session and ssh blocks waiting for that to happen.

So I have now seen it . It did not pop up, I had to go into apps and find the spider man app and click on it.

Pretty stupid waste of time, but not on startup or anything.

This along with the changes to de-emphasize things like watch lists or even "continue watching" is basically the providers seeing how much they can influence users to watch what the provider wants instead of trying to cater to the users. If they find that people rarely navigate away from whatever 'top 10' or 'for you' suggestions, well, that means they have a great deal of freedom to only provide what is convenient for them and still get most of their revenue.

Sure, but based on experience, when the scalp is just sporadically putting hair out there, it's pretty much always better to go all-in and shave it. Trying to make the most of remaining bits of hair is a lost cause. If you have some reasonable parts of your scalp still putting out volume, then the hair can look ok as long as it doesn't grow out too much.

Well, there's livelihood and work, and so far no one has exactly inspired confidence that the current labor class will receive a livelihood. We've let systems solidify that basically demand that the labor class have some semblance of leverage to participate in the benefits. So far the practical result has been that the hypothetical scenario erases that leverage, while avoiding any concessions that may win over the people that would be screwed over. It's nice to hand wave and say "some new system", but without more concrete things to look at, there is the risk of "well, let's remove the labor leverage and just assume that the utopian outcome results instead of the dystopian".

One thing that concerns me is that a common short story held up as an example of awesome utopia brought on by post-scarity due to AI is "Manna". The plight of the dystopian half is very plausible, but the "utopian" half has a lot of problems in mechanism of how it happened and issues when "realized". If even in fiction we can't make a convincing narrative that lands in an unambiguous utopia, then my hopes for reality is pretty low.

So I guess in short, I agree with your sentiment, but too pessimistic to see the upside being realized and afraid that the optimisim around the upside results in rationalizing the downsides.

The toxic aspect generally comes from the consequences of pursuing ambition by undermining others in a competitive context. If, hypothetically, the competitive pressure is off, then "ambition" is not nearly as likely to have negative consequences.

Here the person was saying we really need to actually put our minds to use, and that's not really likely to be the 'toxic ambition' you fear.