Maybe https://picocms.org/

But Hugo is fine, no need to use all the advanced features.

Some good ideas, and most of it wouldn’t even be expensive. It’s a bit sad how education bureaucracy kills most of such initiatives in my experience.

Works great with Akkoma as well.

It has pretty much stagnated in the English speaking part of the internet, and only saw a huge boost in popularity in Brazil recently (due to Twitter being newly banned there).

maybe try: https://github.com/Fancy-Mumble/FancyMumbleV2

CoreCtrl might also work.

https://www.twz.com/this-alien-looking-airship-design-used-a-propulsion-method-unlike-any-other

Hmm, this kind of stuff is usually a result of water acting as a solvent pulling salts and similar substances from a substrate and later evaporating, leaving the powder behind.

It is probably something that was used to treat the plywood or a combination of that with the zinc coating of the metal (zinc-sulfate?).

Edit: probably sodium-borate, as that seems to be prone to leaching from wood treated with it.

If I remember correctly, it needs KDE 6.x to offer the option to create a new fake screen as an output.

KDE doesn’t need hdmi/dp dummy plugs, you can just configure a fake output. Works fine with: https://deskreen.com

Huh, it was still working when I posted it one hour ago… unlucky I guess 🤷‍♂️

It is possible that people get access to your server while it is running via known or unkown software vulnerabilities, but that isn’t really the point… all I am saying is that if you host your server at home, it is unlikely that at-rest disk-encryption does you any good and it certainly doesn’t help to protect against illicit remote access.

What it does “help” is preventing you from remotely accessing your own server if it rebooted for some reason… and many other such footguns that you will experience sooner or later.

No the Nextcloud DB is not excrypted, but neither is your LUKS file system while the computer is running. Anyone getting access to the server while it is running, can access all the data unencrypted. For a server this is the much more likely scenario than for a laptop, which might get stolen while turned off.

At-rest disk encryption is useful for servers in co-location hosting, where a 3rd party might be able to pull a disk from the system, or if you are a large data-center that regularly discards old drives with customer data, and you want to ensure that no 3rd party can access that data from the discarded drives.

I would carefully think about what realistic threat scenario full disk encryptio protects you from.

On a server that runs 24/7 at-rest disk encryption usually helps very little, as it will be nearly always unencrypted. But it comes with significant footguns potentially locking you out of the system and even preventing you from accessing your data. IMHO in most cases and especially for beginners I would advise against it for a home based server.

Nextcloud runs fine via Podman. Stick with Fedora, cockpit and btrfs.

Btrbk is good for snapshots and automated backups.

If the 500gb is a NVMe drive then the database will benefit from the extra r/w speed.

Nginx is great for reverse-proxying. Dehydrated is the no-BS option to generate certs, but Certbot also works.

OVH gives you free dyndns and an email address with every domain you register, good option for self-hosting.

As written above we are still in the community consultation phase. So far there has been only positive feedback, so I guess it is likely that we will switch sometimes in the comming months.

https://snikket.org/ is the easy to configure XMPP server, but it still needs SSL certificates. But that’s fairly easy to do with Snikket AFAIK.

Or you could simply ask the Snikket developers to host a server for you for a small fee. If you are US or Canada based https://jmp.chat/ is also a great service, and it includes a free Snikket server as an add-on.

PSVR2 has eye-tracking no? I still hope for proper foveated rendering to arrive in SteamVR headsets.

That “weekend” trailer has unintended dystopian undertones…

There is also a login issue with our wiki, that we need to get around fixing. Sorry for the delay in tackling that issue, but various other things came up unexpectedly in recent weeks, so that had to be put on the back-burner.

This is fixed now, sorry for the long delay in getting that to work again.