This is what you get if you use silly generic terms as names for your chat protocol 🙄

Deckard will probably be a split unit: a lightweight headset with a small stationary unit for wireless streaming. That stationary unit will also work as a normal steam machine connected to a TV and will be on sale seperatly. (This is all speculation)

No, that divide isn’t political. Its about utilitarianism.

The side you are opposed to cares more about getting many people “good enough” privacy, than getting the best possible privacy for a few while alienating most other people.

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

Nice find indeed.

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.

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 an Apple device or so).

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

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.

Nuclear launch detected.

Should be no problem with Heroic Games Launcher then.

Signal as a centralized meta-data honeypot.

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

The people behind this are bitcoin shills.

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.