Also for longform articles

How are you doing it?

With

Deno

Not Found | Deno

The event is signed locally with created_at = publish time and handed off to a Deno Deploy hold-and-forward service, which persists it in Deno's key value database until due. A cron job runs every 60 seconds, picks up due events, and publishes them via WebSocket to the user's chosen relays. The Deno server only holds a fully signed event, verifies its signature, and forwards it at the scheduled moment.