mleku on Nostr: #realy supports two very important nips that almost no others do nip-40 and nip-70 ...
#realy supports two very important nips that almost no others do
nip-40 and nip-70
the first is expiration timestamps, and the query engine as it is already, if it finds an expiration timestamp on an event that is past, it deletes the event if it comes up in a query
second is protected events tag
this is an event tag, literally just a "-" that indicates that if the relay has auth enabled that this event can only be stored if the auth matches the author pubkey
these are both very important ideas for supporting private relays and enabling private communities, as well as expiring messages, like what many messengers have, such as telegram
they are already supported, and you can see that by going to https://mleku.realy.lol
this will also be available at the `/relayinfo` endpoint later and when there is a realy build that only does http it will only be available on that endpoint, and it can also currently be seen by adding the "Accept: application/nostr+json" header to a normal HTTP query for https://mleku.realy.lol
just another reminder that cares about what matters for privacy and utility of users
btw cody (npub1syj…f6wl) heads up the edit widget currently does crazy things if you put a hashtag twice into it
nip-40 and nip-70
the first is expiration timestamps, and the query engine as it is already, if it finds an expiration timestamp on an event that is past, it deletes the event if it comes up in a query
second is protected events tag
this is an event tag, literally just a "-" that indicates that if the relay has auth enabled that this event can only be stored if the auth matches the author pubkey
these are both very important ideas for supporting private relays and enabling private communities, as well as expiring messages, like what many messengers have, such as telegram
they are already supported, and you can see that by going to https://mleku.realy.lol
this will also be available at the `/relayinfo` endpoint later and when there is a realy build that only does http it will only be available on that endpoint, and it can also currently be seen by adding the "Accept: application/nostr+json" header to a normal HTTP query for https://mleku.realy.lol
just another reminder that cares about what matters for privacy and utility of users
btw cody (npub1syj…f6wl) heads up the edit widget currently does crazy things if you put a hashtag twice into it