Laeserin @Laeserin - 3mo
Disappearing notes is extremely normie-friendly. #JustSaying #GrowNostr
Transaction Heaven, where the missing LN transfers go. Please try to keep up.
Yeah. 😂 I sometimes see the same old note when loading my app, for like weeks. Shitposts from the distant past.
I think they're the only ones that have it. This is one of those killer features, like pins, that seem to go nowhere. 🤷♀️
Notes with an expiration date, after which the author doesn't expect them to be saved and the clients hide them and the relays may delete them. The difference is that, if a relay deletes an expiring event, they free up disk space. So, saying in advance that you want something to expire does relay owners a favor because they don't have to save a delete event.
NIP-09 deletion events work like so: "Relays SHOULD delete or stop publishing any referenced events that have an identical pubkey as the deletion request. Clients SHOULD hide or otherwise indicate a deletion status for referenced events. Relays SHOULD continue to publish/share the deletion events indefinitely, as clients may already have the event that's intended to be deleted. Additionally, clients SHOULD broadcast deletion events to other relays which don't have it."
NIP-40 expiration timestamps work like so: "Relays MAY NOT delete expired messages immediately on expiration and MAY persist them indefinitely. Relays SHOULD NOT send expired events to clients, even if they are stored. Relays SHOULD drop any events that are published to them if they are expired."
Niel Liesmons @nielliesmons - 3mo
Yes. Waaaay easier to do on community relays btw 💪
Lol, I'll stop here. Half of my posts are just "Community Relays fixes this" at this point 😂 .
Well, you actually need a client to produce notes with an expiration time stamp, and then you need a relay to support expiration time stamps, as only those relays can handle that tag. nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h can theforest accept disappearing notes?
You don't need to save anything on your relay, to prevent the event from being rewritten, because they timestamp informs you that it's expired and you can just auto-reject any attempt to write expired notes.
In this case, deletion doesn't free up disc space, as you have to keep the deletion event, to keep the original event from reappearing. And some relays keep both events, and use the deletion event to suppress the publishing of the original event. In both cases, you are stuck storing the deletion event, which is a sort of data spam.
True. Although ~~relays~~ communities can have their own defaults per event kind. I wouldn't keep chat messages long term in most of my communities for example. (incentivising using long term formats for long term stuff)
Yeah, agree. Like, we use disappearing posts in our SimpleX chat and stuff gets auto-hidden by Slack after 90 days, so we put important project docs in git or long-form notes on GitCitadel relay. If you know it'll disappear, and you think it's important, put it in a different kind of event or store it on a relay that won't hard delete it. Some of us might end up working on these projects for years and it'll quickly become millions of spammy notes. That can happen surprisingly fast, if you have a big group, like we do. Don't nobody need all that.
Yup, in communities all of this is way clearer for the user anyway. You say "GM" in the chat, not in a forum post 🤦♂️.
This guy is in the chat 24/7 😂
Nothing is forever.
Hey, did you get my zap? Trying out a new zap setup.
Nein :/
This is literally just an expiration tag the author could add to any kind. It's not censorship to request your own stuff be removed.
