wakoinc on Nostr: As a relay operator or a client? As a relay operator? I’m only a client, no ...
As a relay operator or a client?
As a relay operator? I’m only a client, no mirroring.
As a NostrGraph relay client? The relays change daily, some don’t connect, some change dns, some add whitelists or other similar. Or I add new ones.
Even with a list of relays, I had an issue a couple days ago where I didn’t get a bunch of events in real-time - so there was a few hours delay. Relays may not store or accept all events, like I have a few filters and reject larger events or reject after set rate limits - so knowing a simple list is not really enough.
I do broadcast events to around 20 relays, with rate limits and throttling, when a client of the relay publishes an event.
The above is why I think relay recommendations and such need to be based on data and not static configuration. Trust the data and not what is said to happen.
And any event aggregation needs performant ‘already exists’ checking.. I see at least 10x dupe events from relays than actual unique in practise.
As a relay operator? I’m only a client, no mirroring.
As a NostrGraph relay client? The relays change daily, some don’t connect, some change dns, some add whitelists or other similar. Or I add new ones.
Even with a list of relays, I had an issue a couple days ago where I didn’t get a bunch of events in real-time - so there was a few hours delay. Relays may not store or accept all events, like I have a few filters and reject larger events or reject after set rate limits - so knowing a simple list is not really enough.
I do broadcast events to around 20 relays, with rate limits and throttling, when a client of the relay publishes an event.
The above is why I think relay recommendations and such need to be based on data and not static configuration. Trust the data and not what is said to happen.
And any event aggregation needs performant ‘already exists’ checking.. I see at least 10x dupe events from relays than actual unique in practise.