I bet all the certificate metadata shown in the „View a certificate“ popup window is vulnerable to cross-site scripting. Back then you probably wouldn’t get a <script> tag through a CA's review process and I found such a problem in Netscape's image „About page“ popup.

If it were vulnerable to XSS, why would you even want it properly signed by a CA? People almost never inspect the certificates of working websites, the only time they might look at it is when it fails validation.

I actually do like to view certificates of working sites, because it can be interesting to see what's listed in the Subject Alternative Names field. It can lead to some interesting observations about what sites are linked.

Netscape of this era predates the Subject Alternative Name :)

They already added indirect addressing (see https://github.com/adriancable/eternal/blob/main/docs/machin...) to make it faster.

Or even fixing the "navigating complex browser settings" issue. They control the freaking UI yet still use that as an excuse to build something else instead. Pretty hilarious.

I'm took a brief look and left confused. The list implementation seems completely bog standard with no special code for synchronization whatsoever. I don't see any counter and the rseq syscall seems unused except for feature detection. I don't think that's a viable replacement for any low level code.

The low level interface is documented at https://github.com/compudj/librseq/blob/master/include/rseq/..., the list is just an internal implementation detail.

The syscall these days is invoked by libc not the program; libc provides access to some symbols that let the program execute rseqs as well.

I guess "Diskless" was defined by the same people that invented the term "Serverless"? That Pi is still using an SD card to boot from.

A Pi with Ethernet can truly boot diskless via TFTP. And later Pi4 and Pi5 can even boot directly from the internet by getting their initial "boot.img" FAT partition via HTTP from anywhere. That would be diskless.

what makes that truly diskless? that's still getting the bytes from a disk somewhere

i think if the disk is not necessary for the whole runtime after boot, that's fair to call diskless

except in RAM based OS the page size and computation resources reduce significantly as OS is using the same memory to run instead of reading from disk and eating up critical memory area for applications, only thing in between a full crash and OS is the swap storage, macOS and Windows would never be even able to achieve this it is possible only due to Linux/BSD and it's level of optimization.

a better way would be to boot via nvme SSD, ethernet boot has a dependency of network, what if you need to debug when network is down or debug the errors/bugs network itself ?

Not sure if I understand what you’re trying to say, but Hetzner's Console works just like that too.

I personally find Hetzner's Console even better than DigitalOcean's one, especially since DigitalOcean now looks like three slightly different consoles depending on which page you're in. It feels like they've been migrating to a new system, but they haven't finished it yet.

A few friends and me use bedrock in a similar manner to push the rules on a faction PvP (player-vs-player) server 10 years ago: Basically a faction was a group of players working together on their base. You could claim land and a base on it was then protected from modification by outside players as long as players from your faction didn't die too often. We didn't really participate in PvP (we sucked :-} ), basically never died but did other interesting redstone stuff like vending machines, etc. But other factions did and they were always at risk of becoming raidable as a result of dying too often. Once a base was raidable is was almost always immediately completely destroyed and stripped of anything remotely valuable.

So we figured we might host one of those faction within our claimed land. As long as they store all valuable within our secure base, the fact that their claimed land becomes raidable doesn't really matter. Claimed land had to be at least one block apart from each other. So we had to find a bedrock tunnel: On their claimed land there needed to be free space within the bedrock level to get down to z=-63. Then on the single unclaimable block between our bases we needed bedrock on z=-61 and bedrock on -62/-63 on both sides. Then on our claimed land we again needed a way to get up from z=-63. Basically a single block long fully bedrock-enclosed tunnel. Took a while to find that, but we managed to set it up and caused quite a stir with other players and the server admins once our hosted faction got raidable without consequences :-)

Here's a project that also does this to ensure cycle-accuracy for their emulator: https://github.com/dbalsom/arduinoX86

Flight Simulator uses WASM.

Yep. A Pi 1 can almost play 1080p60 with a proper zero-copy decoding setup. Pi 2 and beyond have no issue with that. As you said: The Pi5 has enough CPU power, so even the H264 decoding itself now uses software as it no longer has a hardware decoder. Oh well.