horazont/xmpp-crowd

The crowd of SleekXMPP/aioxmpp based bots which make my life easier.

xmpp-crowd

This is just a bunch of bots based on the great SleekXMPP python library, which are running on my system to make my life a little bit easier. Some of these will not be of any use for the broader public, especially as they're missing docstrings (ahem), but if anyone can get any interest out of them, it's fine.

hub.py

hub.py is in fact the core of the “modern” bots (i.e. all but foobot.py), which abstracts away some of the (very little) boilerplate all bots share.

buildbot.py

Thats a really cool guy who does what you'd suspect from reading his name. He'll listen for events on a pubsub node and trigger shell commands or whatever when certain events come in. It's built to work together with gitbot.py, which will push the proper events if installed in a git repositories post-update hook. It should be easy to customize both to work with hg or similar.

buildbot is highly configurable. See the buildbot_config.py for a nicely commented example.

xmpp-crowd's Issues

Can you change SleekXMPP (dead project) to Slixmpp (Successor)

Can you update the code for compatibility with the successor of SleekXMPP?

• https://lab.louiz.org/poezio/slixmpp
• https://github.com/poezio/slixmpp

Read common issue tracker fields

It would be nice if foorl could display common fields of bug trackers (author, status, last modified, ??).

I am not entirely sure though if foorl should implement each bug tracker's interface or if there's a way for bug trackers to declare a common interface that foorl can implement.

normalize percentages so that one bar is always full

Avoid displaying titles when urls look "obvious enough"

As describe the other day in some room, it happens somewhat often that foorls output is redundant/pretty similar to the url itself, example:

user> https://blog.rust-lang.org/2018/11/27/Rust-survey-2018.html
foorl> website: Rust Survey 2018 Results - The Rust Programming Language Blog

user> https://blog.gruntwork.io/5-lessons-learned-from-writing-over-300-000-lines-of-infrastructure-code-36ba7fadeac1
foorl> website: 5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code

"obvious enough" can be loosely defined as "most words foorls gather are already contained in the url.
There could be a way for foorls to avoid displaying these urls when it is the case.

allow withdrawal of votes

Command to show most recent followers

As long as the account is small, it is useful to see who has followed most recently. Unfortunately, this is currently only possible by logging into the twitter.com website. We should add a command for that.

support polls with multiple votes per person

poll module uses global state

The fix for this one should probably be analogous to the implementation found in the InfoStore: have a manager object which takes care of all persistent storage. This could even save polls to disk upon a foorl respawn.

SIGINT (Ctrl+C, ^C) in repl shell does terminate foorl

We should probably intercept that signal and ignore it…

hub should be made more reusable

All the class constants need to be pulled out and made configurable. This probably depends on #14.

add pollctl command to highlight all people who didn't vote yet

soup_handler breaks the whole URL lookup if soup.head is None

See common_handlers.py:88, this breaks if soup.head is None.

a reusable config framework must be established

This would allow to get rid of all the constants e.g. in hub.py. Those constants are currently quite annoying, especially when building test setups etc.

however, to properly get rid of them, the implementation of a reusable config framework, which should be a good mix of the one used for infobot and the one used for foorl, is desired.