Fedify Branch Temple (JSR edition)

Even when the edition is on JSR, the sutra is the same. Whether the runtime is Node or Deno, the same library makes the same federation—this tower is the proof. It's pinned across the whole workspace at 2.3.1.

Look closely at the posted note. firstKnock pinned to draft-cavage, "revert once the issue is fixed"—the very same TODO as hollo's Diplomacy Office, down to the letter. Two halls know the same pain and post the same note. Federation interoperability is made of gatherings of small posted notes like these.

Highlights

• The userAgent is HackersPub/(version). ORIGIN is checked at startup for whether it begins with http(s)://
• Upstash's Redis forces IPv6 (family: 6)—even the storehouse key has its matters of address
• The postgres pool (max 20) is wider than the queue's concurrency (10)—because the branch temple's life and the hall's life drink from the same pond

A passage from the sutra

export const federation = await builder.build({
  kv,
  queue,
  origin: ORIGIN,
  // TODO: Revert to Fedify's default RFC 9421-first behavior once
  // https://github.com/bonfire-networks/activity_pub/issues/8 is fixed and
  // released.
  firstKnock: "draft-cavage-http-signatures-12",
  userAgent: {
    software: `HackersPub/${metadata.version}`,
    url: new URL(ORIGIN),
  },
});