Feature request: user specific global message expiry time
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I wish there was an option to specify that messages I sent won't be stored for longer than a week as currently I have to enable exploding messages everywhere separately and that won't affect past messages.
In my opinion instant messengers, even for team chat, shouldn't be document storages. I also feel uncomfortable with the idea of Keybase storing my message history forever and I have understood that people joining the chat/channel are unable to read past messages only if they are of exploding variety.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the chat message retention and exploding-message handling, then determine how a per-user expiry would interact with existing past-message and channel-history behavior; done means the requested expiry applies consistently without requiring per-chat settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100