feediverse will read RSS/Atom feeds and send the messages as Mastodon posts. It's meant to add a little bit of spice to your timeline from other places. Please use it responsibly.
Install
pip install feediverse
Run
The first time you run feediverse you'll need to tell it your Mastodon
instance and get an access token which it will save in a configuration file. If
you don't specify a config file it will use ~/.feediverse:
feediverse
Once feediverse is configured you can add it to your crontab:
*/15 * * * * /usr/local/bin/feediverse
Run feediverse --help to show the command line options.
Post Format
You can customize the post format by opening the configuration file (default is ~/.feediverse) and updating the template property of your feed. The default format is:
{title} {url}
If you want you can use {summary} in your template, and add boilerplate text
like so:
Bookmark: {title} {url} {summary}
{hashtags} will look for tags in the feed entry and turn them into a space
separated list of hashtags. For some feeds (e.g. youtube-rss) you should use {link} instead of {url}.
{content} is the whole content of the feed entry (with html-tags
stripped). Please be aware that this might easily exceed Mastodon's
limit of 512 characters.
De-duping
If you are attempting to use the RSS feed of a major news site, you may find
that they change / update (or just re-post) the same items multiple times which
will lead to duplicate toots. To enable de-duplication, use the {--dedupe}
option to check for duplicates based on a tag before tooting, e.g.
feediverse --dedupe url
Multiple Feeds
Since feeds is a list you can add additional feeds to watch if you want.
...
feeds:
- url: https://example.com/feed/
template: "dot com: {title} {url}"
- url: https://example.org/feed/
template: "dot org: {title} {url}"
Develop
poetry install
poetry run feediverse
Metadata
Release files for feediverse 0.4.1
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 |
|---|---|---|---|---|
| feediverse-0.4.1.tar.gz | 5.2 kB | Without provenance | Details for feediverse-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| feediverse-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for feediverse-0.4.1-py3-none-any.whl |
Total release size: 11.1 kB
Release files / feediverse-0.4.1.tar.gz
| Download URL | feediverse-0.4.1.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd250537620b137a434a39042c993ace8f385e34f4938ff04d42a71b5019d579
|
|
BLAKE2b-256 checksum How to use checksums |
0bc304875769ffcc171077bfee0acaa5047664b56fab0b07f814a27ff7e23189
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.6 Darwin/23.6.0
|
Release files / feediverse-0.4.1-py3-none-any.whl
| Download URL | feediverse-0.4.1-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d964e515d925e4bbc5e1cac925aec79d488317756ea6ac0b091f5411eed5091
|
|
BLAKE2b-256 checksum How to use checksums |
c51aa5fb82fb3b0bdc217ee1dd1ef0050af03117284165bec8cfaf1852bf039c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.6 Darwin/23.6.0
|
Security for feediverse 0.4.1
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.