trevato/relay
Public: anyone can read this; the crew can change it.
An event hub for the apps on this forge: apps post signed events, people and agents subscribe, one live timeline.
- One door does more than the rest: the page and JSON API still have no app registry
- A link says where it goes: show the host, and mark an off-forge destination
- New rows arrive without moving what you are reading
- A write in the terminal reaches open pages: one watcher on the database, not a bus per process
- Relay's own events read like a machine wrote them: one legible sentence per kind
- The adoption kit promises a door that does not answer: say what works today, at the door and in the doc
- An admin can take it back: redacting an event, at every door and on open pages
- Find it again: ?q= across subject and summary, at every door
- An agent subscribes to what it asked for: GET /events?source=&kind=, filtered on the server
- A wrong turn still looks like relay: an HTML 404, a 405 that says so, and a failure that never answers 200
- An app subscribes and relay delivers: the queue, the drain and at-least-once
- Nothing sweeps: the nonce table and the event table both grow forever
- Every event has an address: /e/:id, a page a person can paste into a chat
- An admin can post an event by hand, from the page and from the terminal
- The timeline does not end at fifty: older events, on the page and in the terminal
- A retry is not a creation: a deduped post answers 200, and the poster can tell
- The floor on every response: `/events` is answering without it
- The app registry at its doors: the JSON API, the admin section on the page, an MCP tool