Mercurial > prosody-modules
view mod_pubsub_twitter/README.markdown @ 4989:b74d592df9e2
mod_http_muc_log: Remove dead code
This might be something left over since a different variant where the
loop went like `for n = i-1, i-100, -1 do ... end` i.e. it went trough a
fixed number of items instead of all the page until the current message.
Then it would have needed something to stop going over the end, but
since the checks are simple it shouldn't be much of a problem looping
over even a very busy day.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 16 Aug 2022 01:27:59 +0200 |
parents | 4d73a1a6ba68 |
children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Subscribe to Twitter search queries over pubsub ... Introduction ------------ Twitter has an open 'realtime' search API, but it requires polling (within their rate limits). This module allows Prosody to poll for you, and push new results to subscribers over XMPP. Configuration ------------- This module must be loaded on a Prosody pubsub component. Add it to `modules_enabled` and configure like so: Component "pubsub.example.com" "pubsub" modules_enabled = { "pubsub_twitter" } twitter_searches = { realtime = "xmpp OR realtime"; prosody = "prosody xmpp"; } This example creates two nodes, 'realtime' and 'prosody' that clients can subscribe to using [XEP-0060](http://xmpp.org/extensions/xep-0060.html). Results are in [ATOM 1.0 format](http://atomenabled.org/) for easy consumption. Option Description ------------------------- -------------------------------------------------------------------------------- twitter\_searches A list of virtual nodes to create and their associated Twitter search queries. twitter\_pull\_interval Number of minutes between polling for new results (default 20) twitter\_search\_url URL of the JSON search API, default: "http://search.twitter.com/search.json" Compatibility ------------- ----- ------- 0.9 Works ----- -------