Loop/Architecture/Data Channels: Difference between revisions

Loop/Architecture/Data Channels (view source)

228 bytes added , 24 August 2015

→‎Text Messages: Extend implementations notes.

canmove, Confirmed users, Bureaucrats and Sysops emeriti

3,628

edits

@@ Line 38: / Line 38: @@
 * sentTimestamp: An ISO encoded date
-Note: Implementations are expected to handle their own received timestamp, so that messages are displayed in the correct order e.g. in case of clock skew across the two machines.
+Notes for implementations:
+* Implementations shall handle security concerns around not processing embedded HTML.
+* Implementations should handle their own received timestamp, so that messages are displayed in the correct order e.g. in case of clock skew across the two machines.
+* Implementations should handle linkifying URLs when the message is displayed. These shall not affect the transmitted content.