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.

Good idea, but not sure why there is a limit of 4 days though. As if the weather will stop being bad when four days are reached 🤦‍♂️

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.

Apple also runs an ad business these days and their devices collect more types of data than stock Android does. And contrary to many Android phones there is very little you can do against that in Apple devices.

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.

The default Android on them is pretty standard including Google Play services, so it is not great in regards to privacy (but could be worse, like a Apple or so).

But for most of their models you can find good alternative Android roms or even mobile Linux distributions like PostmarketOS.

“Special Military Operation” is the current popular term I believe /s

Starlink uses CGNAT, so that is not possible since the public IP is shared between multiple subscribers.

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.

Signal as a centralized meta-data honeypot.

Instance admins can “purge” it, but it is only local to that specific instance.