A calm place to write long-form, and publish it to the open social web. skypress.blog/
0

Configure Feed

Select the types of activity you want to include in your feed.

Record decision 0022: view records on mu.social

+26
+26
docs/decisions/0022-atmosphere-view-host.md
··· 1 + # 0022 — View records on mu.social, not bsky.app 2 + 3 + ## Context 4 + 5 + SkyPress publishes to the Bluesky/atproto network, but it also links readers out to 6 + an AppView to *view* profiles, posts, and hashtags. Those links pointed at `bsky.app` 7 + and were marked with the Bluesky butterfly. 8 + 9 + ## Decision 10 + 11 + - View-links (author profile, bio mentions/hashtags, editor-inserted mentions, post 12 + "view" links, sign-in account creation) point at `mu.social`, a Bluesky AppView with 13 + the same `/profile`, `/profile/<did>/post/<rkey>`, and `/hashtag` path scheme. 14 + - The host lives in one place: `src/lib/social/atmosphere-url.ts`. 15 + - Link labels/aria say "the ATmosphere". Network/protocol copy ("creates a public 16 + Bluesky post", `app.bsky.feed.post`) stays "Bluesky" — it describes the real network. 17 + - The butterfly icon is replaced by the 🌀 emoji. 18 + - `public.api.bsky.app` API calls are unchanged — mu.social does not serve that data API. 19 + 20 + ## Consequences 21 + 22 + - `src/lib/publish/mentions.ts` `PROFILE_RE` accepts both `bsky.app` and `mu.social`, so 23 + mentions in drafts saved before this change still get cc'd on the companion post. 24 + - Already-published articles keep the `bsky.app` mention links stored in their content; 25 + only newly authored mentions use `mu.social`. 26 + - Changing the AppView again is a one-line edit to `ATMOSPHERE_WEB_BASE`.