We can receive and process these "wrapped activities" but we don't transmit them.
Posts
-
How do we handle Groups (Reconciling FEP-400e and FEP-1b12)? -
How do we handle Groups (Reconciling FEP-400e and FEP-1b12)?The announce is of course sent only to the members of the group. We always use the shared inboxes (if the system isn't configured differently). But this is not an issue at all. The post does - of course - contain the appropriate headers (
to
orcc
) to ensure that it is delivered only to the desired receivers. -
How do we handle Groups (Reconciling FEP-400e and FEP-1b12)?The list of group members is retrieved via the "followers" endpoint of the group with a signed request. Only if the signer is a member of the group can they retrieve the data. The permissions in the sender's post are then set to all group members. The server makes a regular "announce" activity. The other servers then make a signed request to the sender's server so that only members of the group can retrieve the post.
-
How do we handle Groups (Reconciling FEP-400e and FEP-1b12)?silverpill:My question was specifically about private groups. Implementations based on FEP-400e already exist in the Fediverse. As far as I can tell, private groups based on FEP-1b12 exist only in a form of an RFC.
Friendica, which follows FEP-1b12, does support private groups as well. We implemented them just like the public groups. The only addition is that the author system fetches the list of the group members, so that the access can be controlled.