trails/openspec/changes/public-content-visibility/specs/public-profiles/spec.md at dcbd703f4767230e840672be09acb30ee352a9ee

Ullrich Schäfer dcbd703f47

Propose social MVP: public-content-visibility + demo-activity-bot

Two stacked OpenSpec change proposals for a demoable social layer,
with scope deliberately minimal ("enough to send a URL and have it
open to real-looking content without signup"):

1. public-content-visibility
   - Adds visibility enum {private, unlisted, public} on routes +
     activities, defaulting to private for every existing row.
   - Detail pages (/routes/:id, /activities/:id) become accessible to
     logged-out visitors when content is public or unlisted; private
     → 404 (not 403) to avoid existence leaks.
   - Broadens /users/:username into a public profile listing only
     public routes + activities; 404s when there's no public content
     to prevent account enumeration.
   - Open Graph / Twitter Card meta on public detail + profile pages.
   - Visibility selector in the owner's edit flow.
   - Out of scope: follow/follower, cross-user feed, reactions,
     federation.

2. demo-activity-bot  (depends on #1)
   - A single bot user, Bruno the trail dog, seeded on worker startup
     when DEMO_BOT_ENABLED=true. Reserved username, sentinel email,
     no credentials.
   - pg-boss recurring job fires every 90 min, decides-to-walk with
     p=0.12 during 07:00-21:00 local, yielding ~2-3 walks/day at
     organic times.
   - Each walk: random start + end within inner-Berlin bbox, trekking
     only (dogs don't ride bikes), 2-12 km crow. BRouter plans the
     route; the route GPX is also attached as the activity's trace.
   - Everything inserted with visibility=public, synthetic=true.
   - Daily prune deletes synthetic rows > DEMO_BOT_RETENTION_DAYS old
     (default 14). Hard cap of 40 items/14d protects against runaway
     growth.
   - Small "🐕 demo account" badge on /users/bruno for honesty.

Both changes are artifacts only — no code lands with this PR. Apply
in order after merge: public-content-visibility first, then
demo-activity-bot.

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

2026-04-19 08:49:59 +02:00

1.6 KiB

Raw Blame History

ADDED Requirements

Requirement: Public profile page

The Journal SHALL serve a public profile page at /users/:username that lists the user's public routes and activities in reverse chronological order, viewable without authentication.

Scenario: Logged-out visitor views a profile with public content

WHEN an unauthenticated visitor navigates to /users/:username for a user with at least one public route or activity
THEN the page renders that user's display name (falling back to username), the @username@domain handle, and a reverse-chronological list of their public routes and public activities
AND items marked unlisted or private do NOT appear in the list

Scenario: Profile 404 when there is no public content

WHEN a visitor navigates to /users/:username for a user whose content is all private or unlisted, or for a username that does not exist
THEN the server responds with HTTP 404
AND the response does NOT distinguish the two cases, so existence of a private-only account is not leaked

Scenario: Owner sees their own profile

WHEN a user navigates to their own /users/:username while logged in
THEN the page renders exactly the same as for a logged-out visitor, plus a small owner-only control strip linking to settings

WHEN any visitor loads a populated /users/:username
THEN the page emits Open Graph tags (og:title, og:site_name, og:type="profile") so links shared on social platforms render a meaningful preview

1.6 KiB Raw Blame History