Replying to Avatar Blake

Starting to break down a best practise way we can determine the best relays to publish events to based on context.

It’s not simple.. but if we break it down, we should be able to form patterns and make is easier.

Obviously the same needs to be done for querying the best relays when looking for an event too - I’ve started that as well.
Avatar
Blake 2y ago

The landscape may change in a few ways.

We may have dedicated (more centralised) relays to query only metadata events (kind 0/3/10005).

We may have dedicated indexing/aggregating relays (we have today, but used as generic relays) when you have little more than an event id. These could include event aggregates stats data.

We may have archival relays that host older content. Query if event is expected to be older than 3 months for example.

We will continue to have mass broadcast relays, when events need maximum reach.

And likely other specialty relays or services - like perhaps caching media from events like images that may break in the future.

Reply to this note

Please Login to reply.

Discussion

Avatar
Blake 2y ago

We can then try to best effort consolidate related events like for a channel or in a reply chain on the source relays. Doesn’t mean we have to, however it’s the best lead clients with no information have to follow first when querying.