Just a heads up.

Scott M. Stolz

A move activity would reduce this clash significantly.

That is what I was thinking. Mastodon understands move, but not nomadic identity. But move would have a similar result, which is have all of your Mastodon followers automatically follow your new channel, which is the desired result.

Mario Vavti

@silverpill thanks for the heads up @silverpill, the issue was still present and i just pushed a fix

Mario Vavti

@Scott M. Stolz hubzilla has no support yet for move activities. Anyway, i do not think it makes sense to send a move activity in case you change primary.
It would probably make sense if you delete a location but still have other locations you could move your connections to

Scott M. Stolz

@Mario Vavti How does Hubzilla handle distribution of posts to followers using Mastodon?

My impression is that it sends your new posts from the new server, which Mastodon will probably assume is a different server with a different channel. Wouldn't that mean that the Mastodon followers would still be following the non-primary channel, but no new posts are sent from there anymore. That winds up having the same effect as them no longer following you since they no longer see your new posts.

I know that PubCrawl tells everyone that there are aliases (clones), but I am not sure if Mastodon even reads that part.

silverpill

@mario Thank you!

Mario Vavti

@Scott M. Stolz the hub where you compose a message sends the message to your followers and sends a sync packet to the clone. When the clone receives the sync packet it will also send the message to your followers from that location. So as long as the clone is up and running it will not make a difference to which location the AP contact is connected. If a location goes down, the AP contacts connected to that location will stop receiving messages though.

Scott M. Stolz

@Mario Vavti Oh, interesting. So if you follow an ActivityPub contact on multiple clones, their platform would receive multiple copies of that post. But their platform would look at the meta data and know it is a duplicate.

I do wonder how @Mastodon handles those incoming post in regards to notifications though, since every message will still have the primary clone as the author's channel address ([email protected]). Will your followers still be notified of the new post on Mastodon?

Hey @Eugen Rochko, if you are sneezing right now, it is because we are talking about Mastodon. If you have a moment, could you clarify how Mastodon handles aliases (or clones, as they are called on Hubzilla)?

For example, does Mastodon recognize the aliases that Hubzilla mentions in the meta data?

Scott M. Stolz

@Mario Vavti And, I must mention that I do like the way you implemented it. This allows you to follow different ActivityPub channels on each clone, which becomes one way to filter content.

Mario Vavti

@Scott M. Stolz

Oh, interesting. So if you follow an ActivityPub contact on multiple clones, their platform would receive multiple copies of that post. But their platform would look at the meta data and know it is a duplicate.

No, they will just get duplicate posts from separate authors...

Scott M. Stolz

@Mario Vavti How would that appear on Mastodon?