Good.

The script appears to be missing the #! line. Without that, it is unclear which interpreter should be used for executing the script.

or a domain with a random string of characters so no one could reasonably guess it? Does it matter?

That does not work. As soon as you get SSL certificates, expect the domain name to be public knowledge, especially with Let’s Encrypt and all other certificate authorities with transparency logs. As a general rule, don’t rely on something to be hidden from others as a security measure.

When hosting this locally, I don’t see how 200 GB is much of an issue. Storage is so cheap these days, if you want to host it locally, just buy a 256 GB SSD just for that data for $20. Anyway, you were asking for a mirror, to which I replied with the information about the ZIM files. I don’t really understand the issue. Stackoverflow just isn’t that small, there is not much you can do about that.

I think it’d take a few hours to setup even a smaller copy of SO, which isn’t ideal for answering a quick question.

The download? Maybe, depends on your Internet connection’s speed. Actually serving it as a website certainly doesn’t take hours. It is rather a matter of seconds.

Then I don’t understand what your point is. A CPU on its own without a system isn’t of any use. Since there were no motherboards allowing you to use that much RAM, the point about the CPU supporting it is moot as far as I am concerned.

Of course they aren’t small, but they are probably as small as it gets, since they are pretty efficiently compressed. I am not sure what you mean by

it’s not a straightforward operation for even the average developer or systems engineer to restore these into a working format

since it is really trivial to use them. Just load them with Kiwix and serve them as a website. It doesn’t get much easier than that.

While technically true, the P4 did support PAE, in reality you couldn’t really make use of it on consumer hardware for most of its lifetime. No ordinary socket 478 mainboard with DDR1 memory supported more than 4 GB of RAM. With socket 775 more RAM was possible, but that socket is “only” ~20 years old.

Besides that, there were other even newer systems that supported only 4 GB of RAM, like some Intel Atom mainboards with a single DDR2 socket. Same with Via C3 mainboards.

You can download pretty much all of stackoverflow as ZIM files for self-hosting.

Yes, there is not much going on on this board, but since those trigger boards with USB-PD functionality are so cheap these days, it should have been possible to add such a trigger chip. If you wanted to go the really fancy route you could even use PPS and allow for pretty much arbitrary voltages.

Missed opportunity there, not being able to select all the other available USB-PD voltages. Not every circuit runs on 3.3 or 5 V.

I’m using a DuckDNS domain with caddy as reverse proxy, but it appears that the domain is defaulting to port 80 no matter how I set up the config. I can’t specify a port number in DuckDNS as far as I can tell.

A domain or DNS in general has nothing to do with ports. DNS is primarily used so that you don’t have to remember IP addresses.

kWh is a unit of power consumed. It doesn’t say anything about time and you can’t assume any time period. That wouldn’t make any sense. If you want to say how much power a device consumes, just state how many watts (W) it draws.

I understand their reasoning behind this, but I am not sure, this is such a good idea. Imagine Letsencrypt having technical issues or getting DDoS’d. If the certificates are valid for 90 days and are typically renewed well in advance, no real problem arises, but with only 6 days in total, you really can’t renew them all that much in advance, so this risk of lots of sites having expired certificates in such a situation appears quite large to me.

Ok, that endoflife.date site apparently isn’t quite up-to-date then. But even still, Android 14 was released in October 2023 and as far as I can tell, Fairphone released their Android 14 update only in July 2024. I’m not saying Fairphone’s update policy is terrible or anything. It certainly is better than that of many other vendors, but if you want updates as quickly as possible, you are probably better of with a Pixel phone. Of course repairability is an entirely different matter.

Absolutely, security updates are much more important than feature updates. Upgrading to newer Android versions is mostly useful to have access to newer Android APIs (apps eventually will require newer versions, although that usually takes quite a while). Another benefit of newer Android versions might be added security features.

Yes, there are multiple reasons, but that security chip was very important to them. An easy way to install the OS was also quite essential.

Samsung’s update policy for their lower end models is pretty atrocious. While on paper they offer updates for a couple of years, it you look more closely, you’ll notice that the update intervals get larger and larger as time goes on. You might not get important updates for half a year. Sure, still better than not updates at all, but a pretty awful policy for security updates.

Fairphone is actually worse than Google when it comes to updates. Even their flagship phone is still on Android 13. Even the Pixel 6 runs Android 15 at this point and with this news it is guaranteed to get at least Android 17. Google has always been offering 5 years of support for the Pixel 6 and 7 series. What they didn’t promise until this announcement was additional feature/OS upgrades, but when it comes to that they were already ahead of Fairphone.

When it comes to alternative OSes, Google actually makes it very easy to install them. That’s one reason why GrapheneOS and the likes chose Pixel phones as their primarily supported phones.

For the Pixel 6 and 7 series Google has promised 5 years of security updates right from the beginning. What’s new here is that they now also offer feature and OS upgrades for that same time period. Certainly nice to have, but not essential.

I would prefer more LAN ports as well, but how does that relate to what I said? I never said they intended to build or should build a device that fits all use-cases.