Atomic icon indicating copy to clipboard operation
Atomic copied to clipboard

(Feature Request) Logging to disk

Open Mokura opened this issue 11 years ago • 3 comments

As #36, but with clarification: logging to disk for future review (with a text viewer/editor, etc). Not sure if I should remark on the closed issue or open a new one.

Mokura avatar Jan 14 '15 17:01 Mokura

In some ways I consider logging to disk an anti-feature, given that I actively turn it off in my clients. There are valid reasons to do this, however I'm worried that it would cause a certain amount of unpleasantness.

I have two basic ideas on this thought, should i implement this:

  • The incoming/outgoing streams are responsible for handling this. 100% of this gets handled at the connection level and replay is done by reading all of the logfile for that server/channel. Downside to this is that the logs are pretty raw, as they're just IRC stanzas
  • I cook the logs somehow by making the channels manage them. This is a fairly reasonable concept however it would make the channel/conversation handling logic far more complex than I feel is neccesary. I would also have to somewhat cook the data in order for it to be parsable later.

indrora avatar Jan 15 '15 16:01 indrora

Raw logs would probably be alright as long as conversations are still readable - I was mostly speaking from an end user point of view. No point cluttering up the code more than necessary.

Mokura avatar Jan 15 '15 17:01 Mokura

Would it be possible to simply append to a logfile the results of whatever internal process spits out the formatted messages for the user? Preferably, sorted into folders/files based on the date and conversation.

thetoastcaper avatar Jun 10 '16 00:06 thetoastcaper