... although it's not active at the moment.

eg. http://logs.glob.uno/?c=mozilla%23servo#c714806

have to detect this in the js redirector so the hash can be passed to the server for lookup.

clicking on the url from https://mozilla.logbot.info/media/20171018#c13717313 doesn't highlight c13716690, and the scroll position is wrong.

something like "logbot: location" or something like that. Should also be added to the help feature request that I noticed.

'scroll to last message' should scroll to message, not end of page.

add the ability to mark several lines, so you can send a url with a range or multiple lines highlighted.

For example, if I'm chatting with someone:

<mcomella> How do you solve this?
<...> You do X, Y, and Z!
<mcomella> Amazing, I don't want to forget this!
<mcomella> logbot: permalink
<logbot>: https://mozilla.logbot.info/example/20171219#c14030855

#focus is the official channel for Firefox Focus development - it'd be great if we could get logs too!

if you enter # into the search field, it should display an autocomplete menu listing substring matches against channels

capture the channel's current topic and show it in the web ui.

• don't show in channel logs
• create a new table that tracks the current topic
• show in webui; probably as tooltips

• listen for RPL_TOPIC and RPL_NOTOPIC messages
• add new type to jobqueue
• once a day request topics for channels-in
• in logbot-nightly tidy up the topics table old channels

Previously (when the logs were at http://logs.glob.uno), you could view logs for a channel for a range of dates, I think up to 28 days or so.

Now that the logs are at https://mozilla.logbot.info/, that ability seems to be gone - you can only view one day at a time.

I found viewing multiple days at a time to be very useful. Please consider bringing that feature back.

Maybe a regex is wrong or something similar, but that checkbox does not work for us:
http://logs.glob.uno/?c=mozilla%23automation

if a config change removes a channel, the PART action is triggered, but the bot doesn't leave the channel.

Not sure if this has been explored in the past. It would be great if the logbot UI was responsive for mobile usage.

ie. http://logbot.info/fx-team should redirect to http://mozilla.logbot.info/fx-team not http://mozilla.logbot.info/

i'm sure at some point inviting logbot into your channel will be abused, and i'll need to be able to block channels in the config.

you should be able to invite logbot to a channel. depends on issue 1 being fixed first.

logbot.glob.com.au currently points to lump. need to point at dust and configure the redirector.

logbot-nightly loads a config when it starts, and if it has to archive a channel it saves. if a channel is joined while logbot-nightly is running, that join will be reverted.

probably need a scope-based lock around the config file, something like

$config = config_update($config_file, sub {
    shift->{channels}->{$channel}->{archived} = 1;
});

this would flock and load the $config_file, passing it into the callback, save the config, release the flock and return the updated $config object.

Can't call method "log_event" on an undefined value at /home/logbot/logbot/lib/LogBot/Bot.pm line 177.
at /home/logbot/logbot/lib/LogBot/Daemon.pm line 22
LogBot::Daemon::ANON('Can't call method "log_event" on an undefined value at /home...') called at /home/logbot/logbot/lib/LogBot/Bot.pm line 177
LogBot::Bot::_log_event('LogBot::Bot=HASH(0x2a648b0)', 'LogBot::Event=HASH(0x37df118)') called at /home/logbot/logbot/lib/LogBot/Bot.pm line 168
LogBot::Bot::action('LogBot::Bot=HASH(0x2a648b0)', 'logbot', 'greatwarrior', 'kicks logbot') called at /home/logbot/logbot/lib/LogBot/IRC.pm line 153
LogBot::IRC::irc_ctcp_action('LogBot::IRC', 'POE::Session=ARRAY(0x2a6f578)', 'POE::Kernel=ARRAY(0x20cafd8)', 'HASH(0x2a6b3e0)', 'irc_ctcp_action', 'POE::Session=ARRAY(0x2a5ce48)', undef, '/usr/share/perl5/vendor_perl/POE/Component/IRC.pm', 316, ...) called at /usr/share/perl5/vendor_perl/POE/Session.pm line 482
POE::Session::_invoke_state('POE::Session=ARRAY(0x2a6f578)', 'POE::Session=ARRAY(0x2a5ce48)', 'irc_ctcp_action', 'ARRAY(0x37db5f8)', '/usr/share/perl5/vendor_perl/POE/Component/IRC.pm', 316, 'POE::Wheel::ReadWrite(355) -> select read') called at /usr/share/perl5/vendor_perl/POE/Kernel.pm line 1100
eval {...} called at /usr/share/perl5/vendor_perl/POE/Kernel.pm line 1099
POE::Kernel::_dispatch_event('POE::Kernel=ARRAY(0x20cafd8)', 'POE::Session=ARRAY(0x2a6f578)', 'POE::Session=ARRAY(0x2a5ce48)', 'irc_ctcp_action', 1, 'ARRAY(0x37db5f8)', '/usr/share/perl5/vendor_perl/POE/Component/IRC.pm', 316, 'POE::Wheel::ReadWrite(355) -> select read', ...) called at /usr/share/perl5/vendor_perl/POE/Resource/Events.pm line 266
POE::Kernel::_data_ev_dispatch_due('POE::Kernel=ARRAY(0x20cafd8)') called at /usr/share/perl5/vendor_perl/POE/Loop/Select.pm line 315
POE::Kernel::loop_do_timeslice('POE::Kernel=ARRAY(0x20cafd8)') called at /usr/share/perl5/vendor_perl/POE/Loop/Select.pm line 323
POE::Kernel::loop_run('POE::Kernel=ARRAY(0x20cafd8)') called at /usr/share/perl5/vendor_perl/POE/Kernel.pm line 1276
POE::Kernel::run('POE::Kernel=ARRAY(0x20cafd8)') called at /home/logbot/logbot/lib/LogBot/IRC.pm line 22
LogBot::IRC::start('LogBot::IRC') called at /home/logbot/logbot/lib/LogBot/Daemon.pm line 85
LogBot::Daemon::gd_run('LogBot::Daemon=HASH(0xb385a8)') called at /usr/share/perl5/vendor_perl/Daemon/Generic.pm line 190
Daemon::Generic::new('LogBot::Daemon', 'configfile', 'logbot.conf') called at /usr/share/perl5/vendor_perl/Daemon/Generic.pm line 38
Daemon::Generic::newdaemon('configfile', 'logbot.conf') called at /home/logbot/logbot/lib/LogBot/Daemon.pm line 23
LogBot::Daemon::start('LogBot::Daemon') called at ./logbot line 14
at /home/logbot/logbot/lib/LogBot/Daemon.pm line 22
LogBot::Daemon::ANON('Can't call method "log_event" on an undefined value at /home...') called at /usr/share/perl5/vendor_perl/POE/Kernel.pm line 1297
POE::Kernel::_rethrow_kr_exception('POE::Kernel=ARRAY(0x20cafd8)') called at /usr/share/perl5/vendor_perl/POE/Kernel.pm line 1285
POE::Kernel::run('POE::Kernel=ARRAY(0x20cafd8)') called at /home/logbot/logbot/lib/LogBot/IRC.pm line 22
LogBot::IRC::start('LogBot::IRC') called at /home/logbot/logbot/lib/LogBot/Daemon.pm line 85
LogBot::Daemon::gd_run('LogBot::Daemon=HASH(0xb385a8)') called at /usr/share/perl5/vendor_perl/Daemon/Generic.pm line 190
Daemon::Generic::new('LogBot::Daemon', 'configfile', 'logbot.conf') called at /usr/share/perl5/vendor_perl/Daemon/Generic.pm line 38
Daemon::Generic::newdaemon('configfile', 'logbot.conf') called at /home/logbot/logbot/lib/LogBot/Daemon.pm line 23
LogBot::Daemon::start('LogBot::Daemon') called at ./logbot line 14

network-wide metrics could be useful, especially to server operators.
plan here is provide the most of same info that channels have, across all channels.

• number of active posters (at least one event within the last 7 days)
• number of events per day
  • by channels (top 10)
  • across all channels
• network-wide activity plot
• top 10 users by event count

#telemetry is the official channel for telemetry discussions - it'd be great if there were logs. Note that I'm just a consumer of telemetry and not an owner so it may be pertinent to check with that team first if that's something they'd want (e.g. it'd be undesirable for someone to accidentally drop private data in channels and have it stored forever in logs).

Both the channel owner and an op have tried to /invite logbot but it doesn't seem to join. Is there maybe some sort of channel mode that we have set that we should change? It seems to have the same modes as another channel I see logbot in. Thanks for any help!

currently logbot relies on the network's config to prevent non-ops from inviting users. as this may change, logbot should verify that the invite originated from a channel op before logging.

roughly:

1. upon receiving an invite, add to a pending_invites $state hash, and join the channel
2. in the joined handler, check if we're joining a pending_invites channel, and...
3. send a NAMES command
4. collect ops in RPL_NAMREPLY
5. on RPL_ENDOFNAMES crosscheck pending_invites with the collected list of channel ops
6. if invited by an op, log and update the config
7. if not invited by an op, log, and leave the channel
8. privmsg the requester with the result: either a url or an error message

• don't push messages from pending_invites channels for logging

add a help command, and a base method to commands for a one line syntax blurb

https://mozilla.logbot.info/?q=&ch=firefox&w=c&f=2017-11-01&t=&n=Kwan

A DateTime object can only be compared to another DateTime object (DateTime=HASH(0x4dbec90), 1509494400). at /home/logbot/logbot/lib/LogBot/Web/Search.pm line 144.

freenode -> #indieweb-wordpress is too wide in sidebar using the default font size.

the right-padding should match the left, and it should truncate with ellipses.

touch a file each time we get an irc pong, monitor this file's timestamp with monit, alert when not touched for > 5 minutes.

ideally scrolling vertically should stop at the last message, unless the cursor is over the channel sidebar.

a work around for now is to collapse the sidebar.

because hypnotoad is behind a reverse proxy, the remote ip in the access logs is always localhost. probably need to use x-forwarded-for

Not sure if this is the right place to track this, but it would be nice to have HTTPS and even HSTS preload for the logs.

move nick colouring server-side to avoid the flash of uncolour nicks on load.

currently running on 512mb DO instance.

logbot's memory consumption is right on the limit of this, and triggered a few OOM alerts. i've enabled swap as a stop gap, but really need to bump up to the next instance size (1 gb ram) and disable swap.

when viewing the current date's logs the 'last message' timestamp should update in real time.

this means changing to a different relative func that has identical perl and js implementations.

currently both the irc bot and the mojo webapp hold onto their log file handle. need to get logrotate to send them a signal post-rotate causing them to release their current handles.

http://mojolicious.org/perldoc/Minion

store recently viewed channels in a cookie (eg. last 10) and show them on the logbot.info landing page.

Would be pretty cool, huh? :)

either skip empty days completely, or provide a links to jump to the next and previous days with events.

A use case of mine...

Each morning, for each of several IRC rooms:

1. Visit the log page for the room, eg http://logs.glob.uno/?c=treeherder
2. Try to read any messages I missed overnight, but the log doesn't go back far enough.
3. So, click the "..." for the "from date" selector.
4. Pick the day prior to today (sometimes mis-clicking, meaning I get completely the wrong logs).
5. Click update
6. Wait for page to fully reload
7. Scroll down to where one day turned into the next (ie where the top of the log was at step 2) - because the vast majority of the newly loaded log is redundant (other than the last few hours), since it was during my working day and so I was connected to IRC at that time.
8. Repeat for {#developers, #ateam, ...}

Problems:

• Multiple clicks & easy to click the wrong date
• Tedious to scroll down to the log part that was previously being viewed
• Page has to reload

Proposal:
At the start and end of the viewed log, add "Load previous day" and "Load next day", which would:

• Adjust the from/to date fields appropriately and update the page
• Ideally: Scroll down to the end of the new day / where the previously viewed content was.
• Optionally: Load the additional log segments via AJAX and not need the page reload.

https://mozilla.logbot.info/?q=telemetry&ch=jsapi&w=a&n=billm&debug=1

no results

https://mozilla.logbot.info/?q=telemetry&ch=jsapi&w=a&n=billm&ft=n&debug=1

9 results, including some that i would expect to be returned by fts.

eg. https://mozilla.logbot.info/mozilla.se/

rework logging..

• ~/logbot/logs/irc-$network.log → /var/log/logbot/irc_$network.log
• use Mojolicious::Plugin::AccessLog to log mojo access to /var/log/logbot/access_$network.log
• configure log rotation for all logs