That ks for sharing this, this is fascinating.
Maybe the underlying rule is: the more you know about something, the more you are aware of its flaws, making the alternatives you know less about more attractive?
That ks for sharing this, this is fascinating.
Maybe the underlying rule is: the more you know about something, the more you are aware of its flaws, making the alternatives you know less about more attractive?
I don't really know, sorry :(
If you want to migrate, is going conduit - conduwuit - continuwuity (first version) - continuwuity (current version) maybe an option?
I went with continuwuity and am happy with it. Development happens at a steady pace, with sane priorities. The server is stable and I haven't had any issues to speak of, despite one minor bug that got resolved very quickly after creating an issue.
What's the median though? Through burnout, chronic illnesses,... some people are out sick for weeks or months at a time. That moves the average significantly.
Also e.g. parents becoming sick via their children more than they would on their own. And so on.
In any case - this isn't really an issue, is it? It has worked without issue for a long time. This is simply an attempt to reduce workers' rights and reduce spending at the cost of the poor and middle class, because the top few percent are sacred to the CDU.
It's used for when you are sick.
This, I assume? https://github.com/frida/frida That is indeed a bit eyebrow-raising. Though they do offer pre-built binaries.
Also for stuff like this, I can highly recommend the Nix package manager, even if you are not on NixOS. There it would, for example, just be nix run nixpkgs#frida-tools, from any distro.
But I know you're not OP. Would actually be interesting what exactly they tried to install.
pip and cargo are not intended as (system) package managers. Your target package may of course have dependencies on them, but from the way you described it it sounds like that's what you attempted?
No. As the other person said. The answers to the zkp do not refer to each other. All the site knows is SOME user was not 18 yesterday, and today SOME user is 18 (or 24.. or 89...). No relation between the two zkps/certs.
There isn't one. Local, on-device zero knowledge proof in a cross-platform OSS app. You scan your ID's NFC tag, once. Site only gets "is over 18 y/n" info. We all already have these IDs and they are used for a bunch of stuff, from doing taxes to creating bank accounts.
This doesn't make a call to government servers.
The app (or desktop application BTW, incl. Linux) reads your national ID's NFC tag, once. When you need to prove your age, the app locally computes a zkp that only tells the site "at least 18yo yes/no".
Note that every EU country has a form of national ID, and the digital capabilities of these IDs are already used for a bunch of stuff (e.g. taxes, bank account creation,...). This doesn't worsen the privacy situation for EU citizens, but instead ensures that no privacy-unfriendly solutions emerge.
Das wirkt wie ein Du-Problem, wenn du nur sowas schaust.