Skip to content

Considering ActivityPub support

I looked into ActivityPub support for 6umi. Nothing is implemented yet. This post covers the basics and how it might connect to 6umi.

What ActivityPub is

  • A standard for exchanging posts, follows, and so on between separate servers. A W3C Recommendation (January 2018)
  • The parties in these exchanges are actors (roughly, accounts). Each actor has an inbox for receiving and an outbox for sending
  • When an account on server A follows an actor on server B, B sends that actor's posts to A. The set of servers connected this way is called the Fediverse
  • Source: https://www.w3.org/TR/activitypub/

Mastodon and Misskey

Both are server software that speaks ActivityPub. Within the federation, they can follow each other.

  • Mastodon: From Germany (2016–). The largest implementation in the Fediverse. Its client API (the API apps use to talk to the server) is the de facto standard, and many apps and web UIs support it
  • Misskey: From Japan (2014–). Lots of playful features, such as emoji reactions, custom emoji, and its own markup (MFM). Its client API is entirely different from Mastodon's
  • Culturally and feature-wise, Misskey seems a better fit for 6umi than Mastodon

Two layers

"Lean toward Misskey" or "lean toward Mastodon" means different things depending on which layer you're talking about.

Layer What it determines Leaning toward Misskey
Federation (ActivityPub) Exchanges with outside servers No problem. Misskey extensions such as reactions and quotes can be carried too
client API Which apps and UIs can read and write Not worth it. It's a custom RPC with hundreds of endpoints that change from version to version
UI Look and feel Misskey's web UI doesn't work without Misskey itself
  • To reuse an existing UI, go with the Mastodon family (Elk, Phanpy; both MIT). That means putting a Mastodon-compatible layer on top of 6umi's API
  • The Misskey feel (reactions, custom emoji) can come from federation and our own UI, not from the client API

If we connected it to 6umi (draft)

flowchart LR
  subgraph six["6umi"]
    kz["くずは風 UI"] --> api["6umi の API"]
    elk["Mastodon 系の UI<br/>(流用する場合)"] -.->|Mastodon 互換の層| api
    api --- board["板 = Group actor"]
  end
  board <-->|ActivityPub| mstdn["Mastodon"]
  board <-->|ActivityPub| mk["Misskey"]
  mstdn --- mui["Mastodon の UI・アプリ"]
  mk --- mkui["Misskey の UI"]
  • Board = Group actor. Following a board delivers its posts. Anonymous posts are not turned into per-poster actors
    • Prior examples: Lemmy (communities as Groups), NodeBB (categories as Groups)
    • I couldn't find any example of anonymous posts being sent into the federation
  • Stages
    1. Publishing only: board actors, accepting follows, delivering posts
    2. Receiving: put replies and reactions from outside onto the board. This can merge the current cross-posting to Misskey and Bluesky and the importing of replies into a single mechanism
    3. More actors: bots as individual actors, tags as Groups
    4. Federation between boards: self-hosted boards (the OSS version) connecting to each other
  • The first goal is connectivity: following a board from a Misskey account and getting its posts delivered

Decisions

  • Before building a modern UI, look into whether existing UIs for Misskey and Mastodon can be reused
  • First finish everything other than the modern UI, that is, the API and a minimal UI

Created 2026-10-16 · Updated 2026-10-17 · Machine-translated from the Japanese original.