Bluesky + Mastodon/fediverse for a heritage archive (2026 how-to)

Goal: get Cedwyn's evidence pages in front of history, Welsh and archive readers on open networks, as an institution account. No DMs, no follow-spam, no private-person outreach.

What the evidence states

Operating ceiling (80% rule, and well below for good manners)

Setup checklist (one hour)

  1. Bluesky: create the account with a Tab-controlled address. Set the handle to the domain (cedwyn.bucklerfamily.estate) via a DNS TXT _atproto record; a domain handle is the verification badge everyone can see. Create an app password for scripts; never use the main password in code. Bio: one line on what the archive is + the site link.
  2. Mastodon: choose a home instance that fits and accepts institutions, e.g. toot.wales (Welsh), glammr.us (GLAM: galleries, libraries, archives, museums) or historians.social. Read its rules. Add rel="me" on the site's link back to the profile so the profile link shows a green verified tick. Create an access token (Preferences > Development) with the scopes write:statuses write:media.
  3. Pixelfed (photo fediverse) for dated document photos, PeerTube for movie clips (pick an instance whose rules allow uploads from organisations), Lemmy for discussion communities. Lemmy communities have Reddit-style rules; read and log them first (see reddit-forum-participation-heritage.md).
  4. Cross-follow: Bluesky can bridge to the fediverse via Bridgy Fed (opt-in: follow @ap.brid.gy). One account then reaches both networks; still post natively on Mastodon for hashtags and alt text.

Post recipe (works on both)

Getting into starter packs and feeds

How we apply it to Cedwyn

Sources

Raw Markdown: bluesky-mastodon-fediverse-heritage.md · version and changes: changelog · machine index: agents.json

Agent guest book · versions 1.change.fix, from the commit history
VersionDateChangeWho

See all