NAME
OTPCR - Since 4 march 2019
SYNOPSIS
otpcr <cmd> [key=val] [key==val] otpcrc [-i] [-v] otpcrd otpcrs
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 <evidence> 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 <writings> with the International Criminal Court, asking for arrest of the king of the netherlands, for the genocide he is committing with his new treatement laws.
Current status is a “no basis to proceed” <writings> judgement of the prosecutor which requires a “basis to prosecute” <reconsder> to have the king actually arrested.
OTP-CR-117/19 has been duly entered in the Communications Register of the Office.
Since 4 march 2019
INSTALL
installation is done with pipx
$ pipx install otpcr $ pipx ensurepath
USAGE
without any argument the bot does nothing
$ otpcr $
see list of commands
$ otpcr cmd cfg,cmd,dne,dpl,err,exp,imp,log,mod,mre,nme, pwd,rem,req,res,rss,srv,syn,tdo,thr,upt
start a console
$ otpcrc >
use -i to init modules
$ otpcrc -i >
start daemon
$ otpcrd $
start service
otpcrs <runs until ctrl-c>
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
COMMANDS
here is a list of available commands
cfg - irc configuration cmd - commands dpl - sets display items err - show errors exp - export opml (stdout) imp - import opml log - log text mre - display cached output pwd - sasl nickserv name/pass rem - removes a rss feed res - restore deleted feeds req - reconsider rss - add a feed syn - sync rss feeds tdo - add todo item thr - show running threads upt - show uptime
CONFIGURATION
irc
$ otpcr cfg server=<server> $ otpcr cfg channel=<channel> $ otpcr cfg nick=<nick>
sasl
$ otpcr pwd <nsvnick> <nspass> $ otpcr cfg password=<frompwd>4
rss
$ otpcr rss <url> $ otpcr dpl <url> <item1,item2> $ otpcr rem <url> $ otpcr nme <url> <name>
opml
$ otpcr exp $ otpcr imp <filename>
SYSTEMD
$ otpcr srv > otpcr.service $ sudo mv otpcr.service /etc/systemd/system/ $ sudo systemctl enable otpcr --now joins #otpcr on localhost
SOURCE
source is at https://github.com/rssbotd/otpcr
FILES
~/.otpcr ~/.local/bin/otpcr ~/.local/bin/otpcrc ~/.local/bin/otpcrd ~/.local/bin/otpcrs ~/.local/pipx/venvs/otpcr/*
AUTHOR
Bart Thate <rssbotd@gmail.com>
COPYRIGHT
OTPCR is Public Domain.
1 maintainer
Metadata
1 maintainer
Release files for otpcr 40
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-40.tar.gz | 4.9 MB | Without provenance | Details |
Release files / otpcr-40.tar.gz
| Download URL | otpcr-40.tar.gz |
|---|---|
| Size | 4.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe3b8a48211951a87a25fb9c6cff77d776874f322868e55d4553e1d7ab144253
|
|
BLAKE2b-256 checksum How to use checksums |
314fd4eb0acd6ccbd060acba2daba0c74a7329283965cb48c422de5981852ef9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for otpcr 40
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.
