#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
mleku
npub1fj…mleku
2025-03-11 13:46:17
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2025-03-11 13:46:17Event JSON
{
"id": "9635f4e242179e84e3219a54b2e78b875fec3c19bfed277a0773d411566a9c37",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1741700777,
"kind": 1,
"tags": [
[
"t",
"realy"
],
[
"p",
"8125b911ed0e94dbe3008a0be48cfe5cd0c0b05923cfff917ae7e87da8400883"
],
[
"client",
"jumble"
]
],
"content": "#realy supports two very important nips that almost no others do\n\nnip-40 and nip-70\n\nthe 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\n\nsecond is protected events tag\n\nthis 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\n\nthese 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\n\nthey are already supported, and you can see that by going to https://mleku.realy.lol\n\nthis 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\n\njust another reminder that cares about what matters for privacy and utility of users\n\nbtw nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl heads up the edit widget currently does crazy things if you put a hashtag twice into it",
"sig": "46e0b726237df275fcd6b1af2fa00d51eb5c46fa972b7b5b1a37d921b81c02adff73586dcf2904b49c910c7c72444d1001011e58e9364fb543a6056761ad1de8"
}