README
NAME
OTPCR - Office of the Prosecutor's Communication Rercord 117 of 2019
SYNOPSIS
otpcr <cmd> [key=val] [key==val] otpcr [-a] [-c] [-d] [-i] [-v]
DESCRIPTION
OTPCR holds evidence that king netherlands is doing a genocide, a written response where king netherlands confirmed taking note of “what i have written”, namely proof that medicine he uses in treatement laws like zyprexa, haldol, abilify and clozapine are poison that make impotent, is both physical (contracted muscles) and mental (make people hallucinate) torture and kills members of the victim groups.
OTPCR contains correspondence with the International Criminal Court, asking for the arrest of king netherlands, for the genocide he is committing with his new treatement laws.
Current status is a “no basis to proceed” judgement of the prosecutor which requires a “basis to prosecute” to have the king actually arrested and, thereby, his genocide stopped.
INSTALL
you can install otpcr with the use of pipx:
$ pipx install otpcr $ pipx ensurepath $ mkdir ~/.otpcr
USAGE
without any argument the bot does nothing:
$ otpcr $
see list of commands:
$ otpcr cmd cmd,dne,err,log,mod,req,tdo,thr,tmr
start a console:
$ otpcr -c >
use -v for verbose:
$ otpcr -cv May 12 05:51:49 2024 OTPCR CV CMD,ERR,LOG,MOD,REQ,TDO,THR,TMR >
use -i to run init on modules:
$ otpcr -caiv
start daemon:
$ otpcr -d
show request to the prosecutor:
$ otpcr req Information and Evidence Unit Office of the Prosecutor Post Office Box 19519 2500 CM The Hague The Netherlands
CONFIGURATION
irc:
$ otpcr cfg server=<server> $ otpcr cfg channel=<channel> $ otpcr cfg nick=<nick>
sasl:
$ otpcr pwd <nsvnick> <nspass> $ otpcr cfg password=<frompwd>
rss:
$ otpcr rss <url> $ otpcr dpl <url> <item1,item2> $ otpcr rem <url> $ otpcr nme <url> <name>
opml:
$ otpcr imp <filename> $ otpcr exp
OPTIONS
here is a list of commandline options otpcr provides:
-a load all modules -c start console -d run in the background -h show help -i start services -v use verbose
COMMANDS
commands are mostely for irc and rss management:
cfg - irc configuration cmd - commands dlt - remove a user dpl - sets display items exp - export opml fnd - find objects imp - import opml log - log some text met - add a user mre - displays cached output pwd - sasl nickserv name/pass rem - removes a rss feed req - request rss - add a feed thr - show the running threads
SYSTEMD
save the following it in /etc/systemd/system/otpcr.service and replace “<user>” with the user running pipx:
[Unit] Description=Office of the Prosecutor's Communication Record 117 of 2019. Requires=network-online.target After=network-online.target [Service] Type=simple User=<user> Group=<user> WorkingDirectory=/home/<user>/.otpcr ExecStart=/home/<user>/.local/pipx/venvs/otpcr/bin/otpcr -d RemainAfterExit=yes [Install] WantedBy=default.target
then run this:
$ sudo systemctl enable otpcr --now
default channel/server is #otpcr on localhost
FILES
pipx stores the otpcr documentation in it;s local pipx environment:
~/.otpcr ~/.local/bin/otpcr ~/.local/pipx/venvs/otpcr/*
AUTHOR
I am reachable at the following email:
Bart Thate <bthate@dds.nl>
COPYRIGHT
OTPCR is placed in the Public Domain.
1 maintainer
Metadata
1 maintainer
Release files for otpcr 23
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 | |
|---|---|---|---|---|
| otpcr-23.tar.gz | 4.8 MB | Without provenance | Details |
Release files / otpcr-23.tar.gz
| Download URL | otpcr-23.tar.gz |
|---|---|
| Size | 4.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9080df481a3e1a2697691a4d73d58afdf46bf81f4359e6d5923bb0d983b497bb
|
|
BLAKE2b-256 checksum How to use checksums |
b2d216f88b69efcb5d42545e61ffa6c5dc11afbf9e983a1b750ed009b538b373
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for otpcr 23
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.
