And according to your /etc/passwd you are , located at , reachable under and .
Korrekter wäre "Grundsätzlich ist es schon gut, dass wir uns mit AfD-Inhalten von jeglicher Logik und Menschheit abgrenzen."
A lot of technologies are at hand for P2P communication, which, if you abstract and design it somewhat intuitively, means even more stability and comfort than with just a server.
And no one is saying that there should be no server ever. Forcing a connection to a proprietary server without alternative options is obviously bad, but having a FOSS, self hosteable server with a managed option for non-selfhosters would pretty much be perfect.
- So you'd have an application level, eg. for native functions like a shared clipboard.
- An API level, so third party apps can synchronize/move to other devices.
- A remote device level, which represents all devices you can push data to. Also manages automatic (0/1 click) pairing over NFC and LAN, and manual pairing over Bluetooth, Direct Wifi, and Servers.
- A transport level, which presents NFC, Bluetooth, Direct WiFi, LAN, Server(s) and whatnot as an option for the device level, and manages the availability of transports per device. Transports are chosen based on eg. privacy * speed.
Now I want to implement that shit but have no time to do that :c
I can only hope that people will someday realize that systemd did nothing more than add a userdb field, symmetric to other, similar, userdb fields, while the distro installers are the components that actually decide wherever you need to enter your data, and more importantly, if that includes an actual verification of that data.
If you want to ensure that real age verification will never be a thing, tell your distro maintainers how you feel about that, participate in relevant discussions about the installer etc. Also, support realistic pushes towards keeping it out. No, a random GitHub user won't be able to maintain a hard Ubuntu fork without systemd. Not even for a day. However, it is possible to maintain a soft fork of the installer, minus age input, including the building infrastructure for release images.
Even if systemd would now remove the BD field, or all user info fields, distro maintainers could and would just switch to another implementation, nullifying any efforts and just worsening the situation.
I hope she gets mauled sooner or later. Preferably sooner.
I'd like a CEO paperweight. Literally just a chunk of its body as weight.
And 64 years ago, GECOS was released, with a dedicated field for a users real name, location, phone number and email. That was implemented in UNIX shortly after, as a field in /etc/passwd, which means all Linux distros and other UNIX-like OS's like MacOS have and had fields for all of that forever. So if you don't want the option to store personal information in your OS, use TempleOS.
Other comments mention the post being a google drive link, so ig it was later changed to peertube
Yeah, with GECOS introducing the GECOS field, they normalized name verification, phone number verification, email address verification as well as location verification. So soon we should see those becoming mandatory and controlled.
Oh wait, that was 64 years ago, so by now we should already be in literally 1984, actually?! Or is it that no one actually gives a fuck about a handful of programs trying to read user data that no one set, and if they set it, set it to a nonsencial/false value without any component verifying anything?
The problem isn't libraries adding more optional field to their capabilites, but management systems (such as a distros installer) making them mandatory against user will. That is what users should actually object to. No installer or component I know actually sets the location field. However, some are already planing to require the birth of date field, which is the actual start to pushing any boundaries. So start protesting there.
Or, if you actually think that simple standards for how user data is stored is already malicious verification, your only option is probably, unironically, TempleOS, as even DOS stores user information, Country + TZ, available for other programs to fetch.
LUKS header disk emergency destroy button? *boop!
Und gerade jetzt funktioniert Öffi auch mit der Bahn API nicht mehr...
Bro tut so als wären die Sommerferien in Österreich das angeborene Grundrecht und Teil der evolutionsbedingten Überlebensstrategie, wie bei Zugvögeln.