Go to file
2020-09-09 18:19:24 +02:00
.github/workflows [misc] Add github action for frontend 2020-09-05 02:09:16 +02:00
git-hooks [misc] Tighten commit-msg hook 2020-07-11 02:02:40 +02:00
kibicara [twitter] Fix issue with twitter exceeding request count 2020-09-09 14:19:21 +02:00
kibicara-frontend [frontend] Add more text 2020-09-09 18:19:24 +02:00
tests [core] Add default trigger value 2020-09-08 13:02:07 +02:00
.editorconfig [misc] Add editorconfig 2020-07-02 14:29:59 +02:00
.gitignore [misc] Add PyCharm project files to gitignore 2020-07-05 19:39:38 +02:00
CONTRIBUTING.md [doc] Make test cycle a subpoint of backend 2020-09-06 20:44:58 +02:00
COPYING [misc] Add maike to COPYING 2020-07-17 15:51:14 +02:00
package-lock.json [doc] Make test cycle a subpoint of backend 2020-09-06 20:44:58 +02:00
README.md [doc] Update contributing doc reference in readme 2020-07-06 17:27:38 +02:00
setup.py [email] Fix email bot 2020-07-17 15:51:14 +02:00
tox.ini [misc] Restrict pytest path to tests/ 2020-07-25 13:32:01 +02:00

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 CONTRIBUTING.md to learn how to get started.