-
Notifications
You must be signed in to change notification settings - Fork 706
NIP-17: Expiration preferences #2028
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
NIP-17: Expiration preferences #2028
Conversation
Seems ok to me. Do you think people would want to override their preference per conversation? |
Each user can have a different preference. We don't need to override each other. |
I mean per conversation. I might have a "note to self" that I don't want to expire, or a particular conversation that I want to expire very quickly. |
Ohh.. yeah.. no idea how to integrate that |
I also tend to prefer disappearing messages for individual conversations. For example, if a kind14/15 event has an expiration time, then that sets the conversation? - This is also the approach used by 0xchat. |
Ohhh interesting... So, like the Do people actually have different expirations per conversation? It feels hard to keep in mind that certain things disappear faster than others. |
This is how Signal works, I don't think they even have an option to set it globally. |
Yep, but do people actually use it? Or is it just overengineered? |
I don't really use it, but a lot of privacy-conscious people I chat with do |
Seems reasonable to me. |
Trying to see if there is an appetite for formal disappearing messages in NIP-17.
By adding a setting to the relay list event, each user can make their own chat disappear at a fixed schedule. If enough people implement this feature, it would delete sent and received messages together, avoiding the weird UX of my messages disappearing while other users' messages stay.
Each user can then have their own choice.