I bike (more carrying capacity) about 9km each direction. (Belgium to Germany, funnily enough.) That being said, not wanting to do so under the burning sun is absolutely valid.
smiletolerantly
joined 1 year ago
Better open a package request (or pull request :D) then 😄
I host it publicly accessible behind a proper firewall and reverse proxy setup.
If you are only ever using Jellyfin from your own, wireguard configured phone, then that's great; but there's nothing wrong with hosting Jellyfin publicly.
I think one of these days I need to make a "myth-busting" post about this topic.
Consider this me asking
Matrix fits the bill.
Unless you don't like the federated nature.
Fair, maybe remove the question altogether, and have dedicated GOV endpoints for specific attestations?
While that's true from a technical perspective...
How/where do you keep the certificate? If you either need an app for it, or need to manually install it on your device, most users would probably be out. The benefit of my suggestion is that you need absolutely nothing except a way to authenticate with GOV.
- is a Problem with all of these, that's for sure.
I fjnt get the part about the info service tbh
As long as your browser saves an auth token or something for GOV somewhere, all of that can happen without user interaction.
I think that at the bare minumum, the PORN<->GOV connection must not occur. How about this (simplified):
- USER visits porn site
- PORN site encrypts random nonce + "is this user 18?" with GOV pubkey
- PORN forwards that to USER
- USER forwards that to GOV, together with something authenticating themselves (need to have GOV account)
- GOV knows user is requesting, but not what for
- GOV checks: is user 18?, concats answer with random nonce from PORN, hashes that with known algo, signs the entire thing with its private signing key
- GOV returns that to USER
- USER forwards that to PORN
- PORN is able to verify that whoever made the request to visit PORN is verified as older than 18 by singing key holder / GOV, by checking certificate chain, and gets freshness guarantee from random nonce
- but PORN does not know anything about the user
There's probably glaring issues with this, this is just from the top of my head to solve the problem of "GOV should know nothing".
Not sure. How about this (simplified):
- USER visits porn site
- PORN site encrypts random nonce + "is this user 18?" with GOV pubkey
- PORN forwards that to USER
- USER forwards that to GOV, together with something authenticating themselves (need to have GOV account)
- GOV knows user is requesting, but not what for
- GOV checks: is user 18?, concats answer with random nonce from PORN, hashes that with known algo, signs the entire thing with its private signing key
- GOV returns that to USER
- USER forwards that to PORN
- PORN is able to verify that whoever made the request to visit PORN is verified as older than 18 by singing key holder / GOV, by checking certificate chain, and gets freshness guarantee from random nonce
- but PORN does not know anything about the user
There's probably glaring issues with this, this is just from the top of my head to solve the problem of "GOV should know nothing".
Now THAT is something I wouldn't ever trust.