Damus

Recent Notes

Mike Dilger ☑️ · 190w
I interpret kind 2 to say "Hey this is a great relay, you guys should try it", rather than "If you want to find my posts in the future, I expect to be putting them here". kind-2 also only has a singl...
princess_J20 profile picture
One idea: on initialization, clients try to open up websockets to a collection of relays. whichever ones successfully establish a connection are published as a parametrized replaceable event with a fixed Kind "K", with "d" tags equal to the URL of the relay. These events ideally would be "sprayed".

Then, as another user, I could query for kind "K" authored by the user I am interested and get the list of relays, with timestamps, they have connected to. By filtering the query I can get the most recent relays, etc.

Obvious privacy concerns. But a good client could prompt user before sending (i.e., "let people know you were using relay wss://XXX"?), and maybe you could set to not send such updates for certain relays.. etc..
1
Mike Dilger ☑️ · 190w
Interesting. This allows people to move around rapidly. However, what if I want someone's events spanning a longer time period? It's the same problem of following threads across multiple relays which isn't fully solved either.
Mike Dilger ☑️ · 191w
I like the idea, but a timestamp doesn't really indicate something has expired unless there is a policy to make a new one every N days. And 'nprofile' is defined in a NIP without having a timestamp, so you'd have to debate some people to have that changed. If you wanted the QR to contain things ot...
Colin Sullivan · 191w
Same
fiatjaf · 191w
I am using a client that doesn't render images inline and like to see the URLs I'm clicking.
SURF⚡️ · 191w
Interesting. Thank you. 🙏🏻