Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Profanity shows old messages as new when connecting to some MUC #1254
Old messages are not shown as new but are in the right place of the timeline.
In some MUC (on server running Openfire 4.5.0), after connect old messages are shown as just received with the current date and time (not in Profanity MUC).
Here some log (
This bug concern dev version (and does not occur in the stable release 0.7.1).
Tested on Arch Linux and Debian Buster.
So far we got the first delay with a from that comes from the server. This way we know it's MUC history. Now we take the first time stamp we actually find. Which is likely the one being added first. And should contain the correct time to display. It would be nicer to actually compare the dates though. Regards #1254
So far we saved the timestamp which also had the `from`. But we need this only to find out whether it's MUC history. For displaying we should use the oldest delay timestamp. Also in 61f6696#diff-4926fd4577a336bd3eb240f8104a5c5bL837 a error was introduced. Before we saved the timestamp in all cases. And only if timestamp AND from was given we went into MUC history case. Normal timestamp saving was not done anymore only if it also had a from attribute. Regards #1254
Do you mean that messages that were sent while you were offline (to a MUC) are later displayed as regular messages and not as MUC history?
Or are you saying the date/time of all MUC messages is wrong?
Also does this only happen to you on that openfire server?
I joining some MUC when connecting to my account.
For test this, I just
https://xmpp.org/extensions/xep-0045.html#enter-history sais "The 'from' attribute MUST be set to the JID of the room itself."
Maybe an openfire problem?
I created a bug for openfire: https://discourse.igniterealtime.org/t/maybe-muc-history-bug/87165