Bender is a Jabber-Bot.
Its main functionality is to be always online, joined to a groupchat (MUC), and to accept messages to say there via HTTP POST. Thus, other systems (e.g. Nagios, Continuous Integration etc.) can perform Jabber notifications without having to speak Jabber themselves (and without any join/part noise).
You can tell Bender to say something like this:
curl -d "Say something" http://user:password@host:port
Quotes
Bender also sometimes randomly says things by itself (Bender quotes). To avoid flooding the channel, there are three thresholds:
Only say something with a given probability.
Only say something if we haven’t said anything for a given time.
Only say something if at least a given number of messages from other people have been said in the chatroom.
Deployment
Bender is deployed and configured using buildout. Here is an example configuration file:
[buildout] extends = profiles/prod.cfg [config] chatroom = my-chat@jabber.org jabber_user = bender-user jabber_password = secret min_silence_duration = datetime.timedelta(minutes=5) min_human_messages = 10 speaking_probability = 1.0 / (10 * 60) loglevel = INFO http_address = 0.0.0.0:8099 http_user = bender http_password = http_secret
CHANGES
1.0 (2011-10-09)
first release.
Metadata
Release files for gocept.bender 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gocept.bender-1.0.tar.gz | 19.1 kB | Without provenance | Details for gocept.bender-1.0.tar.gz |
Release files / gocept.bender-1.0.tar.gz
| Download URL | gocept.bender-1.0.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bb9f690fe68b28e3bad7cf6be44a9de0c685cd1842313e271149362ff8d7b9b
|
|
BLAKE2b-256 checksum How to use checksums |
67fcc04842f681fe57a3439a4f32e11cf89dce6bd4c9758de82a1fce5bee1db4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gocept.bender 1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.