No description
  • C 97.2%
  • Roff 2.1%
  • Scheme 0.6%
  • CSS 0.1%
Find a file
2024-07-03 22:28:31 +02:00
src [MOD/WIP] Threading, and bot "API". 2024-07-03 22:28:31 +02:00
.gitignore [MOD] One-way Matrix->XMPP comms. 2024-06-17 18:26:37 +02:00
COPYING.AGPL [META] Actually start licensing 2024-06-23 01:22:10 +02:00
COPYING.CC0 [META] Actually start licensing 2024-06-23 01:22:10 +02:00
COPYING.TELO [META] Actually start licensing 2024-06-23 01:22:10 +02:00
LICENSE [META] Actually start licensing 2024-06-23 01:22:10 +02:00
Makefile [MOD] Add x-parsee tag with metadata, global nicks 2024-06-22 22:43:58 +02:00
README.MD [ADD/WIP] One-way chatstates, capabilities 2024-07-02 02:21:31 +02:00
XEPS-TBD.TXT [MOD/WIP] Threading, and bot "API". 2024-07-03 22:28:31 +02:00

Parsee - the jealous XMPP<=>Matrix bridge

Parsee is a Matrix<=>XMPP bridge written in C99, with Cytoplasm, similar to Bifrost, but it is NOT a drop-in replacment.

Why?

Naming

The name 'Parsee' is actually a reference to Parsee Mizuhashi, a "bridge princess".

Reasoning (personal to LDA)

I hate Bifrost. I also wanted to dip my toes in XMPP, XML, and bridges a bit. Also, as a sister project to KappaChat, this means that I can integrate Parsee with KappaChat however I wish it to be, which allows me to mess around with a codebase I'm already familiar with.

"Why not just use Matrix lol"

"Why not just use XMPP lol"

These two having the same answer should be enough information. Also can I just have fun?

Also dependency bad.

BUILDING

$ make # This generates a 'parsee' executable.
$ 

DEPENDENCIES

Parsee tries to avoid dependencies aside from Cytoplasm.

RUNNING

TODO

DOCS

TODO

TODOS

  • Look at XEPS-TBD.TXT for XEPs to be done
  • Achievements

Why?

"[...] and it [BoVeX] has an achievement system, because another thing I don't like is when software will not acknowledge that you've reached an obscure error state, essentially outsmarting it." - Tom Murphy VII