dividuum

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.

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.

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.

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

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 :-)

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.

bubblewrap is a lot more flexible: You can freely piece together the sandboxed filesystem environment from existing directories, tmpfs, files or data provided via a file descriptor. landrun, from what I understand only restricts what already exists. What is neat with landrun is the TCP port restrictions. This isn't possible with bubblewrap at the moment, although nothing really prevents bubblewrap from adding landlock support for those cases.

Not true. It's getting a constant stream of bugfixes. It's also not "stuck" on Lua 5.1, but is deliberately not following Lua's path, except for some backports. There's also a recent post about how a LuaJIT 3 might work.

I remember you could trivially circumvent that with „/lib/ld-linux.so <executable>“. Does that no longer work?

That seems like an implementation detail, not a fundamental design decision as it should be easy to change how packfiles are implemented. I'm not sure it would be an improvement though: it already only stores deltas for similar objects.