OK now I'm confused what to do with delivery of non-public posts to a sharedInbox. If there is no mention, the only "to" will be a followers collection.

How does one even know it is a followers collection? Is it really expected to fetch every single collection every single time just to check 1) if it is a collection and 2) who it contains? Please don't say "grep for the word 'followers'".

Now I wish sharedInbox had stayed publicInbox :|

@jaywink I haven't read the whole thread. I can just tell what Friendica is doing with this "Followers" collection: We do fetch the path to the followers when we do our profile discovery. When the post then is directed to that collection, we know that it is directed to the followers. Then we just look in our relation table for the contacts to see if one of our users is following that user. Then we direct the post to this user.

Concerning the followers collection and Socialhome: When Socialhome implemented the same permission model like Diaspora, you don't have this single "Followers" collection, but an unlimited number of these. Then you have to place all people for a post in "cc" ("to" only, if these people are directly mentioned) or in "bcc". While "bcc" is special: You must never send out a post with "bcc" fields filled. Instead you have to direct the posts individually to the peoples personal inboxes - just like Diaspora is doing.
Follow

@Heluecht actually doesn't implement the same permission model as . It has "public", "limited" and then two non-federating visibilities. "Limited" is directed to specific people directly and is delivered via single delivery to each one not to leak the receivers to other receivers.

I'm still pondering about contact lists, for easier targeting. But there is no aspect type of following.

Socialhome isn't a diaspora clone :)

@jaywink this "limited" sounds like the "Followers" collection. So every of your followers is automatically included in that list? Then you could send it to the "Followers" collection only, without adressing the persons individually.

BTW: The delivery to the personal inbox automatically implies that the post is directed to that person. You don't have to include that person in any "to" or "cc".

@Heluecht The followers are hidden. I don't like the idea of delivering to a collection that is hidden, I prefer to deliver separately to each participant if the post is not public. If it's public, there is no need to mention the followers collection, just deliver to those servers that have followers.

@jaywink just FYI, some software looks for the followers collection to be in the address list. If the post is addressed only to public, it won't always be shown to followers. Tried it that way myself, had to add followers address anyway.
@tedu or you add every person to "to"/"cc" - or post to every single personal inbox.

@tedu Any idea which ones, so I can test against them as well? I wonder if they also require the followers collection to be readable? My followers collection are not readable so will it even help adding a dummy collection there?

@Heluecht @tedu But if someone doesn't cache followers locally that doesn't really help ;)

@Heluecht @tedu I guess in that situation we'll just be incompatible, not much that can be done.

@jaywink @tedu you don't have to cache all followers locally. You just have got to know which of your users is following this contact. And I hope that you stored this.
@jaywink consider Alice follows bob, who announces carol's note. If Alice runs pleroma, and bob addresses the announce solely to public, it will not be shown to Alice. Bob must add /bob/followers (or whatever) and then it appears. That's one case I know about, I've heard about others. It's not necessary that the followers collection be retrievable, or nonempty, just that it be listed in bob's actor object.

@tedu Hmmh seems weird requiring an URI that doesn't actually get resolved, sort of like a magic variable :P But thanks, will keep this in mind!

Sign in to participate in the conversation
Diaspodon

Instance majoritairement francophone. Nous ne régulons la fédération. Aucun contenu du fédiverse n'est filtré par une décision d'administrateur ou de modérateur.