Subnostr

just got the privileged events gating working on request handling on realy

next thing i want to do is add whitelisting that also extends to the follows of the follows of designated owner npubs

this requires a little more work because it needs to proactively gather those, so it actually literally will require me to create a little service that makes a query to a whole set of other relays to get them.

i think probably as well as the seed relay addresses i will hard code into it, it needs to also have an additional element where whenever it does get the - what i'm going to call "directory events" - relay lists, in/outboxes, profile metadata - it needs to add them to its list, so i really will need to add

and once it is able to find a load of relevant relays that hold these events, i can then extend this so that this "directory event" category when new events upload, the relay blastrs them out to all of the relays it has on the list

this will be a huge benefit to the network once several instances of realy are being used by several users across fairly distent nodes in the social graph, because clients will no longer struggle to find this metadata

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

also, once my relay has a database of all of the relay/inbox metadata of the follows of the follows of the owner of the relay, it can also pick up if privileged events are received they could be also actively propagated to the inboxes of the user in the recipient list

this would make it amply certain that users direct messages would be found by other users clients, if they use the in/outbox lists for fetching DMs

to be less noisy, also, it could keep a list of the times that it gets duplicate messages back from inboxes that it disables forwarding to that outbox because this means the client of the sender is already sending it... probably a short timeout like an hour or so since the last time the client sends this type of message

or, i mean, it's a bit noisy but it would really help get DMs working with outbox model

Reply to this note

Please Login to reply.

Discussion

No replies yet.