Agreed with your points, no question, but I think that even with increased education to implementers and/or fedizens, there’s still a gap between followers-only and public that means “public to this network” that the protocol could address. So I suppose we are then at the point you raise of
surface and map out the mismatched expectations and submerged assumptions
… barring some maybe-not-far-enough-reach polls on Fediverse, how best to approach this?
WRT
Just to nitpick on this a bit, “all users” in this context is following the Overview that describes
- A client to server protocol (so users, including real-world users, bots, and other automated processes, can communicate with ActivityPub using their accounts on servers, from a phone or desktop or web application or whatever)
and
In ActivityPub, a user is represented by “actors” via the user’s accounts on servers.
My read of the document is that a user is not a random public http request, but a user of ActivityPub (“including real-world users, bots, and other automated processes”) with an account on a server, represented by an Actor.