Damus
Open in Damus
Yousif #fuck_jews profile picture
Yousif #fuck_jews
@Yousif #fuck_jews
npub17jj948ae23uy3q7z2rwau9f2y5xsnc62g49xncyj2gfy0tndx7nsl25kx3npub
npub17jj948ae23uy3q7z2rwau9f2y5xsnc62g49xncyj2gfy0tndx7nsl25kx3@npub.cashlnurl
Relays (7)
  • wss://relay.primal.net/ – read & write
  • wss://purplepag.es/ – read & write
  • wss://relayable.org/ – read & write
  • wss://feeds.nostr.band/popular – read & write
  • wss://relay.roli.social/ – read & write
  • wss://relay.roadrunner.lat/ – read & write
  • wss://public-relay.swallow.solutions/ – read & write

Recent Notes

Yousif #fuck_jews profile picture
lets face it, managing tens or hundreds (at peeks) of sockets is server level territory complexity, though many field tested solutions exist for servers some still missed it up

vibing doesn't work because a.i. can't write things we didn't write before

there is no client standards/go-to-way of doing data piping yet @nevent1qgs...
Yousif #fuck_jews profile picture
idk just #thinking
lets call each nostr-filter shape we use a "channel"

per channel, lets declare "eose-plus" as undefined until real 'eose' arrive, then keeps set it to eose timestamp and adjust on latest "EVENT" received

each channel keeps <<pubkey | id>, eose-plus> map

when client requests an id, if its marked with an "eose-plus" then request '"since": <eose-plus>
append ids with similar eose-plus to for as less filters as possible IF they are still much compromise for full delivery

if current subscription isn't stable (no eose-plus) make a transitory subscription
when all subs are stable, merge to a single one with latest "since"

such setup suppose a service to control which ids to be forwarded or withdrawed