Hi @Inga_Saulite_LV77! Opening an account on W helps us diversify our presence on social media platforms and reach out to as many Europeans as possible. We also welcome the development of European social media platforms. Opening an account on a new platform does not exempt it from its obligation to comply with EU legislation.
I cannot wait to also have one of the Czech Ada & #Zangemann books in my hands 🤗 🥰 Big thank you to Tomáš Starý, @mirek , Radek Vokál, and others whom I first met at #devconf who made that possible! 👏
We have taken important steps to combat hate speech through strong legal protections and digital safeguards, including:
🔹 The European Convention on Human Rights
🔹 The Digital Services Act, requiring platforms to quickly remove illegal hate speech
🔹 Criminal laws banning incitement to hatred
By choosing respect over division and facts over prejudice, we can help build a safer, more inclusive society for all.
And to emphasize this: nothing of this operates on the VFS level, it operates on the btrfs level and block level instead. Copying in files and directories is 1990s shit. Not how a modern image based OSes should work.
Once you want to migrate to the internal disk, we just tell btrfs to swap out the backing device of the btrfs, from the zram device to a block device backed by the internal disk. (and we also tell dm-verity to switch is backing of /usr/ too, once we copied it over).
That's really all there is.
During the entire runtime there's only a single btrfs file system, it just has initially one backing device, then two (while streaming over), and then one again.
@agowa338 @gwen i don't understand where the confusion is, but generally, in modern immutable OSes one tries to separate mutable state from immutable OS resources. The former sits in a file system such as btrfs. The latter in a verity protected erofs or so. When booting a fresh instance you take the erofs, mount it to /usr/ into an empty btrfs, and boot up. In the live installer case, that btrfs can be backed by zram. So you will have the mutable part of the OS run off RAM, and the immutable…
Cum să cureți caserolele din plastic îngălbenite folosind ingrediente din bucătărie - Oțetul alb dizolvă petele galbene din recipientele de plastic. Toarnă oțet și apă în proporții egale până acoperă zona îngălbenită. Lasă caserola la înmuiat peste noapte. A doua zi, clătește bine. Oțetul elimină pigmentii și readuce plasticului culoarea originală.
I think that you hit the nail on the head there. You offer up a wonderful buffet. A smorgasbord of delights.
The fact that some prefer to nibble solely on your baps, eschewing everything else, means everyone can enjoy what you do, in a way that works for them.
(And I *do* enjoy what you write, even if I am a plaintext using heathen.)
@flotmjor938382 Hey! So our team has said that our rss feed contains title, description/summary and the post url.
If you use a feed reader that is constrained to the actual rss content, then this is all you will see. Many (most?) rss readers we know can follow the post url and fetch the full post on demand. Some can do it automatically.
@agowa338 no, why would it? it's an in-memory file system, it does not persist across reboots or between systems. The btrfs on it is freshly formatted after the zram device is allocated.
@agowa338 btrfs device replacement is a btrfs native feature. It knows how to invalidate the old device to avoid identifier clashes. And the old device only existed in RAM anyway (i.e. backed by zram0), so once that device is destroyed there's no trace kept around that the backing device of the btrfs fs once upon a time wasn't the internal hard disk.
