silverpill

FEP-5219: Groups and permissions

This is a discussion thread for FEP-5219: Groups and permissions

Summary

This document describes a permission system for ActivityPub groups.

It is inspired by XEP-0045: Multi-User Chat, which defines a comprehensive permission system for XMPP group chats.

I think the FEP should provide an example of following an actor. But I don't know yet how the sequence should look like

The FEP doesn’t currently point to this Discussion Thread (code).

It points to the issue tracker, but this thread can be used too.

My understanding is that a Generic ActivityPub Server would function similar to an ATProto PDS.

Yes, it is similar to ATProto PDSes and Nostr relays.

I’m curious on how this compares to projects like rdf-pub, Vocata, and ActivityPods.

These projects rely on linked data processing. This FEP attempts to solve the problem with JSON only.

Unfortunately I don't know enough about these implementations to provide a more detailed comparison.

Update: https://codeberg.org/fediverse/fep/pulls/851

I think the FEP now better explains why side effects must be explicit:

A generic server can only carry out the side effects of basic activities. Therefore, clients MUST specify the side effects of all other activities as additional activities. Clients can embed them into an activity using the result property, or send them separately.

FEP-fc48: Generic ActivityPub server

This is a discussion thread for FEP-fc48: Generic ActivityPub server.

Summary

Generic ActivityPub server is a server that implements standard ActivityPub client API or FEP-ae97 client API, and can process any activity (including activities those behavior is not defined in the ActivityPub specification).