| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
why, we just prevent further changes to them when we spot one
|
|
go the same place
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
detect memory leaks
|
|
|
|
|
|
|
|
|
|
this seems to be more common
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
control to be more reactive while still preventing excessive flood disconnections
|
|
|
|
salut.address_only is false
|
|
|
|
|
|
not found
|
|
methods
|
|
or false depending on whether the result was taken from the cache or not.
|
|
not needed anymore
|
|
called with station code or location. doesn't remember last location (yet)
|
|
|
|
|
|
|
|
|
|
of its nick as it did before. This ensure consistent scoring even when the bot changes nick
|
|
|
|
when checking expiration
|
|
HTTP headers
|
|
|
|
|
|
actually done to handle it
|
|
search when you want more results than the first keyword.search_resuts
|
