of numbers instead of human-readable names
TBF, they have introduced a 'verified' system that lets you use human readable names.
of numbers instead of human-readable names
TBF, they have introduced a 'verified' system that lets you use human readable names.
I just want to sync my music between my computer and phone and I really can't be arsed with this drama.
Yeah, people are tribal and decentralisation lets people express that in ways centralised platforms don't. Something, something, tech won't save us.
Clicking though to community to post and selecting a community from the create post page are same problem rearranged. A user who subbed to ~technology@piefed.social isn't going to know the difference between !technology@lemmy.world, !technology@lemmy.zip and !technology@piefed.social.
Solution 2 in the post, multicommunities. I'm not sure it actually solves the problem though, as you still have to go to the actual community to post and I imagine multicomms add an extra layer of confusion to that.
Can't wait for the follow up post decrying PeerTube for only allowing videos, or Bookwrym for only allowing book reviews. Just because it's ActivityPub doesn't mean it has to be a Twitter timeline.
Once a major actor in a decentralised network starts to mess with the protocol, there are only two possible output: either that actor lose steam or that actor becomes dominant enough to impose its own vision of the protocol. In fact, there’s a third option: the whole protocol becomes irrelevant because nobody trust it anymore.
You mean like Mastodon? Where's the angry diatribe about Mastodon not allowing posts to have more than 4 pictures despite other platforms allowing more (Pixelfed allows up to 20 for example)?
Real Account Portability: Move your entire account – posts, comments, followers – to any new instance seamlessly. Your identity travels with you.
This is nice in theory but comes with edge cases that are hard to account for. Like, what if you have a post and your new instance defeds the instance the post's community is on? You either have to allow banned content onto the instance or the user loses data, neither of which are acceptable.
This is part of why ATProto's decoupling of user data from app logic is kinda genius and the direction we should go in if we want portable actors in Lemmy/thredi.
Full Fediverse Compatibility: We can add DIDs to Lemmy while staying fully interoperable with Mastodon, Kbin, and all other ActivityPub platforms. No breaking changes, just a powerful upgrade.
Not really, every fediverse platform that people use expects an Object's id to be a https URI it can just fetch the resource from. This is part of why FEP-ef61 specifies a way of translating a DID to a https URI. That's not to mention that moving existing actors from their current ID to a DID will cause all sorts of interop problems.
Edit: Also, is this AI-generated? It has all the tells of Gemini output, especially the the issue on Github.
Wow, that's bad. I would hate working with this so much.