Go to file

maike ae979c37f9 [tests] Tests for email subscription w/o auth		2020-07-17 15:51:14 +02:00
.github/workflows	[core] Unbreak pdoc3/pytest command line arguments	2020-07-09 18:14:09 +02:00
git-hooks	[misc] Tighten commit-msg hook	2020-07-11 02:02:40 +02:00
kibicara	[email] Subscriber routes don't need authentication	2020-07-17 15:51:14 +02:00
tests	[tests] Tests for email subscription w/o auth	2020-07-17 15:51:14 +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	[misc] Add commit tag for documentation	2020-07-08 13:57:08 +02:00
COPYING	[misc] Add maike to COPYING	2020-07-17 15:51:14 +02:00
README.md	[doc] Update contributing doc reference in readme	2020-07-06 17:27:38 +02:00
setup.py	[email] Use NaCL instead of PyJWT for encoding	2020-07-17 15:51:14 +02:00
tox.ini	[misc] Remove unused python interpreter in tox.ini	2020-07-08 13:24:03 +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 CONTRIBUTING.md to learn how to get started.