Opened 9 years ago

Last modified 4 years ago

#10720 new defect

Date change not displayed in log files spanning multiple days

Reported by: piggin Owned by: deryni
Milestone: Component: libpurple
Version: 2.6.3 Keywords: time stamp timestamp date chat window log file logfile
Cc:

Description (last modified by piggin)

Date change isn't added to time stamps in log files spanning multiple days (confirmed only for XMPP/Jabber/Gtalk, MSN, and Yahoo; please test other protocols) - however, it appears in the chat window. Here's an example:

Chat window:

(10:39:47 PM) smurfie: and I'm not available till tomorrow night
(10/10/2009 09:28:02 PM) dildo: you there?
(10:00:20 PM) dildo: let me know when you're back
(10/11/2009 11:08:41 PM) dildo: hello?
(11:13:52 PM) smurfie: back

Log file version:

(10:39:47 PM) smurfie: and I'm not available till tomorrow night
(09:28:02 PM) dildo: you there?
(10:00:20 PM) dildo: let me know when you're back
(11:08:41 PM) dildo: hello?
(11:13:52 PM) smurfie: back

Change History (14)

comment:1 Changed 9 years ago by darkrain42

  • Component changed from XMPP to pidgin (gtk)
  • Status changed from new to pending

I believe the timestamp plugin allows you to do this.

comment:2 follow-up: Changed 9 years ago by darkrain42

  • Status changed from pending to new

Nevermind, I was wrong.

comment:3 in reply to: ↑ 2 Changed 9 years ago by piggin

Replying to darkrain42:

Nevermind, I was wrong.

Why do you recommend it as "pidgin (gtk)" instead of "XMPP"?

comment:4 follow-ups: Changed 9 years ago by darkrain42

  • Component changed from pidgin (gtk) to libpurple

Because this is a Pidgin (or actually, probably libpurple now that I think about it) issue.

the protocol plugins (in this case, the XMPP one) have nothing to do with how the logs are written.

comment:5 in reply to: ↑ 4 Changed 9 years ago by piggin

Replying to darkrain42:

But then it's strange that this should happen only with XMPP. It's like each protocol has its own log management. So that's why I assumed it was an XMPP problem.

comment:6 in reply to: ↑ 4 ; follow-up: Changed 9 years ago by piggin

But then it's strange that this should happen only with XMPP. It's like some protocols have their own log management. So that's why I assumed it was an XMPP problem. (Corrected.)

comment:7 in reply to: ↑ 6 ; follow-up: Changed 9 years ago by darkrain42

  • Status changed from new to pending

Replying to piggin:

But then it's strange that this should happen only with XMPP. It's like some protocols have their own log management. So that's why I assumed it was an XMPP problem. (Corrected.)

What other protocols does it not occur for? (and are you comparing chats with IMs?)

comment:8 in reply to: ↑ 7 ; follow-up: Changed 9 years ago by piggin

  • Status changed from pending to new

Replying to darkrain42:

What other protocols does it not occur for? (and are you comparing chats with IMs?)

Here's a list of all the protocols available in my Pidgin that are not XMPP: AIM, Bonjour, Gadu-Gadu, GroupWise?, ICQ, IRC, MSN, MySpaceIM, QQ, SILC, SIMPLE, Sametime, Yahoo, Zephyr.

And no, I'm not comparing chats to IMs. Such a comparison would be irrelevant, as the two may indeed be managed differently, which would render the argument in my previous message invalid. It would be like comparing apples to oranges, although this analogy does not do justice to the difference between chats and IMs, as it always makes sense to compare apples to oranges when a fair comparison is made (for example one prefers oranges because one finds good oranges better than good apples, and average oranges better than average apples, and bad oranges better than bad apples; as you can see, the comparison makes sense because similar-quality products are compared based on the same person's taste), whereas comparing chats to IMs with respect to my reported bug is invalid and useless (not to emphasize that it would be a broken bug report, if not pretty dumb).

In other words, I'm comparing IMs to IMs and chats to chats, both of which don't work with XMPP, while they both work (and always have, to my testing) with other protocols *on the same Pidgin*.

comment:9 in reply to: ↑ 8 ; follow-ups: Changed 9 years ago by darkrain42

  • Status changed from new to pending

Replying to piggin:

Replying to darkrain42:

What other protocols does it not occur for? (and are you comparing chats with IMs?)

<snip>

You didn't actually answer the first question in amongst your rant.

And, with all due respect, the second question was valid. I did not know what assumptions you have or have not made about how logging works. In fact, the logging is very unified, so comparing one to the other would be (as a first order approximation) valid.

While it does not directly replicate what you are attempting to accomplish, the Message Timestamp Formats plugin will allow you to have date information for every line of chats/IMs.

comment:10 in reply to: ↑ 9 Changed 9 years ago by piggin

  • Status changed from pending to new

Replying to darkrain42:

Replying to piggin:

Replying to darkrain42:

What other protocols does it not occur for? (and are you comparing chats with IMs?)

<snip>

You didn't actually answer the first question in amongst your rant.

I answered it by showing you a list of non-XMPP protocols. I didn't test them, if this is what you wanted to know (it would be difficult, at least because they are too many), that's why I couldn't tell you which other protocols it did not occur for. Perhaps the only thing I could do was to name only the very few ones I could *confirm* were not affected by this bug (but I knew it would have been irrelevant).

I'm not sure I understand what you're calling a rant. If you're talking about my explanation, it was NOT a rant. I just tried an analogy that may admittedly have gone a bit insane because I tried to make it sound as accurate and fair as I could. "Comparing apples to oranges" is indeed an improper expression; it didn't serve my purpose too well.

And, with all due respect, the second question was valid. I did not know what assumptions you have or have not made about how logging works. In fact, the logging is very unified, so comparing one to the other would be (as a first order approximation) valid.

I didn't say your question was invalid, but that my comment would've been invalid if I'd said "yes". Your question was valid and I answered "no". Then I tried to show how a "yes" would've made my bug report (and especially a particular comment in my previous message) invalid. I was implying something like this: "a *potential* difference between chat and IM logging managements would have been my first suspect, which would have been the first for me to disambiguate away before invoking (and then reinsisting on) any hypothetical interprotocol differences (especially after you'd already explicitly rejected such a hypothesis), as I did in my previous message, so I couldn't have confused them".

While it does not directly replicate what you are attempting to accomplish, the Message Timestamp Formats plugin will allow you to have date information for every line of chats/IMs.

I don't know where to find that plugin. I have a "Timestamp" plugin, but it's very different from what you're describing ("Display iChat-style timestamps every N minutes"). Or is it some recent addition to the 30+ plugins pack?

comment:11 in reply to: ↑ 9 Changed 9 years ago by piggin

While it does not directly replicate what you are attempting to accomplish, the Message Timestamp Formats plugin will allow you to have date information for every line of chats/IMs.

Oops, I just noticed the titlecase. So actually it was an exact plugin name ("Message Timestamp Formats"). Had I known about this plugin before filing this bug report, I would have only complained about the *tricky* inconsistency between what is displayed and what is logged. Deceitfully tricky in that it doesn't log what it implicitly promises to log. Yeah, I'm using the loaded word because I counted on that displayed behavior and now I have many log files that will need to be fixed manually, which will be impossible to do accurately in quite a few cases. :(

However, the plugin is a little noisy. Simply marking date changes (both in the conversation window AND in the logs) would be much better. So I hope this will be fixed. By the way, was there a time (like, before this plugin existed) when Gaim was always saving dates (for every message) in logs by default (although not necessarily showing them in the conversation window)?

And an unrelated question: why does it automatically switch status from "pending" to "new" whenever I post a message?

comment:12 in reply to: ↑ 9 Changed 9 years ago by piggin

While it does not directly replicate what you are attempting to accomplish, the Message Timestamp Formats plugin will allow you to have date information for every line of chats/IMs.

What confused me was that you called it "the Timestamp plugin" in your first message. (That plugin actually exists and does something else.) So, when you mentioned it again, I didn't pay much attention to your suggestion anymore because I was sure you were talking about the same plugin.

comment:13 Changed 9 years ago by piggin

  • Description modified (diff)
  • Summary changed from Date change not displayed in XMPP log files spanning multiple days to Date change not displayed in log files spanning multiple days

comment:14 Changed 4 years ago by jl_baldridge

Confirmed in IRC.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!