Is it so desirable to sent even more info, this time potentially non-public, if you decide to interact with the other instance?
This includes partial information about your online identity, namely identifying you uniquely. Not all instances should be considered trustworthy, so your log-in token may get re-used by a malicious instance to post things in your name here and there. Kind of a silly situation, favorable to spammers for example.
Have you tried the archive link? There's no need to sign in with it
Users can already do so, what would instance-level block bring?
I had "weathering steel" in mind, butt you're right, even in this case, rust still eats at it, just slower.
Is it now? Github says it's Rust at 80%. And a layer of rust is a good protection again further rust 😃
not enough nodes were there
And a bit later he mentions "Not just all account servers; different kinds of services". I have a feeling this has been overlooked in the recent discussions about Threads. The fediverse is an excellent base to launch a myriad of varied kinds of services, not all of them "account servers" like lemmy, mastodon, pixelfed, etc. Let's also build more bots and automated services too :3 It could be games played through fedi, it could be statistics, admin tools, and whatever comes to mind.
This is the kind of thing that would be added value even for huge account nodes, and would probably act as a deterrent to want to change the rules of the game (making changes to ActivityPub). If you change the proto, your users would lose access to all the nice things that exist outside of the instance, quite the backlash, like what happened with reddit.
What do you all think?
Good reminder that: small instances = small impact. Both true for the positive and the negative.
One could make the argument that 5000 users is still not mass adoption. If that is enough activity, then mass adoption is not a requirement for the fediverse to be a nice social place to be.
All 35 of us :d
@[email protected] ? I start typing @Dana… and then I get a popup to autocomplete with the user name
Wouldn't that overload popular instances even more? Right now, popular instances only need to accommodate their users, but with a "fediverse-wide" auth, soon they'll also have to serve content to people who followed that popular link to their content?