summary refs log tree commit diff
diff options
context:
space:
mode:
authorPaul "LeoNerd" Evans <paul@matrix.org>2014-10-01 17:59:55 +0100
committerPaul "LeoNerd" Evans <paul@matrix.org>2014-10-01 17:59:55 +0100
commit5813e81dc65764cbb8862e49f619d6ff71e8e004 (patch)
tree942c0e3503576a7285faf3a27dbb7cf101776c5d
parents/m.room.redacted/m.room.redaction/ (diff)
downloadsynapse-5813e81dc65764cbb8862e49f619d6ff71e8e004.tar.xz
Move documented but-unimplemented 'presence idle times' into a new document to contain such features
-rw-r--r--docs/specification-NOTHAVE.rst20
-rw-r--r--docs/specification.rst8
2 files changed, 20 insertions, 8 deletions
diff --git a/docs/specification-NOTHAVE.rst b/docs/specification-NOTHAVE.rst
new file mode 100644

index 0000000000..6ed8298cd9 --- /dev/null +++ b/docs/specification-NOTHAVE.rst
@@ -0,0 +1,20 @@ +Matrix Specification NOTHAVEs +============================= + +This document contains sections of the main specification that have been +temporarily removed, because they specify intentions or aspirations that have +in no way yet been implemented. Rather than outright-deleting them, they have +been moved here so as to stand as an initial version for such time as they +become extant. + + +Presence +======== + +Idle Time +--------- +As well as the basic ``presence`` field, the presence information can also show +a sense of an "idle timer". This should be maintained individually by the +user's clients, and the home server can take the highest reported time as that +to report. When a user is offline, the home server can still report when the +user was last seen online. diff --git a/docs/specification.rst b/docs/specification.rst
index 6fe72da224..84801b7d65 100644 --- a/docs/specification.rst +++ b/docs/specification.rst
@@ -1497,14 +1497,6 @@ in the other direction will not). This timestamp is presented via a key called ``last_active_ago``, which gives the relative number of miliseconds since the message is generated/emitted, that the user was last seen active. -Idle Time ---------- -As well as the basic ``presence`` field, the presence information can also show -a sense of an "idle timer". This should be maintained individually by the -user's clients, and the home server can take the highest reported time as that -to report. When a user is offline, the home server can still report when the -user was last seen online. - Transmission ------------ .. NOTE::