ticketfrei/ticketfrei3
8
1
Fork 0
Code Issues 11 Pull requests 2 Projects 1 Releases Wiki Activity
24 commits 5 branches 0 tags 94 MiB
TypeScript 61.1%
Python 22.2%
HTML 12.8%
SCSS 3%
Shell 0.6%
Other 0.3%
Go to file
maike 10b3ec5be7 [misc] Add contribution guidelines
2020-07-05 19:09:59 +02:00
.github/workflows [misc] Replace flake and pytest with tox in github action 2020-07-02 11:26:28 +02:00
kibicara [misc] Reformat code to match black styleguide 2020-07-02 14:31:53 +02:00
tests/unit [tests] Validate missing body return code in registration 2020-07-02 11:23:16 +02:00
.editorconfig [misc] Add editorconfig 2020-07-02 14:29:59 +02:00
.gitignore [misc] add vim temporary files to .gitignore 2020-07-05 18:07:48 +02:00
CONTRIBUTE.md [misc] Add contribution guidelines 2020-07-05 19:09:59 +02:00
COPYING [misc] Add license file 2020-07-01 20:32:43 +02:00
README.md [misc] Add contribution guidelines 2020-07-05 19:09:59 +02:00
setup.py [tests] Remove tests_install and replace with tox configuration 2020-07-02 11:24:43 +02:00
tox.ini [misc] Replace flake8 with black 2020-07-02 14:30:25 +02:00

README.md

Kibicara

Kibicara relays messages between different platforms (= social networks).

In its web interface, a hood admin (= registered user) can create a hood to build a connection between different platforms.

Users can message a specific hood account on a specific platform (e.g. @xyz on Telegram). This pushes the announcement to all platform accounts of a hood. For example: User A writes a message to @xyz on Telegram (which has been connected to Kibicara by a hood admin). This publishes the message on e.g. Twitter and other platforms which have been connected to the hood.

The admin of a hood has to define trigger words and bad words. Messages need to contain a trigger word to be relayed, and must not contain a bad word.

Kibicara needs to be hosted on a server by an instance maintainer. That way, hood admins don't need a server of their own.

Contribute!

Read CONTRIBUTE.md to learn how to get started.