Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IRCv3 server-time support #511

Open
Mikaela opened this issue Oct 22, 2017 · 1 comment
Open

IRCv3 server-time support #511

Mikaela opened this issue Oct 22, 2017 · 1 comment
Labels
needs-spec T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.

Comments

@Mikaela
Copy link
Contributor

Mikaela commented Oct 22, 2017

When the client supports server-time and it's enabled, the IRC server includes timestamps when it received messages which clients should then show instead of their own timestamps.

I think Matrix behaves by just showing the first instance of the message received in the room and then distributing it to other participating homeservers with the same timestamps, so I think it could be said that Matrix is also using server-time on the Matrix side. I think using server-time, when available, would decrease how complex mapping messages across would be, but I am not a coder/developer and thus I am unsure.

The specification linked in the beginning also says:

Servers offering this capability for all messages SHOULD also offer the echo-message capability to allow clients to keep a consistent chronology of events.

but I think it's not possible to do with Matrix and at the time of writing WeeChat (native IRC client) doesn't support echo-message either while supporting server-time.

@Half-Shot
Copy link
Contributor

This needs a spec, as showing a user-defined timestamp on Matrix is not supported.

@justinbot justinbot added T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements. and removed feature-req labels May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-spec T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.
Projects
None yet
Development

No branches or pull requests

3 participants