| Age | Commit message (Collapse) | Author |
|---|
|
Since httputil.get_response() can raise exceptions, catch them into an
appropriate block. Turn a missing response body into a runtime error to
handle this error conditions consistently with other exceptions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Define configuration keys for maximum and default number of user data
items output, with a separate value for shouts (which are usually much
more verbose and therefore would have a much lower maximum and default).
Each command also allow the specification of the number of entries
actually output (different than the default, clipped at the configured
maximum.
This way user data has the same rate limiting as events.
Internally, the switches for the user data are also made more uniform to
select, where it makes sense, different sentences depending on how many
entries are being displayed (none, all, some).
|
|
|
|
|
|
|
|
|
|
This ensures that 'lastfm who' triggers the correct map.
|
|
|
|
there to make replies consistent with rbot's usual style
|
|
|
|
aliases in @registry are favored over literal last.fm users
|
|
nonexistent user(s)
|
|
|
|
|
|
now_playing works again
Lastfm removed the <date> element from track's which are currently being played, which caused the plugin to die. Now we detect if the <date> element exists.
|
|
user. this way it is more intuitive.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2.0 routine yet
|
|
|
|
|
|
|
|
|
|
|
|
internationalization to all strings, removed cruft.
Conflicts:
data/rbot/plugins/lastfm.rb
|
|
|
|
track if real time data isn't there.
|
|
|
|
user. fixed help too.
|
|
nickname, and 'lastfm' by itself will
retunr the now playing tracks
|
|
|
|
|
|
|
|
|
|
|
|
* (plugins/*) converted to the new threading model
|
|
|
