Fedinesia
⚠️ BEWARE, THIS TOOL WILL DELETE SOME OF YOUR POSTS ON THE FEDIVERSE ⚠️
Fedinesia is a command line (CLI) tool to delete old statuses from Mastodon or Pleroma instances. It respects rate limits imposed by servers.
Install and run from PyPI
It's easy to install Fedinesia from PyPI using the following command:
pip install fedinesia
Once installed, Fedinesia can be started by typing fedinesia into the command line.
Configuration / First Run
Fedinesia will ask for all necessary parameters when run for the first time and store them in a config.json file in the current directory.
Podman / Docker Container
Fedinesia can also be run using Podman or Docker as follows:
podman run \
--env AUDIT_LOG_FILE=/logging/audit.log \
--env PAUSE_IN_SECONDS=300 \
--replace \
--volume ./config:/config \
--volume ./logging:/logging \
--name fedinesia \
forge.marvin8.zone/marvin8/fedinesia
Podman / Docker Environment Variables
-
PAUSE_IN_SECONDS (mandatory) This must be set to a positive integer. This value is the number of seconds to wait between successive runs of
fedinesia. -
AUDIT_LOG_FILE (optional) Full path to where audit log file should be written to. It is intended that logfiles will be written to
/loggingdirectory. No audit log file will be generated / updated if this value has not been set. -
AUDIT_STYLE (optional) What style of audit log file to write. Possible options are
PLAINorCSV. Defaults toPLAIN. Has no effect ifAUDIT_LOG_FILEhas not been set. -
LIMIT (optional) If set to a positive integer, will make
fedinesiastop processing any further deletions once this number of statuses have been deleted in the current execution. -
DRY_RUN (optional) If set to any value, e.g.
DRY_RUN=true, will makefedinesianot actually delete any status. Statuses that would be deleted are shown instead. -
PROGRESS_FILE (optional) If set to a filename, will store the progress of deleted statuses to that file. This is intended to be used together with the
CONTINUE_PROGRESSvariable. This allowsfedinesiato process a large number of status deletions over multiple executions while keeping track of progress. -
CONTINUE_PROGRESS (optional) If set to any value, e.g.
CONTINUE_PROGRESS=true, will makefedinesiacontinue with deleting statuses from last successfully deleted status in reverse historical order. Setting this variable implies thatPROGRESS_FILEhas been set as well. -
LOGGING_CONFIG (optional) Can be set to a filename containing logging configuration definition. Below is a sample of the logging config file I use during development:
[[handlers]]
sink = "sys.stdout"
format = "{message}"
level = "INFO"
[[handlers]]
sink = "/logging/dev-fedinesia-debug.log"
rotation = "1 day"
retention = 3
level = "DEBUG"
format = "{time} - {level} - {name} - {function}({line}) - {message}"
colorize = "none"
Licensing
Fedinesia is licensed under the GNU Affero General Public License v3.0.
Supporting Fedinesia
There are a number of ways you can support Fedinesia:
- Create an issue with problems or ideas you have with/for Fedinesia
- Create a pull request if you are more of a hands-on person
- You can buy me a coffee
- You can send me small change in Monero to the address below:
Monero donation address
86ZnRsiFqiDaP2aE3MPHCEhFGTeiFixeQGJZ1FNnjCb7s9Gax6ZNgKTyUPmb21WmT1tk8FgM7cQSD5K7kRtSAt1y7G3Vp98nT
Metadata
Release files for fedinesia 3.7.15
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 |
|---|---|---|---|---|
| fedinesia-3.7.15.tar.gz | 12.4 kB | Without provenance | Details for fedinesia-3.7.15.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fedinesia-3.7.15-py3-none-any.whl | Python 3 | none | any | Details for fedinesia-3.7.15-py3-none-any.whl |
Total release size: 28.3 kB
Release files / fedinesia-3.7.15.tar.gz
| Download URL | fedinesia-3.7.15.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
861cd08146fe2e0928427482d7d354714edcb5101fc6c25ebfcc57494916a612
|
|
BLAKE2b-256 checksum How to use checksums |
1a026d2358a289dcc258f840af03538ad6c940bf5b4b57352667bcd1a02b33b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / fedinesia-3.7.15-py3-none-any.whl
| Download URL | fedinesia-3.7.15-py3-none-any.whl |
|---|---|
| Size | 15.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dfffe830075f33d755fb5fcdb3b1896ccc3f18fdd00f50a4ece5fbfb80f10b5d
|
|
BLAKE2b-256 checksum How to use checksums |
a5b48445a4af4547d00ae8bfafe07ab42f0a5af34bec9040cf34a1591f13b613
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for fedinesia 3.7.15
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.