Well, this is then a relay like in
I started learning ActivityPub for a project I want to do with WebVR, and realized the social groups functionality I’d been craving in the fediverse would be dead simple to implement with a server-to-server app.
Now I have Guppe Groups up and running. It really just does two things:
Create new group actors on demand whenever they are searched or tagged
When receiving an activity to an inbox, announce it
This creates actors whose outboxes serve as group activity timelines that people can foll…
while the Conf session and these posts are more about group based communication
I’ve implemented groups in Tavern and would like feedback and comments. All of the group specific actor and activity behavior is documented in https://gitlab.com/ngerakines/tavern/-/blob/issue-21-groups/FEDERATION.md as well.
Groups share the same namespace as users and it is up to instance operators to moderate how that namespace is managed. For example, both @sneakerheads@groups.tavern.town, @sneakerheads-group@tavern.town, and @sneakerheads@tavern.town are all valid names. I’m considering ad…
and
There will be a moment when I’ll have groups. And then there will be a moment when I’ll have to federate these. There seems to be no consensus on what groups actually are and how to represent them. So,
Group members. How are those represented? Are they the followers collection? Can a group have followers at all? Or should it be a separate, custom collection a-la Mastodon’s pinned toots?
Since it’s a collection of actors anyway, can groups be members of groups? This feels weird to think about…
1 Like