Limit chat history to timestamp of joining?
Open
Nobody has claimed this yet.
enhancement
feature: api 🛠️
feature: chat 💬
feature: upload & shares & voice 📤🎙️
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
The question arose if the chat history could be limited to the point when a user was added.
In theory this should be possible easily:
- On adding we need to additionally store the message id
- When returning the chat we filter out all messages which are with a lower message id (on SQL as well as API)
- Similarly the shared items tab needs to be limited
Biggest open issue:
- Shares in the files app would need to be conditioned in the same way. That would be possible by also storing the timestamp of joining and putting a similar constraint on the share selection. However when a file/folder is shared again, we don't share it again but just repost the message. That would not make the share accessible as of yet. So that needs more thinking about a solution.
Contributor guide
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
Start by tracing the chat-history and shared-items retrieval paths described for SQL and the API, then inspect how the files app selects shares. Done means history and shared items are limited to the user's joining point, while reposted file or folder shares remain accessible according to an agreed solution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sql
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100