It would be extremely useful to have a local file with a copy of all the messages from the past, like konversation does (~/logs, one file per chat room or private chat).
It can be create some problem as we can load history from room. For example we have room #foo we write into this room, => it will save in ~/logs/#foo/... But a day we decide to load very old history => we will have a problem with log file no ? We will have old history + current history + after that very old history I don't know to manage it.
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 ;)
(In reply to David Faure from comment #2) > 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? Yeo I implemented it. > > 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. ok > > 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. Ok I see. I will implement it. > > 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 ;)
I implemented this long ago.