trails/openspec/changes/archive/2026-06-07-social-federation/specs/social-follows/spec.md at d87a1e30c28c2faa3eebd029a4032934248df67d

Ullrich Schäfer d87a1e30c2 docs(openspec): archive social-federation; sync delta specs into main

The change shipped end-to-end (58/58 tasks; live on trails.cool since
2026-06-07, soaked against Mastodon and flagship⇄staging). Delta specs
synced into the mainline:
- specs/social-federation/spec.md created (8 requirements: actor
  objects + WebFinger, signing keypairs, narrow inbox, outbox, push
  delivery, trails-only outbound, poll ingestion, audience filtering)
- specs/social-follows/spec.md: social-activity-feed requirement
  updated for remote rows + audience gating; pending lifecycle for
  outbound remote follows added
- specs/public-profiles/spec.md: Pending follow-button state added

openspec validate --all: green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-07 16:47:35 +02:00

3 KiB

Raw Blame History

ADDED Requirements

Requirement: Pending lifecycle for outbound trails-to-trails follows

A follow row originated from a local user against a remote trails actor SHALL be created with accepted_at = NULL (Pending) until the remote's Accept(Follow) activity arrives at our inbox. The local user SHALL see the Pending state on the profile page and SHALL be able to cancel a Pending request, which deletes the row and delivers Undo(Follow) to the remote inbox.

Scenario: Outbound follow enters Pending

WHEN a local user follows @alice@other-trails.example
THEN the follow row is created with accepted_at = NULL, a signed Follow is delivered to the remote inbox, and the profile button shows Pending

Scenario: Pending → Accepted

WHEN the remote inbox returns Accept(Follow) for our outgoing Follow
THEN accepted_at is set to now(), an immediate one-off outbox-poll is enqueued for that actor, and the profile button transitions to Unfollow

Scenario: Pending → Rejected

WHEN the remote inbox returns Reject(Follow) for our outgoing Follow
THEN the follow row is deleted and a small UI notice is surfaced on the user's outgoing-follows list

Scenario: Cancel a Pending follow

WHEN the follower cancels a Pending request from the outgoing-follows list
THEN the follow row is deleted and an Undo(Follow) activity is delivered to the remote inbox

MODIFIED Requirements

The Journal SHALL expose a feed at /feed, visible only to signed-in users, listing activities from the users they follow with an accepted follow. The feed SHALL include public activities from any followed actor (local or remote) and SHALL include followers-only activities from a remote actor only for the specific local viewer who holds an accepted follow against that actor. private and (local) unlisted activities SHALL NOT appear regardless of follow state.

Scenario: Feed aggregates local + remote public activities

WHEN a signed-in user with one or more accepted follows (mix of local + remote trails) loads /feed
THEN the page shows the most recent public activities across all followed actors, reverse-chronological, up to 50 per page

Scenario: Followers-only remote content reaches only the right viewer

WHEN two local users A and B exist; only A holds an accepted follow against remote actor X; X publishes a followers-only activity that lands in our cache via A's poll
THEN A sees the activity in /feed and B does not

Scenario: Empty feed state

WHEN a signed-in user with zero accepted follows loads /feed
THEN the page shows an empty-state message pointing them to follow someone

Scenario: Pending follows do not contribute to the feed

WHEN a signed-in user has only Pending outgoing follows
THEN the feed renders the empty state; no remote content is fetched or shown for that follow until Accept(Follow) lands

3 KiB Raw Blame History