Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/tilpner/ilc
IRC log converter/collector
https://github.com/tilpner/ilc
irc irc-logs rust
Last synced: about 1 month ago
JSON representation
IRC log converter/collector
- Host: GitHub
- URL: https://github.com/tilpner/ilc
- Owner: tilpner
- License: bsd-3-clause
- Created: 2015-03-23T15:43:15.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2016-03-20T16:40:59.000Z (almost 9 years ago)
- Last Synced: 2024-11-02T11:21:45.750Z (about 2 months ago)
- Topics: irc, irc-logs, rust
- Language: Rust
- Homepage:
- Size: 177 KB
- Stars: 7
- Watchers: 4
- Forks: 3
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
ilc
=========
[](https://travis-ci.org/tilpner/ilc)
[](https://ci.appveyor.com/project/tilpner/ilc)
[](https://crates.io/crates/ilc)
[](http://choosealicense.com/licenses/apache-2.0/)
#### What is this thing?
ilc is a library to work with common IRC log formats, as well as a collection
of commonly needed utilities for IRC logs.
The library can convert between most of the EnergyMech (ZNC) and Weechat log formats, as well as binary and msgpack representations of them.
The tools can merge, convert, and pretty-print them, or count the lines/words that people said in them.
#### Downloads
There are other builds, including for/with musl, mingw, or ARM. Please [check out the latest release](https://github.com/tilpner/ilc/releases/latest) to see all archives.
| Platform | 64 bit | 32 bit |
| -------- | ------ | ------ |
| Linux | [Download](https://github.com/tilpner/ilc/releases/download/v0.3.1.1/ilc-x86_64-unknown-linux-gnu.tar.gz) |[Download](https://github.com/tilpner/ilc/releases/download/v0.3.1.1/ilc-i686-unknown-linux-gnu.tar.gz) |
| OS X | [Download](https://github.com/tilpner/ilc/releases/download/v0.3.1.1/ilc-x86_64-apple-darwin.tar.gz) |[Download](https://github.com/tilpner/ilc/releases/download/v0.3.1.1/ilc-i686-apple-darwin.tar.gz) |
| Windows | [Download](https://github.com/tilpner/ilc/releases/download/v0.3.1.1/ilc-x86_64-pc-windows-msvc.zip) |[Download](https://github.com/tilpner/ilc/releases/download/v0.3.1.1/ilc-i686-pc-windows-msvc.zip) |
*Note that these links might be broken in the one hour it takes between release and uploading builds, sorry for that.*
#### How can I compile this myself?
Because I'm using experimental features (slice_patterns), you have to use a Rust nightly installation either way.
###### From crates.io
```console
cargo install ilc
```
###### From git
`67ee599c56ba9e58cfe190036b7dcc656b20bfdd` is known to compile with
> rustc 1.8.0-nightly (d63b8e539 2016-01-23)
> cargo 0.8.0-nightly (8edc460 2016-01-21)
To compile:
```console
cargo build --release
```
#### Examples
```console
ilc stats -f w -i full.dated.sorted | jq ".stats.freqs[].lines" | awk '{ total += $1; count++ } END { print total/count }'
```
#### Usage
```console
Usage:
ilc parse [options] [-i FILE...]
ilc convert [options] [-i FILE...]
ilc freq [options] [-i FILE...]
ilc seen [options] [-i FILE...]
ilc sort [options] [-i FILE...]
ilc dedup [options] [-i FILE...]
ilc (-h | --help | -v | --version)
Options:
-h --help Show this screen.
-v --version Show the version (duh).
--date DATE Override the date for this log. ISO 8601, YYYY-MM-DD.
--tz SECONDS UTC offset in the direction of the western hemisphere.
--channel CH Set a channel for the given log.
--inf INF Set the input format.
--outf OUTF Set the output format.
--in -i IN Give an input file, instead of stdin.
--out -o OUT Give an output file, instead of stdout.
--infer-date Try to use the filename as date for the log.
```
#### Are you stupid? Why Rust?
Uhh, actually... that may have been a suboptimal choice. Nobody cares about performance here
anyways. But it was what I started with, and I didn't feel like rewriting it.
#### I found a bug!
Great! Or... well, not so great. Please file it [here](https://github.com/tilpner/ilc/issues/new)!
#### It doesn't support my format.
Support for irssi is planned, but beyond that you'll have to file an issue or implement it yourself.
PRs are welcome, but I can't promise to merge all of them without revision. :)