Compare commits

...

2 Commits

Author SHA1 Message Date
f383701f9e
m.room.retention: add the expire_on_clients option
I doubt anything implements it, but hopefully Synapse implementation contains it
2022-05-17 23:10:23 +03:00
48773d2d4a
m.room.retention/README.md: mention not being on spec, add MSC link 2022-05-17 23:09:52 +03:00
5 changed files with 9 additions and 4 deletions

View File

@ -1,4 +1,5 @@
{ {
"min_lifetime": 3600000, "min_lifetime": 3600000,
"max_lifetime": 3600000 "max_lifetime": 3600000,
"expire_on_clients": true
} }

View File

@ -1,4 +1,5 @@
{ {
"min_lifetime": 86400000, "min_lifetime": 86400000,
"max_lifetime": 86400000 "max_lifetime": 86400000,
"expire_on_clients": true
} }

View File

@ -1,4 +1,5 @@
{ {
"min_lifetime": 86400000, "min_lifetime": 86400000,
"max_lifetime": 2678400000 "max_lifetime": 2678400000,
"expire_on_clients": true
} }

View File

@ -6,6 +6,7 @@ Read that, it explains what is actually done etc.
## Notes ## Notes
* Not part of spec. https://github.com/matrix-org/matrix-spec-proposals/pull/1763
* Matrix uses milliseconds, keep that in mind! * Matrix uses milliseconds, keep that in mind!
* Everything requires every server involved to have rention support enabled, * Everything requires every server involved to have rention support enabled,
otherwise the messages go nowhere and are fetchable upon request. otherwise the messages go nowhere and are fetchable upon request.

View File

@ -1,4 +1,5 @@
{ {
"min_lifetime": 86400000, "min_lifetime": 86400000,
"max_lifetime": 604800000 "max_lifetime": 604800000,
"expire_on_clients": true
} }