Haven’t used it yet, but I’ve been researching authentik for my own SSO.

Oh, judicial duels have always been bad, tending to favor the wealthy who can afford training. The pistol duel was once considered egalitarian because you were just as likely to miss your opponent regardless of how much you trained. For most of the 20th century (until the 90s) Uruguay had legalized dueling. It was mostly used by politicians and the powerful to muder journalists and lawyers who “defamed” them.

But if we are already living in a period where the rich act with impunity anyway, I want a world where there’s a nonzero chance that we get to watch Elon Musk take an estoc to the face because of a twitter argument.

Grand journeys to far off lands. The kind of journey where someone who is “exotic” and personable can make a life for themselves by being the court foreigner.

Also: Judicial duels. They are unjust, unethical, and unproductive, but damn if I don’t want to see white collar criminals have to fight the selected champion of all the folks they ripped off. Of course, being a billionaire would probably buy you a pretty good champion yourself, so we’d also have to bring back old concepts of honor to compel them to represent themselves.

BTRFS should be stable in the case of power loss. That is to say, it ought to recover to a valid state. I believe the only unstable modes are RAID 5/6.

I’d recommend BTRFS in RAID1 mode over mdadm RAID1 + ext4. You get checksumming and scrubs to detect drive failures and data corruptions. You also have snapshotting, in case you’re prone to the occasional fat-fingered rm -rf.

For backup, maybe a blu-ray drive? I think you would want something that can withstand the salty environment, and maybe resist water. Thing is, even with BDXL discs, you only get a capacity of 100GiB each, so that’s a lot of disks.

What about an offsite backup? Your media library could live ashore (in a server at a friend’s house). You issue commands from your boat to download media, and then sync those files to your boat when it’s done. If you really need to recover from the backup, have your friend clone a disk and mail it to you.

Do you even need a backup? Would data redundancy be enough? Sure if your boat catches fire and sinks, your movies are gone, but that’s probably the least of your problems. If you just want to make sure that the salt and water doesn’t destroy your data, how about:

1. A multi-disk filesystem which can tolerate at least 1 failure
2. Regular utilities scanning for failure. BTRFS scrubs, for example.
3. Backup fresh disks kept in a salt and water resistant container (original sealed packaging), to swap any failing disk, and replicate data from any good drives remaining.
4. Documentation/practice to perform the aforementioned disk replacement, so you’re not googling manpages at sea.

This would probably be cheapest and have the least complexity.

I recommend that if you go with a home carbonation system, that you look for one you hack your own CO2 refills for.

Some people buy a CO2 tank and regulator, then hook it straight up to their machine. I have a large CO2 tank in the basement with an adapter to refill the individual proprietary canisters. I got the tank free from a friend, and then paid 30 USD to have it certified (good for 10 years) and 30 USD to have it recharged with beverege-grade CO2. Buying an adapter was 40 USD

My large tank holds ~5kg of CO2, and it costs about 17 USD to officially refill one of the small canisters with 500g of CO2. Thus, even if I didn’t get the tank for free (new ones cost ~120 USD), the large tank would still pay for itself after filling it one time.

I wouldn’t trust anything like that to the open internet. It would be better to access the system over a VPN when you’re outside the network.

Barony is fun as hell. Engine is FOSS, but the default game assets require purchase.

You’ve laid out one potential development cycle: FOSS from the get-go, and open collaboration welcome.

However, that’s not the only way that a FOSS game might be developed. The code could be freely licensed, but the upstream developers refuse to accept outside patches. In that case, there’s one “original” and then if you don’t like it, build your fork.

Alternatively, a game could be developed entirely in-house under proprietary licenses, and then only made FOSS upon commercial release. Contributor patches could improve the project, but conception of the game would be entirely the domain of its original developers.

How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like “Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?”

In a real aviation design scenario, they want to minimize the bullshit tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that’s managed by the flight computer.

You are not in the sudoers file. This incident has been reported and your account suspended.

VNC is a security hole unless you route it through an SSH tunnel. If you’re managing a docker container for jellyfin there’s not much UI work to be done anyway.

Neither shrooming, nor dismissing. It just reminded me of that school of thought. I don’t know any anarchist theory, so I assume it’s evolved since the days of the Paris commune.

So we’re back to “If we all ignore the government, it will wither away” type anarchism?

But the emperor isn’t paying for this circus. The plebs are. The Superbowl is not a loss-leader to keep the poors from rising up, it’s a profitable enterprise that keeps generating wealth. The money is what keeps it going, not some plan to keep people down.

I fucking wish it were bread and circuses. Except instead of bread I’ll accept healthcare, and instead of circuses we get cable news.

I guess it would depend on whether or not the project spawns a dedicated community that lasts for a long time. Without a wide pool of knowledgeable contributors, I think it would be hard for an original team to both support the one design while also developing the next iteration.

Not to bring it up as a whipping boy, but let’s take the case of Wayland, which is “just” a software protocol. It was started back in 2008, and is still under active development. As more projects support it, more edge cases are coming up, which is why new features are added to the protocol all the time. In those 15 years, they’ve had to adjust to technologies that didn’t exist back in 2008, like widespread adoption of 4k HDR displays, or Vulkan. Now imagine that, but with every aspect of a computer. In 2008, DDR3 RAM was just a year old. Today we’re on DDR5 and you (probably) can’t buy a new machine that takes DDR3. PCIE 2 was the latest shit in 2007. Now I see that PCIE 7 is planned for next year.

A global corporation can support old products while also developing new technologies because they have unfathomable labor and capital at their beck and call.

I think that free software can keep up with proprietary offerings because the barrier to entry is relatively low. You just need free time and a source control client. I think it would be different if your project toolchain involved literal tools that cost millions of dollars.

I think because such an undertaking would require a wide breadth of extremely specialized knowledge. It would require intense coordination of many experts to work together over many years, all to design something that:

1. Will eventually be obsolete within a few years
2. Is outside the realm of replicability for individuals (I never heard of anyone with a nanometer-scale photolithography room in their house)

Item 1 is OK for hobbyists, who might value open source over new-ness, but item 2 all but guarantees that only big corporations can actually get involved. They don’t care about free and open source. They just want a computing platform that their engineers can develop a product for. As long as there’s enough documentation for their goals, open source is irrelevant.

The power of modern computing comes partly in how it enables abstraction. You don’t need to understand the physics of electrons through a transistor to write a video game. Overall, the open source community has generally converged on the idea that abstracting away the really hard stuff is an acceptable tradeoff.

Caps lock is great for rebinding to Ctrl

It’s common in communities where rigid adherence to a set of beliefs is necessary to enforce cohesion. It’s commonly used to avoid engagement with “Facts U Dislike” (haha) by terminating all meaningful discussion.

Part of a flat earth forum and you’re posting an experiment you performed that suggests the earth is round? You’re spreading FUD that should be ignored.

Posting on a crypto shitcoins discord about how this kinda looks like a scam and maybe it’s not a good investment? That’s also FUD. You’re just mad that everyone else is going to be rich.

The stop button problem is not yet solved. An AGI would need a the right level of “corrigability”: a willingness allow humans to stop it when undertaking incorrect behavior.

An AGI that’s incorrigible might take steps to prevent itself being shut off, which might include lying to its owners about its own goals/internal state, or taking physical action against an attempt to disable it (assuming it can).

An AGI that’s overly corrigible might end up making an association “It’s good when humans stop me from doing something wrong. I want to maximize goodness. Therefore, the simplest way to achieve a lot of good quickly is to do the wrong thing, tricking humans into turning me off all the time”. Not necessarily harmful, but certainly useless.

https://www.youtube.com/watch?v=3TYT1QfdfsM