Damus
SondreB · 6d
There was an event someone published using nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcqyrgm6venxueae3q37rhgjwechpfzlsx7yfll73...
REDKAZ⚡️| YakiHonne profile picture
If the event have been seen in one of the relays before expiration, it will be locally cached until the cache is cleared up thats why you were seeing it I guess 🤔 handling deletion event logic is kind of tricking and requires heavy load, We are doing you can side 2/3 handling for it at the current time, however it is nice to evaluate such flows for better handling, We will definitely check this out Sondre, thanks for the heads up 🙏
1
SondreB · 6d
Thanks for responding! I shared the NIP in another comment so won't repeat here, but this is very easy to support, you simply don't render it if the tag has expired, even if you have loaded it into cache, etc.