been working on the massive rewrite/cleanup of #realy this afternoon, getting quite excited
i've stripped it back hard and built some nice things like registries for http handlers/middleware and event publishing (to subscribers)
currently refactoring the access control configuration to work with a HTTP API accessible configuration method that allows you to read and write the configuration settings dynamically... this means that the actual configuration part for the runtime is tiny, and anyone with a web browser and a tool to make expiring variant NIP-98 auth headers can at minimum configure their relay, just one difficult bit, the actual auth
i expect that later i will scrape together a simple web interface that has a form with all the fields of the configuration and works with a signer like alby or nos2x and do it even simpler, but getting it working so it's dynamically configurable is a big deal, even if at the simplest level of UI i can make
one of the fundamental concepts that i fully grasped once i grappled with making HTTP REST APIs is that a relay is a web server, albeit in the legacy form it is a websocket server, which greatly complicates implementation, which means that i probably will gradually get familiar with building at least simple administrative interfaces to make using my stuff easier for relatively n00b users, which i think is very important for nostr to gain wider acceptance while staying decentralised, moar relay runners, it's the new node runner
mleku
npub1fj…mleku
2025-04-17 17:56:08
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2025-04-17 17:56:08Event JSON
{
"id": "07e9d71de7770ef241e93bba896c7601cfee26e5733d4be3529bd4d992fb97e3",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1744912568,
"kind": 1,
"tags": [
[
"t",
"realy"
],
[
"client",
"jumble"
]
],
"content": "been working on the massive rewrite/cleanup of #realy this afternoon, getting quite excited\n\ni've stripped it back hard and built some nice things like registries for http handlers/middleware and event publishing (to subscribers)\n\ncurrently refactoring the access control configuration to work with a HTTP API accessible configuration method that allows you to read and write the configuration settings dynamically... this means that the actual configuration part for the runtime is tiny, and anyone with a web browser and a tool to make expiring variant NIP-98 auth headers can at minimum configure their relay, just one difficult bit, the actual auth\n\ni expect that later i will scrape together a simple web interface that has a form with all the fields of the configuration and works with a signer like alby or nos2x and do it even simpler, but getting it working so it's dynamically configurable is a big deal, even if at the simplest level of UI i can make\n\none of the fundamental concepts that i fully grasped once i grappled with making HTTP REST APIs is that a relay is a web server, albeit in the legacy form it is a websocket server, which greatly complicates implementation, which means that i probably will gradually get familiar with building at least simple administrative interfaces to make using my stuff easier for relatively n00b users, which i think is very important for nostr to gain wider acceptance while staying decentralised, moar relay runners, it's the new node runner",
"sig": "b376becde72cf2e751469f8bded2a44b4d82c99912d7c73051ca03e906a34c8503156cbf7c3d790cd8f67e18c9da5c3c4743d053ed1202f2abf56885863d8c16"
}