Built on open standards

The social web is a set of open protocols. Archival implements ActivityPub, the AT Protocol and Webmention as part of its hosting.

W3C Recommendation

ActivityPub

The protocol behind Mastodon, Threads, Pixelfed and the rest of the fediverse. An Archival site is an account people can follow, and every deploy delivers what changed.

Open protocol

AT Protocol

The network Bluesky runs on. An Archival site hosts its own account there: its handle is its domain and its posts are its content.

W3C Recommendation

Webmention

The simplest way for one page to tell another that it linked to it. Archival receives, verifies and keeps mentions of your pages, and sends them when your posts link out.

Works with Mastodon apps

Your website is your identity

Your handle is your domain, and so is your server. Sign in to it from Ivory, Tusky, Elk, Phanpy or most other Mastodon apps to read the accounts you follow and star, boost and reply as yourself.

Your site is an account

Add an activitypub section to your site and it becomes something people can follow: @blog@example.com, from Mastodon, Threads, Misskey, Micro.blog and hundreds of other apps.

Archival answers WebFinger and serves your actor, inbox and outbox. Every time your site deploys, the people following it get what you added, changed or removed. Pin a post with a single boolean field.

Your site is an account on your own domain. Each deploy delivers its posts to followers on Mastodon, Threads and other ActivityPub servers, and their follows, likes, boosts and replies come back. YOUR SITE @blog@example.com your posts, on every deploy posts follows · likes · replies FOLLOWED FROM Mastodon Threads Misskey Micro.blog and hundreds more
  1. 1 Map a post type's fields once. Archival serves the account and delivers each deploy.
  2. 2 Followed from anything that speaks ActivityPub, and what people do there comes back.

Your domain is your Bluesky handle

Add an atproto section and your site is an account on the AT Protocol, the network Bluesky runs on. People follow @example.com. The site hosts the account itself.

Every deploy publishes what your content says. A short post goes out as a Bluesky post with its images. Long-form writing goes out as a standard.site document and a post with a link card back to your page. Edit the file and the post updates. Delete it and the post is gone.

Your site hosts its own AT Protocol account, whose handle is your domain. Each deploy publishes its posts, which appear on Bluesky, and follows, likes and replies come back. YOUR SITE post/hello.toml @example.com every deploy follows · likes · replies BLUESKY Your site @example.com 3 replies · 12 likes and any AT Protocol app
  1. 1 The site hosts its own account. Its handle is your domain.
  2. 2 Posts appear on Bluesky, and what people do with them comes back.

Sign in from any Mastodon app

Turn on allow_mastodon_clients and your site is a server Mastodon apps can sign in to. In Ivory, Tusky, Elk, Phanpy or most others, add a server and give it your domain. The app opens the Archival editor, you choose which of the site's accounts it acts as, and you approve.

The app shows the account's home timeline: every post and boost from the accounts it follows, kept by Archival as they arrive. Star, boost and reply from wherever you read. A reply is published as a post of your account, and a follow is added to your site's configuration and sent on its next deploy. Your posts are still your site's content, written in the site.

A Mastodon app signs in with your domain as its server. Once approved in the Archival editor, it reads the account's home timeline and stars, boosts and replies as that account. HOME Ana @ana@mastodon.social Kai @kai@pixelfed.social Sam @sam@sams.blog Ivory · Tusky · Elk · Phanpy sign in timeline YOUR SITE @jesse@example.com no password to make star, boost and reply as you
  1. 1 Add a server in any Mastodon app, and give it your domain.
  2. 2 Approve it in the Archival editor. The app reads the account's timeline and acts as it.

Pages that talk to each other

Webmention is how the open web replies. When a blog on WordPress, Ghost or micro.blog links to one of your pages, its site tells yours. Archival takes the mention, fetches the page to confirm the link, and reads its microformats to learn whether it is a reply, a like, a repost, a bookmark or a plain mention.

It works in both directions. Map a post type and every link in your posts sends a mention of its own when you deploy. Likes and replies from Mastodon and Bluesky arrive the same way through Bridgy.

A page on another site links to yours and sends a webmention, which Archival verifies and keeps. When your posts link out, Archival sends a webmention to the other site on deploy. their-blog.com/notes/42 Replying to example.com/post/hello mention and yours to them example.com/post/hello ✓ 1 reply, verified kept with your site
  1. 1 A page elsewhere links to yours and its site sends a mention. Archival checks the link and keeps it.
  2. 2 When your posts link out, Archival sends the mention on deploy.

Bring the conversation home

Replies, likes and boosts from the fediverse, replies, likes and reposts from Bluesky, and mentions from other sites are kept with your site. A small carrier reads them when a visitor asks, so a post's page can show the whole thread under it: a comment from Mastodon beside a reply from Bluesky and another from a blog.

The carrier decides which of them to show and in what order. Your pages stay static HTML, and the thread is read at request time.

A reply from Mastodon, a reply from Bluesky and a webmention from a blog are kept by Archival and shown as one thread under the post on your own site. Ana reply from Mastodon Kai reply from Bluesky Sam's blog webmention kept by Archival example.com/post/hello Replies · 3 12 likes · 4 boosts
  1. 1 Replies, likes and mentions arrive from wherever people already are, and Archival keeps them.
  2. 2 A carrier reads them when a visitor asks, and your page shows the thread.

Turned on in one file

Every protocol is configured the same way: name the fields of your objects that make up a post, and Archival does the rest. Everything it publishes is your content, read from the files already in your repo.

One more line, allow_mastodon_clients = true, lets Mastodon apps sign in to your accounts. Write it by hand, or ask the editor's task mode to add it for you. Remove the section and your site stops federating. Add it back and it picks up where it left off, followers and all.

archival_editor.toml
allow_mastodon_clients = true

[[activitypub]]
username = "blog"

[activitypub.actor]
object = "site"
summary = "bio"
icon = "logo"

[activitypub.objects.post]
name = "title"
content = "body"
published = "published_at"
featured = "pinned"

[atproto]

[atproto.objects.post]
content = "body"
published = "published_at"

[webmention]

[webmention.objects.post]
name = "title"
content = "body"
published = "published_at"
  1. 1 Mastodon apps: one line lets them sign in to the site's accounts.
  2. 2 The fediverse account: a handle on your domain and a profile from your site object.
  3. 3 Posts: the fields that make up each one. A boolean pins it.
  4. 4 Bluesky: the same post type, published from an account on your domain.
  5. 5 Webmention: receive with an empty section, send by mapping a post type.

Own your audience

Followers follow your domain. Redesign, rename your objects or go quiet for a year: the account stays put and everything it published is still there.

Part of the hosting

ActivityPub, the AT Protocol and Webmention are part of Archival's hosting, and every site we host gets all three.

Implemented as specified

We implement the protocols as written, so your site works with any app that follows them.

Still just a website

Your pages build to static HTML and your content lives in plain files in a git repo. The protocols publish from those same files.

Join the social web.

Start from a template, map your posts, and publish. Your site is followable in minutes.

Already on Archival? Add the section to archival_editor.toml, or ask task mode to do it for you.