- From: Jeff Zucker (he/him) <jeff@oceanofstreams.org>
- Date: Fri, 21 Aug 2026 07:17:56 -0700
- To: public-solid <public-solid@w3.org>
- Message-ID: <CAG2wPQ-bb87OXRtQbdF6vtmohY_TW31T6peW_qtZk4HVrSO3TQ@mail.gmail.com>
I am pleased to announce three new open source products available for testing: * **FediPod** - serverless access to the Fediverse & ATProto from a pod and a local agent * **FediPod Gateway** - a thin spam-filtering gateway shared by multiple FediPod accounts * **FediPod Server** - a full Solid + ActivityPub server as a CSS component To create a FediPod account and/or sign on to a gateway, see https://fedipod.net To run a gateway or server, see : https://github.com/jeff-zucker/FediPod Please correct me if I'm wrong, but, AFAIK, FediPod is a full ActivityPub server, on both of the spec's profiles: server-to-server (§7) and client-to-server (§6) — POST /ap/outbox on the agent takes an activity (or a bare Note) and does the id-minting, side-effects and delivery, authenticated by a Solid-OIDC token whose WebID is the owner's. The Mastodon REST API is the everyday client interface; C2S is the spec's own. Group actors follow FEP-1b12: a carried post names the group as its audience, the moderator roster is published as the actor's attributedTo, a followed group's announced Delete of a post it carried is honoured, and the group's own moderation is announced to the membership. The FEP-4ccd pending-follow collections and the FEP-c648 blocked collection are published as owner-only documents. -- Jeff Zucker
Received on Monday, 24 August 2026 12:21:05 UTC