Fixed in 9ef234b: MatrixReading.text takes the messages newest first, as the room gives them, and prints them oldest first; MatrixReadingTest "each message is a block of time, sender, event ID…
Fixed in 9ef234b: ReadRequest carries the caller's zone through control.sock, and the times print in it. The socket is a local Unix socket, so the relay runs on the same machine, but its…
Fixed in 9ef234b: an event before --since TIME is skipped, and only 20 such events in a row end the reading, so an older time stamp among newer ones no longer stops it. Test: MatrixReaderTest…
Fixed in 751fdd5: Scenario#100.01, the Solution and the help text say that SENT comes without the event ID when the outbox gave the message up before the client saw it; the README said so…
Olm encrypts only to-device events; Trixnity has no Olm content for room events (OlmEncryptedToDeviceEventContent only). Still, candidate now takes EncryptedMessageEventContent of any…
Not a finding: m.relates_to stays cleartext in an encrypted event (Matrix spec, end-to-end encryption and relations), so an encrypted reaction carries its RelatesTo.Annotation outside the…
Fixed in f54ad51: with --since EVENT_ID the reading looks for the event beyond the limit and fails if it is not among the last 500 events; it keeps the newest limit messages after it. Test:…
Fixed in f54ad51: matrix send refuses more than one text argument with its usage, exit code 2. Test: MainTest "matrix send needs room and text, none of them blank".
Not a finding: in Kotlin a $ that no identifier or { follows is a literal, so "$" compiles. The build of 254fdc9 is green, with MatrixReadingTest and MainTest using --since $e. No…