Speaking of broken models and social contracts.
-
Speaking of broken models and social contracts. Can it really be true (as it looks like) that the origin server of a fedi user isn't notified when a post is delivered to a new federated server via a boost? That there is no complete record anywhere of a post's full distribution?
#ActivityPub #Mastodon
https://mas.to/@osma/114056828919559222 -
Speaking of broken models and social contracts. Can it really be true (as it looks like) that the origin server of a fedi user isn't notified when a post is delivered to a new federated server via a boost? That there is no complete record anywhere of a post's full distribution?
#ActivityPub #Mastodon
https://mas.to/@osma/114056828919559222 -
Speaking of broken models and social contracts. Can it really be true (as it looks like) that the origin server of a fedi user isn't notified when a post is delivered to a new federated server via a boost? That there is no complete record anywhere of a post's full distribution?
#ActivityPub #Mastodon
https://mas.to/@osma/114056828919559222 -
I suppose this might be particularly impactful for bulletin board style systems, yes, because they probably see less federated followers and hence have even less of a view into distribution.
@naturzukunft @julian -
Speaking of broken models and social contracts. Can it really be true (as it looks like) that the origin server of a fedi user isn't notified when a post is delivered to a new federated server via a boost? That there is no complete record anywhere of a post's full distribution?
#ActivityPub #Mastodon
https://mas.to/@osma/114056828919559222@osma@mas.to the default assumption is that announces are delivered back to the origin server in order to close the loop.
However it is not a requirement. For example I am considering not doing so for group announces.
