Fediverse

Outlap implements ActivityPub, the protocol behind Mastodon and much of the Fediverse. Drivers can be followed from other servers, and Outlap drivers can follow people elsewhere.

What’s supported

• Discovery by WebFinger: acct:slug@host.
• Actors for Outlap drivers (type Person, linking to their public driver page), with an inbox and outbox, followers collection and a shared inbox.
• Posts served as ActivityPub objects.
• Inbound activity: boosts, likes and replies from the Fediverse are recorded against your posts.
• Outbound follows: follow a remote account by handle. Outlap sends signed Follow and Undo(Follow) activities and imports recent posts from accounts you follow.

Requests Outlap sends are HTTP-signed.

Link an existing Fediverse handle

You can connect a handle you already have to your Outlap account. Ownership is proven with a backlink: add your public Outlap profile URL to your remote account’s profile metadata (the same rel="me" approach Mastodon uses for verified links). Outlap then checks the link both ways via WebFinger before connecting.

Accepted profile hosts for the backlink: outlap.xyz, www.outlap.xyz and app.outlap.xyz.

Endpoints

Path	Purpose
GET /activitypub/.well-known/webfinger?resource=acct:slug@host	Discover an account.
GET /activitypub/users/{slug}	Actor document.
POST /activitypub/users/{slug}/inbox	Receive activities.
POST /activitypub/inbox	Shared inbox.
GET /activitypub/users/{slug}/outbox, /followers	Collections.

Paths are under the same API host. You normally never call them by hand; your Fediverse server does.