You are overlooking the idle power-consumption. A 7600 basically idles at 5W or so (and turns off all fans). Now think about how many hours you surf the web etc. with your PC Vs. actual gaming and you can see that this makes a big difference.

Depends… its a very capable 1080p card with extremely good power efficiency.

There is the overclocked “xt” version that is generally considerd bad value as it loses the power efficiency aspect and costs significantly more for only little extra performance.

Dunno, realisticly speaking it is a slightly cheaper 7600, hardly a market shake-up.

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.

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.

OnlyOffice has good mobile apps.

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.

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.

Unless they have an active IT department that is already hosting various websites for them, it is probably better to show them some hosted offer like this: https://masto.host/

As for your questions:

1. Medium difficulty as far as self-hosting goes. Mastodon is a Ruby on Rails app.
2. Really depends on the number of users etc.
3. See no. 2. a few hundred $ or so.
4. As others have mentioned, let them make an account on an existing server first, it can be migrated to your own server later.

Not really what you are asking for, but I found the combination of KaraDAV and Filestash to be a great alternative to Nextcloud, and much more stable for basic use.

As for Owncloud… I am skeptical of the company behind them ever since they split off into them and Nextcloud. Probably better to avoid, regardless of what you think of Nextcloud.

If you need it you will find it, and if you don’t, maybe it is unncessary clutter in your life that would be better to get rid off in a yard sale asap?