Add date and time to quotes #499

Closed
opened 2 years ago by Positron · 3 comments
Positron commented 2 years ago

Sometimes it is required to scroll back in history and quote a statement made in a MUC earlier as described here:

kriztan/Pix-Art-Messenger#378

Furthermore, it is useful to add date and time to the quote header indicating the time the statement was made,
esp. after several days back in time.
This allows other participants can scroll back in time to see the context close to the statement.

e.g.
UserX wrote on 2020-08-29 at 15:12 UTC:

quoted statement here

Own response here
..

If the quoting person does not want not to give away his own timezone
the date should in in ISO 8601 and time should be in UTC.

If the quoting persion wants to do it, date and time can be in his local date/time format.

This requires a switch in the security settings. Date and time for quotes in local time or UTC.

Instead of the date the words today and yesterday are useful when applicable.

Sometimes it is required to scroll back in history and quote a statement made in a MUC earlier as described here: https://codeberg.org/kriztan/Pix-Art-Messenger/issues/378 Furthermore, it is useful to add date and time to the quote header indicating the time the statement was made, esp. after several days back in time. This allows other participants can scroll back in time to see the context close to the statement. e.g. UserX wrote `on 2020-08-29 at 15:12 UTC`: > quoted statement here Own response here .. If the quoting person does not want not to give away his own timezone the date should in in ISO 8601 and time should be in UTC. If the quoting persion wants to do it, date and time can be in his local date/time format. This requires a switch in the security settings. Date and time for quotes in local time or UTC. Instead of the date the words today and yesterday are useful when applicable.
kriztan added the
Enhancement
UI
labels 2 years ago
Echolon changed title from [FR] Adding date and time to quotes to Add date and time to quotes 1 year ago
bttr commented 1 year ago

Not sure, if I would want it this way. It makes the quoting introduction very long. Bad idea for a mobile in portrait mode.

At least a little shorter:
not: UserX wrote on 2020-08-29 at 15:12 UTC:
but: UserX (2020-08-29T15:12 UTC):
or: UserX 2020-08-29T15:12 UTC:

Not sure, if I would want it this way. It makes the quoting introduction very long. Bad idea for a mobile in portrait mode. At least a little shorter: not: `UserX wrote on 2020-08-29 at 15:12 UTC:` but: `UserX (2020-08-29T15:12 UTC):` or: `UserX 2020-08-29T15:12 UTC:`

The idea itself is good, but it definitely needs to be polished.
Firstly, in my opinion, the year would have to go as it is way too lenghty. Maybe it would appear when you quote messages from another year, but that happens like never so I don't know if it's useful at all.
Secondly, i don't think it's good to add a setting where you use your own time format. Because users are from all over the world, and if you quote a message from multiple hours ago and their time is different than yours, they won't know when it was and can't find the message easily.
Thirdly, I wouldn't use any writes or wrote or any verbs, as 1. it is a different word for almost every language, and 2. some languages intergrate the sex in the verb but you don't know who you're talking with (that's what I said in #557 too).

The idea itself is good, but it definitely needs to be polished. Firstly, in my opinion, the year would have to go as it is way too lenghty. Maybe it would appear when you quote messages from another year, but that happens like never so I don't know if it's useful at all. Secondly, i don't think it's good to add a setting where you use your own time format. Because users are from all over the world, and if you quote a message from multiple hours ago and their time is different than yours, they won't know when it was and can't find the message easily. Thirdly, I wouldn't use any writes or wrote or any verbs, as 1. it is a different word for almost every language, and 2. some languages intergrate the sex in the verb but you don't know who you're talking with (that's what I said in #557 too).

But actually, thinking in a more detailed way about how your issue could be realised, Blabber.im can't really do this. Not alone and not just as an app.
Because the time formats are often different internationally: It's 24.8. for some, 24/8/ for other, 08/24 for others and so on. It'd be even more confusing for international readers of quotes from the Blabber.im app.
Even if you use UTC, there are other differences, and not just with the date but also the time (for example some say AM and PM and some go to 23:59). Today and yesterday also wouldn't work for international readers.

The only solution I can think of (through the help of a certain someone ;) ) is in a XEP which a couple of clients, all of them at best, integrate. It would probably put a universal time format into the metadata of each message and then each clients supporting the XEP would read that date and time metadata and show it in the right time and format the recipient sets it to show in their client, or by the location of the user or something else.
I hope you understand only Blabber.im doing this wouldn't help and would just cause more confusion when people with different timezones meet.

But actually, thinking in a more detailed way about how your issue could be realised, Blabber.im can't really do this. Not alone and not just as an app. Because the time formats are often different internationally: It's 24.8. for some, 24/8/ for other, 08/24 for others and so on. It'd be even more confusing for international readers of quotes from the Blabber.im app. Even if you use UTC, there are other differences, and not just with the date but also the time (for example some say AM and PM and some go to 23:59). Today and yesterday also wouldn't work for international readers. The only solution I can think of (through the help of a certain someone ;) ) is in a XEP which a couple of clients, all of them at best, integrate. It would probably put a universal time format into the metadata of each message and then each clients supporting the XEP would read that date and time metadata and show it in the right time and format the recipient sets it to show in their client, or by the location of the user or something else. I hope you understand only Blabber.im doing this wouldn't help and would just cause more confusion when people with different timezones meet.
kriztan added this to the 3.1.0 milestone 8 months ago
kriztan referenced this issue from a commit 7 months ago
kriztan closed this issue 7 months ago
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.