IRC logs continuity after BotBot.me shutdown

[Justin Obara]

It looks like Colin, Avtar, and Alan should be able to update the topics
for our channels. I’ve updated the wiki to point at the new logs and the
botbot archive that Alan setup. However, it looks like you can’t view all
of the botbot archive over the web because there are too many files.

Thanks
Justin

On November 9, 2018 at 5:48:04 AM, Javier Hernandez (
javi at raisingthefloor.org) wrote:

Hi Alan,

thanks for setting all this up.
In terms of the user interface, i guess it's all we need. Yes, it can be
prettier, but it's just fine in my opinion.
Just one thing, we need an "Op" to update the topic in the fluid channels
to include the new URL to the logs. Who can be that generous "Op"?

Cheers,
Javi


On Mon, Nov 5, 2018 at 8:10 PM Harnum, Alan <aharnum at ocadu.ca> wrote:

> Update for this because today is the last official day of the BotBot
> service (it is still up right now, but likely not for long):
>
>
>
>    - http://irc-logs.fluidproject.org/ will continue to have channel logs
>    going forward.
>    - if you are looking to access IRC logs from the last several years in
>    the immediate term, please refer to the repo at
>    https://github.com/waharnum/fluid-irc-logs (we should arrange to
>    transfer this repo to the Fluid organization) – this is where I’ve
>    preserved the raw logs scraped from BotBot and daily logs extracted from
>    those with a small Python script I wrote
>
>
>
> *From:* "Harnum, Alan" <aharnum at ocadu.ca>
> *Date:* Friday, September 21, 2018 at 5:07 PM
> *To:* Fluid Work <fluid-work at fluidproject.org>
> *Subject:* IRC logs continuity after BotBot.me shutdown
>
>
>
> As many of you know already, the (free) BotBot.me logging service we use
> to log our IRC channels is shutting down in early November:
> https://lincolnloop.com/blog/saying-goodbye-botbotme/
>
>
>
> PLANS FOR PRESERVING THE LAST SEVERAL YEARS OF LOGS
>
>
>
> I’ve been in contact with the BotBot.me operators and they provided me
> with a script to download our logs in bulk. I’ve done this already once to
> make sure it works, and will do it again closer to the time of shutdown.
>
>
>
> The logs are extremely basic (a single large text dump for each channel)
> and will likely require some parsing and re-presentation to be useful. If
> anyone is interested in seeing the raw logs now, let me know and I can
> share a private GitHub repo with you.
>
>
>
> PLANS FOR IRC LOGGING GOING FORWARD
>
>
>
> The plan for logging continuity at the moment is to run a simple logging
> bot and serve its log through a web server. This is basic but can be
> executed with reasonable speed so we’ve got some overlap between this
> solution and the BotBot shutdown in order to work out any challenges with
> this approach. We can look into
>
>
>
> The bot is called “fluid-bot” and the (plaintext) logs are visible right
> now at http://irc-logs.fluidproject.org/ - please keep in mind this
> approach is still experimental and I can’t guarantee they’ll be
> comprehensive at this point – there’ll be some gaps in the next week as I
> work out any issues.
>
>
>
> Please let me know if you have any questions or concerns with this
> approach.
>
>
>
> *ALAN HARNUM*
>
> SENIOR INCLUSIVE DEVELOPER
>
> INCLUSIVE DESIGN RESEARCH CENTRE, OCAD UNIVERSITY
>
>
>
> *E *aharnum at ocadu.ca
>
> *OCAD UNIVERSITY*
> 100 McCaul Street, Toronto, Canada, M5T 1W1
> www.ocadu.ca <http://ocadu.ca/>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

_______________________________________________________
fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
To unsubscribe, change settings or access archives,
see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20181109/ba5d0acd/attachment.html>