What’s very interesting to me in this discussion is that both Solid and fediverse are investigating how to implement Groups (see Groups implementation on SocialHub) and both based on ActivityStreams for that. This is a great opportunity to combine Solid vs. ActivityPub and, at least, stay as compatible as possible to each other.
How cool would it be if the Solid Groups App would be fediverse-compliant, integrated with the federated web, and showing Solid goodness to the AP audience over there?
The discussion on SocialHub was started by @ngerakines creator of Tavern, a minimalistic Mastodon-compliant AP server implemented in Go. Rather than creating formal descriptions the fediverse recently adopted the practice to have FEDERATION.md documents that describe server-to-server federated communication. Tavern has one too, that describes Group messaging.
@aveltens what I find unintuitive is the Offer{Join} semantics. To me that says “I, Angelo offer to join the group” . I see Offer more in terms of “I offer this Product or Service”. Also the Join in this case refers to an activity that has not happened yet, hence it is not a real activity. Creation of the Join should be left to the group after it happened, hence making it a real activity.
Some highlights of SocialHub discussion and FEDERATION.md (highly recommended reads):
- As per ActivityStreams spec a
Groupis an Actor-type (in ActivityPub this means it has its ownldp:inbox) - As such the
Groupis the single-source-of-truth of group membership - Joining a
Groupentails sending aFollowactivity to its inbox, which is responded with eitherAcceptorReject- This can be automatic
Acceptfor public groups, or a pending operation for private groups, manual approval. - A
Rejectincludes the reason for rejection e.g. “Private group, invitation only”.
- This can be automatic
- The
Groupnotifies its members (including the new member) about membership change with aJoin{Person}message. - An
Undo{Follow}to theGrouptriggers aLeavemembership change message from the group. - An
Invite{Person}to bothGroupandPersonfrom an existing member means that a subsequentFollowto that group from the person is automatically accepted.