Add public nostr submission relay and approved-content sync #705
No Reviewers
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
Infrastructure metrics, alerts, notifications, etc.
service
discourse
Kosmos Community Forums
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
lightning
Lightning address, lndhub, etc.
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
All your base are belong to us
User interface, process design, etc.
This won't be fixed
release
major
release
minor
release
patch
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#705
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds a second strfry instance and the machinery that promotes moderated content into the members relay, for raucao/marco#97.
A new
role[strfry_submission]plus thekosmos_strfry_submissioncookbook run a separate relay on port 7778 with its own database (capped at a 4 GiB mapsize), fronted atsubmit.nostr.kosmos.org. Its write policy is the open submission policy from akkountsextras/strfry. It is deliberately notrole[strfry], so nginx never adds it to the members relay's_strfryupstream.Two promotion paths feed the production database:
kosmos_strfry::approved_syncruns a dedicated fail-closed sync config and a five-minute timer that pulls moderator-approved content from the nuc staging relay into the members relay. Thestrfry syncURL andSTAGING_RELAY_URLare both derived from a single node attribute, so the policy's byte-exact source match cannot drift.kosmos_strfry::member_bridgeruns a live one-waystrfry router(dir = "down") that subscribes to the local submission relay on loopback and writes member-authored events into the production LMDB, gated per event by the LDAP-only write policy (ldap-only-policy.ts), so no member list is maintained.Also included: a role-scoped Node 24 install (the global Node attribute is left untouched; blossom and substr were checked and do not depend on Node), a firewall rule scoped to the openresty proxy nodes, an nginx site using
tls_cert_for(gandi_dns), a runbook, and two render regression checks — one that fails if the sync template's age floor is0, one that fails if the member bridge is not one-way or not LDAP-gated.Status: deployed to production. The relay is live at
wss://submit.nostr.kosmos.org(NIP-11 nameKosmos submission relay), both promotion paths are enabled viarole[strfry_submission], and the akkountslivepolicy files and the DNS CNAME are in place.doc/nostr-submission-relay.mddocuments the deployed layout and rollback.8b8dd42b48to8c0c7a3ca18c0c7a3ca1to511a512908