# Protocols to support

**URL:** <https://discourse.imfreedom.org/t/protocols-to-support/234>\
**Category:** Libpurple\
**Created:** [January 14, 2025, 1:28pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234 "2025-01-14T13:28:10Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [January 14, 2025, 1:28pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/1 "2025-01-14T13:28:10Z")

</div>

This is meant to keep track of what protocols we think or want to support in tree. Remember, we are only supporting open source/spec protocols in tree now.

We also need to decide which protocol we want to implement next. Right now I’m leaning towards sip/simple, simple specifically since the chat features are very basic and we would have a good base to start on voice calls with sip when we’re ready for that.

- ~~irc~~ (already implemented more or less)
- xmpp (based on our libxeme)
- bonjour (based on our libxeme)
- matrix (based on our libmyna)
- sip/simple (based on libsofia)
- rocket.chat
- mattermost
- activity pub (mastodon, goto social, et al)
- @at (blusky)

On top of that, we need to decide which to implement next. So…

_Poll ([view on site](https://discourse.imfreedom.org/t/protocols-to-support/234/1))_

---

<div class="post-metadata">

**Author:** ![ivanhoe](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/ivanhoe/32/24_2.png) [@ivanhoe](https://discourse.imfreedom.org/u/ivanhoe)\
**Post date:** [January 14, 2025, 7:37pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/2 "2025-01-14T19:37:03Z")

</div>

Not sure if they are maybe too niche but [SimpleX](https://simplex.chat/) and [Tox](https://tox.chat/) are open source too.

---

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [January 14, 2025, 9:23pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/3 "2025-01-14T21:23:22Z")

</div>

Maybe too niche for this stage, but something to keep on the radar for sure.

---

<div class="post-metadata">

**Author:** ![sdgathman](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/sdgathman/32/116_2.png) [@sdgathman](https://discourse.imfreedom.org/u/sdgathman)\
**Post date:** [January 14, 2025, 10:00pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/4 "2025-01-14T22:00:04Z")

</div>

SIP is more complex than XMPP for IM and calls, but is widely deployed. Sort of. Me talking to typical business owner with “SIP” phones: “So can you make SIP calls with your SIP phones?” BO: “SIP calls? What are those?” Me: “You know, call name@domain - it’s like email except for phone/video calls and IMs.” BO: “…”

I use XMPP calls from Pidgin a lot. It works great, but the echo cancellation in the audio library is not as good as whatever you get with Element web for matrix in firefox. I have an old fashioned telephone handset that plugs into the headphone/mic jack for that problem.

---

<div class="post-metadata">

**Author:** ![sdgathman](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/sdgathman/32/116_2.png) [@sdgathman](https://discourse.imfreedom.org/u/sdgathman)\
**Post date:** [January 14, 2025, 10:09pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/5 "2025-01-14T22:09:58Z")

</div>

One more thing: SIP support should handle raw IPs. This allows p2p SIP calls without a SIP “server”. Of course you also don’t get server features like call transfer, etc - but it is dirt simple to use without being vulnerable to centralized DNS and TLS, and the address book takes care of memorizing those pesky IP addresses. Use a cryptomesh IPv6 network (cjdns,yggdrasil,pinecone,etc) to avoid any dependency on IANA as well and provide e2e encryption and authentication.

An article about doing this with Linphone a while back: [Decentralize common Fedora apps with Cjdns - Fedora Magazine](https://fedoramagazine.org/decentralize-common-fedora-apps-cjdns/)

---

<div class="post-metadata">

**Author:** ![sdgathman](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/sdgathman/32/116_2.png) [@sdgathman](https://discourse.imfreedom.org/u/sdgathman)\
**Post date:** [January 14, 2025, 10:39pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/6 "2025-01-14T22:39:56Z")

</div>

Looking at “Manage Accounts”, it is not clear how you would create a p2p “account”. There is no login and no server. Maybe leave password blank? You do need a user, as that is part of SIP protocol. XMPP server is so light, it is no big deal to just run one on local machine. SIP server is larger and more complex - so P2P support for a client is that much more important.

Another P2P issue for Pidgin users is likely to be firewall setup. SIP is one of those protocols like FTP that uses a bunch of ports. Configuring firewalld or other to work with P2P SIP is not trivial.

---

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [January 14, 2025, 11:09pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/7 "2025-01-14T23:09:16Z")

</div>

I assume you’re looking at Pidgin 2. For Pidgin 3 we have a lot of stuff to do / change to make stuff like that possible. The biggest of which is overhauling [authentication](https://issues.imfreedom.org/issue/PIDGIN-17875) which is why everything is forced to have a username.

We have to work about NAT’s and firewalls for all sorts of stuff. We’ve started [traversity](https://keep.imfreedom.org/traversity/traversity) to deal with all of that but it’s far from usable as we’ve been focusing on other things at the moment and haven’t gotten to a point where we really need it yet. Obviously this won’t get through an aggressive corporate firewall but it should help a good number of users.

---

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [January 15, 2025, 12:26am UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/8 "2025-01-15T00:26:55Z")

</div>

Actually the more I think about this, wouldn’t P2P SIP just be SIP without registration? And maybe an option to trust random SIP requests.

---

<div class="post-metadata">

**Author:** ![sdgathman](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/sdgathman/32/116_2.png) [@sdgathman](https://discourse.imfreedom.org/u/sdgathman)\
**Post date:** [January 15, 2025, 2:52am UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/9 "2025-01-15T02:52:00Z")

</div>

Yes, there is no registration. You do need a username, because that is part of SIP protocol. But there is no password. A nice feature for the contact list is to blacklist numbers (certain raw IPs or SIP ids - for are authenticated on the cryptomeshes), or to optionally allow only numbers (SIP ids) in the contact list.

When using a cryptomesh, once that is through any corporate/airport/etc firewall, only the local firewall has effect. The IP stays the same regardless of location or clearnet IPs. The cryptomesh IP is a hash or truncated pubkey, and authenticated (unlike telco numbers).

For traditional SIP, there is an authuser and authpasswd that is different from the user part of user@domain. Auththentication is like any federated protocol (eg. XMPP).

Sadly, most “normies” have only used SIP with a telco bridge service, and have no idea that it is actually a federated protocol like email that also works very well fully p2p.

I didn’t vote for Matrix because the encryption part is hard (handling session keys). Apart from that, it is a fairly easy “restful” API. The existing plug-in does ok with unencrypted rooms.

---

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [February 4, 2025, 6:40am UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/10 "2025-02-04T06:40:25Z")

</div>

[meshenger](https://github.com/meshenger-app/meshenger-android) looks interesting, but I don’t see any documentation on the actual protocol so someone would have to tease it out of the code.

---

<div class="post-metadata">

**Author:** ![amirkhandr](https://avatars.discourse-cdn.com/v4/letter/a/2acd7d/32.png) [@amirkhandr](https://discourse.imfreedom.org/u/amirkhandr)\
**Post date:** [December 19, 2025, 11:36pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/11 "2025-12-19T23:36:48Z")

</div>

Please add Matrix then. It would be great since it’s the “Linux Cave" Thingie.

UPD: Ok, I found out [About the Myna category](http://imfreedom.discourse.group/t/about-the-myna-category/169). Still want to see it.

---

<div class="post-metadata">

**Author:** ![ivanhoe](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/ivanhoe/32/24_2.png) [@ivanhoe](https://discourse.imfreedom.org/u/ivanhoe)\
**Post date:** [February 6, 2026, 8:42pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/12 "2026-02-06T20:42:13Z")

</div>

I’d like to add [zulip](https://zulip.com/api/) to the list of possible protocols to support. After Rocket.Chat got restrictive with the free version, Ryzom switched to zulip.

---

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [February 8, 2026, 10:15pm UTC](https://discourse.imfreedom.org/t/protocols-to-support/234/13 "2026-02-08T22:15:07Z")

</div>

So after some investigation, I decided that Zulip is actually going to be the next in-tree protocol. A few quick reasons why are…

- It’s open source
- Well documented
- Encourages third party clients
- Is easy to setup
- Doesn’t require registering applications
- It’s a simple rest based API with HTTP long polling for events.

The Biggest cons I see with it right now are

- The threaded model doesn’t fit well at the moment. We can work around this with message titles for now, but this can help us figureout / finalize our thread support as well.
- There’s not a lot of use of this protocol/network but that might also work in our favor as it’s a niche we can help fill.

I threw together a stub of this last night that just creates the plugin and protocol, but I’m kind of blocked until the account setting stuff is done especially the password stuff.
