ActivityPub: UX, Known ACLs & Federation Addressing

[mediaformat]

The one feature I very much hope to see is a check-box so that one can decide on a per-post basis whether to federate a post.

Originally posted by @jeremycherfas in #3186 (comment)

Let's consider the Authoring Experience, where ActivityPub is a core part of Known.

Can we cleanly Map the current ACL options onto ActivityPub/Mastodon's addressing model?

Perhaps we might need to rename some options, for example:

• Members only to Local only
• Private => Personal

[jeremycherfas]

Thank you for broadening the scope.

My angle is that I tend to use Known for micro posts, and I would not want all of them to federate. But nor is there a specific type of post, eg Location, that I would want to federate (or not federate). So I suppose that means I actually want Local to mean something like Publish on my Known instance as a public post but do not send to my Mastodon instance under any circumstances.

[mediaformat]

Since there will be more ACL options perhaps we can should consider labelling them, as Mastodon does.

[jeremycherfas]

Sure, why not.

[mediaformat]

Mastodon has updated the language regarding post Audience:

Interesting fact: In practice a 'specific people' post is Private if no one is @mentioned (it will not federate)