kepi is a Django-based microblogging system, implemented in Python. It uses the ActivityPub protocol to communicate with other servers, and the Mastodon protocol to communicate with clients.
 
 
 
 
Go to file
Marnanel Thurman a8186fa585 trilby tests:
- ACCOUNT_EXPECTED etc moved to __init__
 - the path param to get, post, etc is called "path" not "url"
 - _create_alice in TrilbyTestCase for now
 - get, post, etc methods in TrilbyTestCase
     (the existing standalone functions are still there for now
      to avoid breaking stuff we're going to refactor soon)
 - test_post_multiple_statuses removed bc pointless
 - test for custom emojis moved to test_instance and
      its path fixed to the correct one
2020-04-16 17:25:17 +01:00
docs Added contribution guide and overview to docs 2019-10-04 17:44:51 +01:00
kepi trilby tests: 2020-04-16 17:25:17 +01:00
.gitignore intermediate 2020-04-06 23:44:35 +01:00
LICENSE.txt Initial commit 2018-08-06 14:44:35 +01:00
MANIFEST.in Renamed entire project from "chapeau" to "kepi". 2019-11-20 19:10:10 +00:00
README.md Renamed entire project from "chapeau" to "kepi". 2019-11-20 19:10:10 +00:00
manage.py Renamed entire project from "chapeau" to "kepi". 2019-11-20 19:10:10 +00:00
requirements.txt "reblog" in StatusSerializer becomes a RecursiveField 2020-04-15 18:24:02 +01:00
runtests.py changed location of test_settings 2018-08-16 18:51:24 +01:00
setup.py Renamed entire project from "chapeau" to "kepi". 2019-11-20 19:10:10 +00:00

README.md

kepi

kepi is an ActivityPub daemon.

ActivityPub is a standard protocol for integrating social media across Internet sites.

For example, you might post an article. Someone else on another site might reply to it, and someone else might "like" it. Someone else again might "follow" you, in order to get notifications when you post anything else.

kepi runs in the background on your server, distributing your messages to other sites, and receiving their responses.

If you'd like to contribute, there's lots to do. Find something on the bug tracker and dive in. If you'd like a gentler learning curve, look for bugs marked "newbie"