I ran it some years ago, and over all it wasn’t bad.

The UI is a bit old fashioned and some of the built in plugins seem pretty useless, but the webdav/carddav/caldav integration is nice.

Nomadic identity also works fine, but if you are selfhosting it there will be probably not much use for it.

Due to checksum based auto-correction ZFS and btrfs (in raid1) are actually less sensitive to data-corruption due to non-ECC ram.

This is a common setup for WiFi routers, where the idea is that most traffic will be on WiFi.

I disagree, and Gmail and Facebook do engage in censorship by hiding stuff the advertisers that pay for it don’t want you to see or be themselves associated with. That’s not even close to what moderation is and confusing the two things as “just two perspectives” is not helpful at all, as you end up justifying censorship through that.

I think you (and the Nostr people as well) are just muddling terms here. Censorship is about an external 3rd party (usually the Government) preventing you from seeing things you are potentially interested in, not (as in the case of Lemmy) your service provider and their trusted moderators helping you curate your social media experience. If you are unhappy with the moderation you can easily switch to another instance and use other communities.

If Lemmy isn’t meeting your needs, why not go back to Reddit? /s

lol, what? A project migrating away from Codeberg to Github? That’s a first I think, and also stupid.

It nearly certainly happened to you, but you are simply not aware as filesystems like ext4 are completely oblivious to it happening and for example larger video formats are relatively robust to small file corruptions.

And no, this doesn’t only happen due to random bit flips. There are many reasons for files becoming corrupted and it often happens on older drives that are nearing the end of their life-span and good management of such errors can expand the secure use of older drives significantly. And it can also help mitigate the use of non-ECC memory to some extend.

Edit: And my comment regarding mdadm Raid5 was about it requiring equal sized drives and not being able to shrink or expand the size and number of drives on the fly, like it is possible with btrfs raids.

One of the main features of file systems like btrfs or ZFS is to store a checksum of each file and allow you to compare that to the current file to notice files becoming corrupted. With a single drive all btrfs can do then is to inform you that the checksum doesn’t match to the file any longer and that it is thus likely corrupted, but on a btrfs raid it can look at one of the still correct duplicates and heal the file from that.

IMHO the little extra space from mdadm RAID5 is not worth the much reduced flexibility in future drive composition compared to a native btrfs raid1.

Btrfs on a single storage prevents it from doing auto correction via checksums. I would get rid of the raid5 and do a btrfs raid1 out of these devices. Makes it also easier to swap out devices or expand the raid as btrfs supports arbitrary sizes.

Storage space and bandwidth, as well as compute for re-coding lower resolution versions (although you can do that on another machine these days).

A cheap VPS will probably be insufficient rather soon, but something around 50€ a month should do it for quite a while.

OnlyOffice has good mobile apps.

The OG Lemmy meme is shower heads.

I am using btrfs on raid1 for a few years now and no major issue.

It’s a bit annoying that a system with a degraded raid doesn’t boot up without manual intervention though.

Also, not sure why but I recently broke a system installation on btrfs by taking out the drive and accessing it (and writing to it) from another PC via an USB adapter. But I guess that is not a common scenario.

Nuclear launch detected.

https://joinjabber.org/tutorials/service/unifiedpush/

It does solve my problem in the sense that right now I need to configure each subdomain individually both in the OVH web-ui and then a second time on my firewall for the dyndns update. With a few dozen subdomains that is both annoying and easy to mess up accidentally.

If I can manage everything from env parameters in a single location that saves me a lot of hassle.

Cool. I am currently using the OVH dyndns option and it is a bit annoying that you have to update each sub-domain individually and can’t just tell OVH to update all subdomains to the same new IP via a wildcard.

Is that something your script could do?

Also it seems like the OVH dyndns API currently only does either IPv4 or IPv6 but not both the same time.

Edit: Ah I see you plan to allow creating sub-domains through it. I guess that would indirectly solve my issue as well.

An the Syncserver still runs on Python2 with multiple known vulnerabilities.

There is a new Syncserver written in Rust, but it seems in continous half finished state or so.

Some WebDAV server, can be Nextcloud but actually something more lightweight is better.

Also a XMPP server is very nice to have. Even if you don’t have many contacts on it (yet), it works very well has a notification service and can even be extended to act as a Unified Push distributor.