| Commit message (Collapse) | Author | Age |
|
|
|
| |
With the colored context too.
|
|
|
|
|
|
|
|
| |
This vastly increases the speed of the query for any search with a
decent number of matches. It can be slightly less accurate since
it depends on the insert order of events, but that usually won't
be a problem for a query limited to a single network. The litterbox
query interface isn't meant to exhaustively list results either.
|
|
|
|
|
| |
Not adding a corresponding -o option like in pounce and catgirl,
since litterbox is likely connecting to pounce anyway.
|
|
|
|
|
| |
This feature is rarely used, so just skip STATUSMSG prefixes in the
target so events use the right context.
|
|
|
|
|
| |
Not accurate but better than every message being the same color in
imported logs.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
LibreSSL is "a modified version of that library".
Oops, should've done this before tagging, but I don't think it matters
much. They're both versions of the same library, right?
|
| |
|
|
|
|
| |
This saves 125 MB on my own database after VACUUM.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently IRCds have decided that the 15-parameter limit doesn't matter
anymore. 254 is the maximum number of single-byte parameters (following
a single-byte command) which fit in a 512-byte CR-LF-terminated line.
When everyone decides that the 512-byte line length limit doesn't matter
either, I will delete my software and people can use some JavaScript
garbage instead.
This makes struct Message 2080 bytes, but there's only ever one of it
around at once. Avoid passing it by value to handle.
|
|
|
|
|
|
| |
Relying on the MOTDSTART handler to set motd.cap and allocate the buffer
is an issue if a regular RPL_MOTD is received without one. Just allocate
the buffer on the first RPL_MOTD.
|
|
|
|
| |
https://www.gnu.org/licenses/gpl-faq.en.html#GPLIncompatibleLibs
|
|
|
|
|
| |
To simplify upgrades, restarting litterbox should be sufficient. The
database can still be explicitly migrated with -m.
|
|
|
|
|
| |
This should prevent continually crashing on the same ERROR in the pounce
buffer.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Replacing declarations followed by while loops with for loops and
generating the short option string from the long options.
|
| |
|
| |
|
| |
|
|
|
|
| |
This matches the function used by catgirl.
|
| |
|
| |
|
|
|
|
|
| |
This is implemented by pounce and prevents litterbox from affecting the
away status of pounce's server connection.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It's a side-effect of imports that shouldn't surface elsewhere. Would be
nice to have unscoop figure out how it can eliminate using * in more
places.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Even with NOTICEs litterbox would sometimes receive its own responses,
which would create duplicates in the database, essentially.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
When connected to pounce, it's possible to receive some of its own PMs,
so it should respond with what can't be commands.
|
| |
|
|
|
|
|
|
|
|
|
| |
The code is a bit cleaner this way I think, and performance would be
better if the list of handlers ever got very long, and it was sorted
anyway.
However, I would prefer if there were a way to enforce the list being
sorted at compile-time.
|
| |
|
| |
|
|
|
|
|
|
| |
No idea now why I wanted to have network bound all the time. Ended up
creating a copy of the string for each statement instead of just having
one like this.
|
|
|
|
|
| |
It's more like a cache of existing topics. events is still meant to
record actual topic events.
|
| |
|