mirrors/Parsee
1
0
Fork 0
mirror of https://forge.fsky.io/lda/Parsee.git synced 2026-03-13 12:15:12 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
22 commits 3 branches 1 tag 701 KiB
  • C 97.2%
  • Roff 2.1%
  • Scheme 0.6%
  • CSS 0.1%
Find a file
LDA b820a441ed [MOD] Add x-parsee tag with metadata, global nicks 
Still need to grab it on the room-level from the room state if possible,
otherwise just rollback to the MXID.

I also need to consider profile pictures and bridging media, and check
if the nick was present XMPP-side first, as that can and will cause
issues, especially around semi-anonymous MUCs.
2024-06-22 22:43:58 +02:00
src [MOD] Add x-parsee tag with metadata, global nicks 2024-06-22 22:43:58 +02:00
.gitignore [MOD] One-way Matrix->XMPP comms. 2024-06-17 18:26:37 +02:00
Makefile [MOD] Add x-parsee tag with metadata, global nicks 2024-06-22 22:43:58 +02:00
README.MD [ADD/WIP] Continue MUCwerk 2024-06-21 00:48:27 +02:00

README.MD

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