Maybe https://picocms.org/

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

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.

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.

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.

https://en.wikipedia.org/wiki/Caucasian_race

edit, delete, etc.

Can you do that with a letter once it is send? And the instance admin of the mirroring server can delete posts if that is legally required for some reason.

And how would that even work technically? Bulk import posts and spam other instances with mass updates? That would immediately detected as a spam-wave and blocked. And back dating technically new messages is also not exactly a great thing to allow.

Other implementations of nomadic identity like Hubzilla get around this by letting you run two accounts in parallel and syncing them from your main account, but they will also not back-port old messages before you linked up the secondary account.

Basically anyone with some experience with federated systems agrees that importing old messages in bulk on account migration will never happen, and I don’t really see an issue with that, since messages are not lost.

I don’t think that’s even desirable and also legally questionable. But anyways, these posts are not gone with an instance shutting down and thus I don’t really see a problem. You can always add a link to a mirrow of those old posts in your profile.

Content is mirrored on all federated instances and it is very rare for an instance to shut down without notice.

It’s super easy to migrate accounts on Mastodon. Even works fine to move an account from Mastodon to Akkoma for example.

Mbin is a fork that was startend to add some stuff the original Kbin dev didn’t like. These days it seems Kbin is dead though, so basically Mbin is the new Kbin.

Lemmy.world used to cost that much, but I think they downscaled a bit recently, or are at least planning to as the current growth of the userbase has slowed down.

I was actually surprised by that 150 figure when I first read it, as it is much cheaper than what the BlueSky documentation makes it sound.

It is certainly possible to collect that much in monthly donations, but then again… how do you build a loyal base of supporters for running a mostly hidden piece of infrastructure? People always complain about the instance focussed nature of the fediverse, but the ability to build communities around them and get people actually emotionally invested in their home instance is IMHO rather a strength of it. That is also why I am slightly sceptic of easy account migration tools, as it devalues the instance as yourhome base to a certain extend.