You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wouldn't a regular txt log make sense too? I know a lot of pages that use them and it wouldn't require the web UI.
Parsing the nick list is actually not too easy (unless you just show the active conversation members).
I would add options to disable join/parts in the logs in the config.json.
@S0lll0s Parsing the nick list should actually be easy. A simple NAMES lookup will fetch the list, and from their you just listen for KICK/JOIN/PART/QUIT messages, all of which are emitted by the Event Manager. :)
I'm not opposed to creating a txt file as a first pass, but I'd definitely like this to be publicly viewable and hosted on a web UI at some point if the user so chooses.
I didn't mean the looking up names during logging, I meant extracting "current users online" information from a regular (text) log. As you want to store the info in a custom format / db, that issue is probably resolved by simply storing "user sessions" with a join-time/part-time schema and filtering that according to the current time (in a text look you would have to scan the whole text log to determine the users online at any time).
This relies on completion of #58 (web UI) first, in order to display the logs.
Ideally, I'd like the following features:
Logging should be quite easy using Cardinal's events. The web UI is the only tricky part currently.
The text was updated successfully, but these errors were encountered: