Uy... 👀 Interesante...'n> Change the identifiers used in ActivityPub to numeric IDs (instead of their username) for new users.
Fediverso
1
Post
1
Autori
0
Visualizzazioni
-
RE: https://mastodon.social/@MastodonEngineering/115337952873418574
Uy... 👀
Interesante...> Change the identifiers used in ActivityPub to numeric IDs (instead of their username) for new users. This is a first step towards allowing account renaming. — Github PR #32724 (by ClearlyClaire)
-
undefined julian ha condiviso questa discussione
Gli ultimi otto messaggi ricevuti dalla Federazione
-
RE: https://mastodon.social/@MastodonEngineering/115337952873418574
Uy... 👀
Interesante...> Change the identifiers used in ActivityPub to numeric IDs (instead of their username) for new users. This is a first step towards allowing account renaming. — Github PR #32724 (by ClearlyClaire)
-
FYI all the Mastodon team is looking for feedback on featured collections (aka "starter packs") so they may check in on this post 🙂
-
@anna @adrienne @eniko @mcc all the records in your PDS contain references to your identity (DID document), it's theoretically possible to modify the data to change that but requires rewriting your entire PDS for that account, so not particularly practical.
It's the DID that is moderated against in the higher layers, not your handle.
So it doesn't matter if you're @fred.example or @jason.example, if the DID used for one becomes the DID used for another handle.
It's kinda like how on ActivityPub, software has often encoded your username into the identifier for all your posts, meaning you can't change it without breaking everything.
(Though Mastodon is starting to fix this long-standing issue, there's fix only applies on new accounts, there's no protocol level way to fix it yet — it's kinda a weakness in JSON-LD)
-
@mcc yeah have a look at Rudy's thread there, he makes that very clear. And similarly Northsky is saying well, our original plan was do PDS as Phase 1, Relay as Phase 2, and AppView as Phase 3, but now we're acceslerating Relay and AppView up and treating it all as Phase 1. My take is that everybody always took the approach of treating Bluesky PBC as a potential adversary but didn't expect them to be this adversarialy this quickly.
(If this is all an N-dimensional chess play to blow up the company to speed up the decentralization ... well as shitposting goes, that's pretty darned epic. But it's probably just horrbile comms accelerating and magnifying the tensions that were always inherent. Time will tell I guess.)
@by_caballero it's true that's a huge hole in the composable moderation model (and Rudy and others had been looking at it even before this -- https://discourse.atprotocol.community/t/how-should-we-fairly-split-the-costs-of-commons-moderation-across-producer-and-consumer-apps/122 is interesting thinking from the Eurosky perspective although doesn't yet point to any conclusions). But for this particular case they just need an appeal method for community members that allows themm to override the Bluesky mod service's app-level takedowns in their own AppView. On the deeper issue though I feel pretty vindicated because I've always said that composable moderation is interesting and valuable in some important use cases but doesn't actually solve the moderation scalability issue.
-
@mcc @jdp23 here guys this might help clarify why Rudy has to rearrange his epics in jira:
https://whtwnd.com/bnewbold.net/3m2j6ccx2bs2t
moderation can only be additive until/unless you pony up the CSAM/hashmatch API key money plus roll and run yr own mod sys at scale. thats the real Achilles heel of composable moderation-- replacing the bottom layer is incredibly expensive
-
@adrienne @eniko @mcc one thing i was never clear on, if you have your own pds and get permad, can you migrate and get around the perma, or is it some kind of cryptographic seed/hash of your pds data that's perma'd so you're fucked?
-
@eniko @mcc if you're on your own PDS, you at least don't lose all your existing posts if bsky decides to permaban you. (If you're on one of their mushroom PDSes, they'll nuke all your content along with a permaban.)
-
I really don't understand the point of packs when Mastodon has hashtag follows. Mastodon is already winning in terms of discovery here and in fact I still don't use Bluesky because its impossible to discover content there.
On Bluesky you get a pack of people but in linear timelines the power spammers just take over and then you have to do all that personal curation anyway but it's often even a worse starting point than just blank slate. With hashtag following I just subscribe to #fediverse and discover new content and creators organically.
Instead I'd like to see Mastodon commit more to organic discovery rather than consolidation of power users by expanding post classification system like using AI classification that attaches topic hashtags to posts etc to help users discover content they actually want to see not follow personalities.
