Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Maunium
synapse
Commits
a443d2a2
Unverified
Commit
a443d2a2
authored
5 years ago
by
Brendan Abolivier
Browse files
Options
Downloads
Patches
Plain Diff
Spell out that Synapse never purges the last event sent in a room
parent
88d41e94
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/message_retention_policies.md
+4
-0
4 additions, 0 deletions
docs/message_retention_policies.md
with
4 additions
and
0 deletions
docs/message_retention_policies.md
+
4
−
0
View file @
a443d2a2
...
@@ -42,6 +42,10 @@ purged according to its room's policy, then the receiving server will
...
@@ -42,6 +42,10 @@ purged according to its room's policy, then the receiving server will
process and store that event until it's picked up by the next purge job,
process and store that event until it's picked up by the next purge job,
though it will always hide it from clients.
though it will always hide it from clients.
With the current implementation of this feature, in order not to break
rooms, Synapse will never delete the last message sent to a room, and
will only hide it from clients.
## Server configuration
## Server configuration
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment