1. It's very common, especially in certain ecosystems like Python, for the system to depend on old versions of things in such a way that updating to modern versions will break your entire system, while at the same time you want to run something at the user level that depends on a newer version. The solutions to this are usually ecosystem specific and often annoying to use for someone who just wants to run a program (again a great example being Python venvs, which at this point have decades of tooling built up around trying to make it less annoying to deal with).

2. For "cattle" systems having everything installed at the system level is generally not too much of an issue, but for "pet" systems where the user might be experimenting with things it's really nice to be able to install stuff in a way that doesn't affect anything outside of your user account even if it's also available at the system level. The computers that I personally operate from on a daily basis tend to build up a lot of crap I used once over time and removing it without just backing up my stuff and nuking it all can be a major pain.

If the user gets the email and completes the validation, the email is valid. If they fucked up, they don't get the email and the account never gets created.

No one ever gets prevented from creating an account with a legitimate email address, as opposed to "opinionated validation" where that absolutely will happen. Speaking from years of experience having a .info domain which isn't even all that odd, and at one point using gmail-style + addresses regularly. "Opinionated validation" has forced me to use my .com domain without a plus dozens of times.

I know part of this is intentional, those who know they plan to sell your email addresses don't want you to use the plus addresses, but that doesn't make the advice to not filter addresses any less correct.

Not really, this is actually pretty easy. If such a device beacons and a trusted device is within range the trusted device can respond to the beacon and let it know it's nearby, then it just counts up if not. X number of beacons with no response, set the "not near my trusted device" flag. Some other device sees X number of beacons with that flag set while moving around, send alert to the user.

Flipper Zero has Bluetooth built in, that's how the phone app works.

I don't know how much control the apps have over it, but there were definitely Flipper apps to abuse the BLE auto-pairing feature of a lot of devices and spam popups to nearby phones.

Where are you seeing healthy forests or other "beautiful land" being destroyed for solar farms? There's plenty of low-yield farmland and other similar land that's already been denatured by industry out there, lots of which already has major transmission infrastructure nearby, beautiful land tends to be expensive, and clearing trees costs money. It just doesn't make sense to do something like that outside of isolated areas where there's no other choice.

Here in the midwestern US every single solar or wind farm I've seen has either been on active farmland, former farmland, or a corporate/university campus.

That's of course not to say some rogue agents haven't confiscated a few Flippers, especially after seeing hyperbolic media reports about them being magical evil hacker devices, but I have high confidence that there's no official policy to do so.

I guess that's true if you think of assembly as a more readable form of machine code, but from a practical sense I'd argue that assembly inherits the undefined behaviors of the architecture it represents and the implementations of that architecture it actually builds for.

IIRC the OG Xbox security was broken partially as a result of undefined behaviors in x86 where the AMD CPUs that were used in early development would crash or throw an error or something when execution reached the end of the memory space but the Intel CPU they switched to instead just rolled over and kept executing from 0.

There's one major reason to have higher expectations for autonomous systems (of all kinds, not just LLM-powered) than for humans, at least those intended to be deployed at scale, and that's the scale. If a human makes a mistake, has biases, or even intentionally breaks the rules the impact of their actions is limited by the nature of them being a human, where something like an autonomous driving system, a coding agent, etc. is intended to be deployed by the thousands, millions, or more and any problematic behaviors happen at that scale.

There are obviously millions of bad drivers out there, but every one of the human ones is bad in different ways. If Waymo pushes a bad update there could be tens of thousands of "drivers" that suddenly become bad in identical ways.

Humans also have the ability to learn from our mistakes. The ones you'd want to have working for you usually don't make the same one twice. LLMs are pretty good at making the same mistake repeatedly, even the simplest things like basic math or counting letters.

The x86-32 version (and hypothetically the never-complete PowerPC version), as I see it, exists (or would exist) for binary compatibility with legacy BeOS systems. The AMD64 version on the other hand is a hobby OS demonstrating a path not taken where personal computer operating systems remained separate from server operating systems.

Also, like others, these days I can do basically everything I need to do on a computer other than gaming as long as I have a browser that supports the modern web and a SSH client so Haiku is absolutely fully usable on the right hardware.

Pausing issuance immediately upon discovery of a compliance issue is the absolute correct response so as long as they do their followup appropriately there is absolutely zero risk of being distrusted.

This is a feature that some graphical desktops used to have back when 640x480 and 800x600 monitors were still common, the desktop resolution could be set independently of the display resolution, so you could have a larger framebuffer that your monitor presented a view in to. I recall some graphics drivers (Matrox for sure) added this to Windows 9x and called it "virtual desktop" and I know I've seen it on a few *nix platforms too.

I'd assume if the resolution adjustments work as expected below 1024x768 that whatever graphics driver OI is using in your VM only sees the virtual display as capable of 1024x768 at max and so it does this if directed to provide a larger desktop.

edit: apparently xrandr calls this "panning"

I worked "maintenance" at a local outlet mall back in college so I was that guy, and after the first couple of times it was just a matter of "this needs to be done, I'm the guy who does it" turning my brain off and getting the job done. I remember basically nothing from those evenings, I would just put my headphones on and mentally be somewhere else.

It was a shit job in a lot of ways, figuratively and literally, but at the same time I had amazing work/life balance. From the moment I clocked out until the next time I clocked in what happened at the outlet mall was not my problem in any way and I didn't have to think about it at all.

Trust is earned, it's built on reputations at the individual, corporate, and industry-wide levels. AWS has 20 years of reputation on which I can judge the value of their promises.

Not only has the LLM industry (it is not "AI" and never will be) absolutely not earned anything like that level of trust, the thing the technology has proven most effective at is in fact scamming. Making up something that looks/sounds convincing, especially if you aren't thinking too hard about it, is what they're best at. Combine that with a lot of money flying around and trust levels should be somewhere around "Elon Musk promises".

At this point there have been so many blatant examples of why you should never give a LLM "agent" control over production systems, but the allure of just giving some vague direction to a chatbot and telling it not to screw things up it just irresistible to some like Sideshow Bob stepping on rakes [1].

If everyone around you is whacking themselves in the face with the rake, and you know you can avoid it just by using your brain and not stepping on the rake, and avoid entirely by just keeping your rakes contained, but a rake vendor comes to you saying that instead they have built a new rake that they swear won't whack you in the face even if you leave it right in your walking path, do you trust them?

1: https://www.youtube.com/watch?v=ouau9SVVrBA

No, as it's supposed to be implemented a single internet-routable /64 is used per *network* and then most devices are expected to assign themselves a single address within that network using SLAAC.

ISPs are then expected to provide each connected *site* with at least a /56 and in some cases a /48 so the site's admins can then split that apart in to /64s for whatever networks they may have running at the site. That said, I'm on AT&T fiber and I am allocated a /60 instead, which IMO is still plenty for a home internet connection because even the most insane homelab setups are rarely going to need more than 16 subnets.

> So if I wanted to annoy GitHub, I could connect to them without ever using the same IP twice. Their response would have to be banning my /64, or possibly /56.

Well yeah, but it's not like it's exactly rocket science to implement any sorts of IP rate limiting or blocking at the subnet level instead of individual IP. For those purposes you can basically assume that a v6 /64 is equivalent to a v4 /32. A /56 is more or less comparable to /25 through /29 block assignments from a normal ISP, and a /48 is comparable to a /24 as the smallest network that can be advertised in the global routing tables.

The comparison in this case is to Hetzner's VPS offerings, which are probably less powerful than the average "old laptop" but have a significant advantage in terms of hardware reliability. It's still possible for the host running the VPS to have problems which result in a crash or the VM equivalent of a hard power off but the VM hosts and their underlying storage should be redundant such that the virtual hardware never fails.

That's not to say rebooting from a crash-consistent state will always work, you should always keep backups even with a high-quality VPS host, but the odds of recovering cleanly from a hardware problem are orders of magnitude better than an old laptop. For the sort of hobby project or personal tinker box that would be reasonable to host on a random laptop shoved in a rack you probably wouldn't even notice the downtime until you saw the event notification email your provider sends you.