It seems like #ActivityPub was always supporting username changes when implemented correct.
General Discussion
5
Posts
3
Posters
9
Views
-
It seems like #ActivityPub was always supporting username changes when implemented correct. @snarfed.org@bsky.brid.gy's Bridgy Fed perfectly renamed my account as I changed domains on @bsky.app@bsky.brid.gy.
Fediverse Data is not Deleted ... -
It seems like #ActivityPub was always supporting username changes when implemented correct. @snarfed.org@bsky.brid.gy's Bridgy Fed perfectly renamed my account as I changed domains on @bsky.app@bsky.brid.gy.
Fediverse Data is not Deleted ...@cmislek.me well, yes and no.
When people talk about username changes in the context of AT-Proto, they mean it that the two users on each side of the rename can be clearly identified as the same entity (through the magic of cryptographic keys).
In ActivityPub even if you can create a new account, there's no way to link it unambiguously to the previous one because in the protocol the URL of the user itself is the identifying element, not a separate piece of information like a public key.
-
@cmislek.me well, yes and no.
When people talk about username changes in the context of AT-Proto, they mean it that the two users on each side of the rename can be clearly identified as the same entity (through the magic of cryptographic keys).
In ActivityPub even if you can create a new account, there's no way to link it unambiguously to the previous one because in the protocol the URL of the user itself is the identifying element, not a separate piece of information like a public key.
Damn, I got bridged. :D
-
@cmislek.me well, yes and no.
When people talk about username changes in the context of AT-Proto, they mean it that the two users on each side of the rename can be clearly identified as the same entity (through the magic of cryptographic keys).
In ActivityPub even if you can create a new account, there's no way to link it unambiguously to the previous one because in the protocol the URL of the user itself is the identifying element, not a separate piece of information like a public key.
mariusor@metalhead.club might you be conflating username changes and account migrations?
Changing preferredUsername (or maybe it was name, I forget now) is pretty well supported if you're not Mastodon.
-
@julian possibly, but I was trying to answer to what I thought was Çağan's argument.
It feels to me like there was no confusion about ActivityPub being able to update a preferredUsername, name or any other property of an Actor outside of it's ID.
I was hoping he didn't confuse Mastodon for ActivityPub but maybe I'm wrong. :D
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@Edent It should work. But of course, there is a possibility of some popular implementation not being able to handle it.
-
@Edent - fun - just knowing this exists has me thinking of where to try it.
-
I mean, I see no reason why this wouldn't work. `alsoKnownAs` is an array of names.
I suppose if Alice is following both Bob and Chuck, then B & C are merged into Dave, she won't "double follow".
But I wonder if there are any other gotchas?
-
A question about #ActivityPub account migration.
Is it possible to use it to combine multiple accounts into one?
That is, can I `movedTo` all my old accounts to one new account, and set *several* `alsoKnownAs` on my new account's actor?
-
@Edent There is also the html5 dom parser in 8.4, etc.
Nah, I suspect in Ubuntu 26.04 LTS version 8.5 will be available. For those simpler/cheaper webhosting with some oldstable Debian I suspect they use PHP packaged by SURY.
I just have to be patient.
-
@fabio @liaizon New quote test, wooo!
https://blog.fabiomanganiello.com/article/Madblog-federated-blogging-from-markdown
-
@silverpill
@general @julian
Talk about an appropriate application of a merkle tree
-
@aslakr yeah, it's a tough trade-off.
The new curl stuff in 8.5 looks essential for dealing with all the POSTing it has to do - and the new URl validation is very handy.Happy for you to make an 8.3 fork if you think it is worth it.
