@heluecht @evan I'm also glad sharedInbox exists!
-
@heluecht @evan I'm also glad sharedInbox exists!
The issue I had with sharedInbox was that I was proposing that it should respect the actor model for delivery and we could do this by the posting server adding an HTTP header which listed all the intended recipients. However, Mastodon's devs said "no, we're already tracking the follow lists ourselves so we'd rather use our own information"
And I conceded to that at last minute because we needed to get the spec out. This lead to several issues!
-
@heluecht @evan I'm also glad sharedInbox exists!
The issue I had with sharedInbox was that I was proposing that it should respect the actor model for delivery and we could do this by the posting server adding an HTTP header which listed all the intended recipients. However, Mastodon's devs said "no, we're already tracking the follow lists ourselves so we'd rather use our own information"
And I conceded to that at last minute because we needed to get the spec out. This lead to several issues!
@heluecht @evan delivering to an "instance" and expecting that the instance can infer who should get the message means that the delivering side isn't as in control of where the messages go, it violates the actor model, and precluded several possible directions for a more capability-oriented model which I think the fediverse should have pursued. I don't think "inferred recipients" is a good design. The poster (or more accurately, the addressed collection) knows best its recipient list.
-
undefined cwebber@social.coop shared this topic