For those who are more technically oriented, here is some interesting information about how Hubzilla's nomadic identity interacts with platforms over ActivityPub.
The basic concept is that in Hubzilla, your channel can reside on more than one server and have more than one channel address. Hubzilla calls them clones since they are synced. One of those channels is designated as the primary channel. People can follow any of your clones and receive the same messages.
I wrote some notes about it here:
https://codejournal.dev/wiki/scott/Hubzilla/ActivityPubClones (Channel Aliases) and ActivityPub
The other day I learned something interesting. For ActivityPub followers, Hubzilla uses your clones to send messages to your followers on that clone.
The short version is that if you have your Hubzilla channel cloned onto more than one server, followers of primary@example.com will receive your messages from example.com, while followers of clone@example.social will receive your messages from example.social. This happens after the clones are synced.
More details in my personal notes:
https://codejournal.dev/wiki/scott/Hubzilla/ActivityPubThis is different than how Zot Protocol handles it, which I also mentioned in my notes.
It is a rather ingenious way of dealing with the fact that most other platforms do not recognize the concept of nomadic identity.
