Conversation
Notices
-
@dielan Regardless of whatever Mastodon branding crap.
Censorship (as in abusive admins) on fedi is annoying but it's a much lesser version of what's on Twitter and it fixes itself with people moving to better instances.
Moving to a better twitter instance? You can't, or that's called moving to fedi.
-
@roboneko @dielan
Public keys:
- Weaken over time together with the algorithms and their parameters (Like dsa1024-sha1 OpenPGP keys are probably way too weak to be significant)
- Game over if you leak your key, but also if you loose it. Much more dangerous than say a password or an OAuth token.
- You need a very good cryptographic implementation and a good source of entropy. (see: logjam, debian openssl, …) I wouldn't trust a browser to provide this.
See OpenPGP and Tor.
-
@dielan Yeah, I think nostr handwaves away a lot of problems unique to it's style and we're going to see them get bigger plus discover new ones as it gains adoption.
Like who could have acknowledged stuff like fediblock back in GnuSocial era? Specially before servers like smugloli.
Or that we could solve the account migration problem either with public-key cryptography (friendica-hubzilla-zap lineage) or just forward and back references (mastodon/pleroma/…). Both having pretty massive pro and cons but none being really the best.
-
@lanodan @dielan
> Both having pretty massive pro and cons
serious question, what are the cons of nomadic identity via pubkey? as long as you use delegation I really struggle to find any. if the concern is people losing their keyfile you can always provide the option to go the custodial route
of course discussing pros/cons and actually delivering a functional implementation are entirely different things. and achieving adoption of whatever scheme yet another hurdle after that. but purely in terms of hypothetical downsides I'm curious what those are
-
@dielan And to me, fedi without using DNS wouldn't have worked more than say Tox did, because human-meaningful names are quite critical.
And there has yet to be a true alternative to DNS with adoption beyond early-adopters.
-
@lanodan the other reason I highlight this is because Snowdens post I screenshotted here was on Nostr, which actually kinda sidesteps this problem. As nostr relays only store and replicate text. Theres no file upload (the front ends we have right now embeds image URLs, so in theory takedown requests for illegal content would go to the place hosting the image, not the nostr relay containing a link to it), theres no instances, its just keys.
So this problem I just described, which is probably not what snowden is talking about cuz I think he's misinformed, is actually kind of solved over there? Strange times
-
@lanodan I dont even think thats much of an issue
The only real censorship problem on the fedi IMO is scorned trolls calling up peoples domain registrars and hosting providers to cut their service over false reports and false flags
Admins of remote instances rejecting your posts doesnt actually silence you from speaking. You will be heard in some way shape or form
-
@dielan Registrar/TLD censorship or even just instability has existed for decades prior though, it's why most seasoned ~admins prefer OG net/com/org/… or ccTLDs of their own region.
-
@lanodan @dielan
> there has yet to be a true alternative to DNS with adoption beyond early-adopters
it is entirely possible for a petname system to be fully backwards compatible with ICANN administered DNS. and there's no reason a key based system can't provide user friendly names for keys, DNS based or otherwise
for example fedi via tor is (arguably) already fedi without DNS
-
@roboneko @dielan But Tor has yet to have a petname system, right?
And even with a petname system… How do I easily give say an onion address to someone when AFK?
Or do you just assume everyone is terminally online? (increasingly true to be honest)
-
@lanodan @roboneko @dielan QR codes? 😬