https://bugs.kde.org/show_bug.cgi?id=382592
--- Comment #2 from David Faure <fa...@kde.org> --- Yep history replay always makes this tricky. With konversation and bitlbee (history replay when connecting) we had exactly what you describe, lines were repeated many times, this was suboptimal. Are you saying that ruqola works like RC+, the user can (or will be able to) scroll back to load more history? One simple solution is to only log what's coming in while we're connected (i.e. no history replay). After all, 95% of the time I use local logs, it's for re-reading a discussion I was part of. But how about extending that with the new messages received while offline? In details: Ruqola would store the last message timestamp (across all rooms) into kconfig. Then on the next login it can load and log all messages between that time and right now. Over time this will be the full history. Scrolling back to get old history will not log anything, because those messages will be from before that "last timestamp" date-time. When coming back from 3 weeks of vacation it will be a bit slow, but I think that's OK, as long as there's some sort of a progress bar ;) -- You are receiving this mail because: You are watching all bug changes.
