Cleverson
DistroWatchWith some distribution projects starting to adapt age verification code, I wonder if people are now starting to realize why immutable filesystems are such a concern? Once a distro bakes user tracking code into the core image it's harder to get rid of it when dealing with an immutable operating system. With a writable filesystem the component can just be swapped out or recompiled.
Nicolás Danelón@distrowatch nah they won't care. We care about that because we are nix nerds :/
@nicolasdanelon Nix the package manager or *nix the family of operating systems? I am in favour either way.
@distrowatch hahaha the OS family ahah
Tokenizer@distrowatch Interesting point.
AdamThe immutable O.S. never included a hostile O.S. in the threat model but if it comes to that maybe its better just not to use a hostile distro to begin with?
@adamsaidsomething This shows how people tend to be short sighted. An immutable OS sounds beneficial to many, but it only remains that way until the developers do something the user doesn't like.
People who see immutable platforms as "the future" have not studied the past.
Chris Goss
Wilfredo 💬ℹ️ Now DistroWatch will need to include a new item on the distro description page:
• Age verification: yes / no
Root Moose@wilfredo @distrowatch If we are open to adding new search fields at distrowatch...
userland and libc type could be useful.
@RootMoose @wilfredo This is probably too broad to make a search field since several distributions include mixtures and/or multiple options.
For something like this you'd probably have a better time using the package search field to find a specific item, such as glibc or gcc or busybox rather than trying to group distros under an umbrella like userland or libc.
@wilfredo This one is planned, or something similar. Though it'll need to wait until projects actually implement some form of age declaration.
It will probably be a tri-option field: Age Verification, Age Declaration, None.