Replying to Avatar PABLOF7z

I'm considering adding a "relay-set router" to NDK.

This would give developers the ability of providing certain policies to route both event fetching and publishing to a particular set of relays, overriding the default calculation. It could (or not) include in the information the router receives the selection that NDK has done, including what it wants to do per the outbox model.

I want to use it for an application that I'm making that creates certain kind of special events and with this I could create a router that says:

"whenever you fetch/publish kind XXX, send it to only these relays"

"whenever you fetch/publish kind 0, include PurplePages, otherwise don't include PurplePages"

Does anybody find this interesting or useful?

Avatar
Sebastix 2y ago

This makes sense to me for kind-focused relays like your purplepages. So the routing depends on which kind of event needs to be broadcasted right? This will also incentify building more niche relays focused on handling one or more kinds really good (also decentralization will increase of the network imo)

Reply to this note

Please Login to reply.

Discussion

Avatar
PABLOF7z 2y ago

Exactly what I’m thinking

Avatar
Sebastix 2y ago

Build it, I will test it for sure (with a own configured relay besides)! 😃

Thread collapsed
Thread collapsed