[expiration, now]

Reply to this note

Please Login to reply.

Discussion

Literally just listened to you and nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s talking about this on the podcast while washing dishes. 😅

🤌 perfect timing.

Or expiration in the past, at least then i would know not to store it in nostrdb and just pass it around as an owned note in memory

is it logical to broadcast an expired event? why?

i think it won't work. for example in immortal relay, we just check if its expired or not. for expired ones we even don't broadcast them. other ones will be stored and broadcasted at the same time.

beacuse its not logical to broadcast expired events. also adding a third status of `now` is a little confusing since in the best situation we have only 1 sec.

Yeah, that's what I mean really, just expire "immediately" accounting for clock drift.

then there is a high possibility for it to get expired when relay process it. we can use a expiration of 10 secs for example or one minute. isn't that do the work?

expire: 0, i don’t want to store it

well this one needs to be defined in the spec.

Yeah it would be a way to make any event ephemeral

seems fun and useful for this kind of situation.

Unless we want expiring ephemeral events for some reason… then i guess you could just use an ephemeral kind

yes. we can define how someone should interpret the expiration on an ephemeral kind.