nostr:nprofile1qqsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsfqhde8 we wrote this based on relay.nsec.app idea. you may want to take a look or replace.
few months ago i had this idea with a lot of features specified for bunker, tonight o wrote it but i did remembered them exactly. if you (also nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7auvdel) have any ideas or feature requests that can make a relay better for bunker communication, please let me know on nostr or github. ๐ซกโก
> maybe some kind of auth for reading and subscribing to events? so only connected client and bunker can read their messages?
nostr:nevent1qqstx5qvsga3p5lgr6agwk7u7p2kznpxpjs4z2tantahf2mua8wvqgsppemhxue69uhkummn9ekx7mp0qgst4k7a55r4w2ee0pfqfr48fuh08tvjkx4vqlpafcw7c96w3nwfv2srqsqqqqqpfwsn9j
Login to reply
Replies (3)
Aside from only 24133 kind, what other benefits do you see with it?
Does it store these ephemeral events for awhile? We need that for nsec.app
Auth to read would break nsec.app bcs it wouldn't be able to monitor unanswered requests to send push notifications.
Focus on lowering latency as much as possible. Maybe ignore any req without kind and authors to reduce any irrelevant load.
Focus on stability, most bunkers use a single relay and if it's stuck then users are furious.
currently its only limits the kind, i was waiting for your ideas...
thanks a lot for your help. ill publish a new version in few hour with your suggestions and let you know. ๐ซกโก
nostr:nevent1qqsgj5k3rm9sv9ummme5pgxududz5m2ajru6fu72jwazalu7eje3r6sppemhxue69uhkummn9ekx7mp0qgst4k7a55r4w2ee0pfqfr48fuh08tvjkx4vqlpafcw7c96w3nwfv2srqsqqqqqpqn4fka