Telegram Ad Platform

• session-desktop

  301 1,397 0.0 TypeScript

  Session Desktop - Onion routing based messenger

  

I've been wondering the same thing for a while. The closest iteration of this I've come across so far is Session (https://getsession.org)

It routes messages through an Onion/TOR-like network of nodes that others volunteer to run. In return for running those nodes, they generate the Oxen cryptocurrency, similar to how mining Bitcoin works.

This way, it's not fully centralized like WhatsApp/Telegram/etc, but also solves the issues of devices directly communicating, like what happens when the app isn't running on the phone.

• cabal-club.github.io

  5 9 4.3 HTML

  cabal website

  

There are many P2P chat/instant message platforms but they are very niche.

For example: https://cabal.chat/

There isn't a way to monetize an open P2P protocol, or even a "captive user base" to sell to VCs for a cash exit so not a lot of development has been done on that area. (And I would be highly skeptical of any "blockchain" P2P Chat proposal)

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• matrix-doc

  71 749 9.5 HTML

  Discontinued Proposals for changes to the matrix specification [Moved to: https://github.com/matrix-org/matrix-spec-proposals]

  

An example of resolving conflicts is something like MSC2962 (https://github.com/matrix-org/matrix-doc/pull/2962) and MSC3216 (https://github.com/matrix-org/matrix-doc/pull/3216). Two proposals to solve the same problem, different ways. The first one was written by me; the second one was written by joepie91, who's a completely independent community member. Doesn't get much more of a direct conflict than this.

So, to resolve it, the spec core team (which is a mix of element employees and community members) went through the two proposals to compare them and concluded that joepie91's approach is better. So we're about to kill off MSC2962 and merge MSC3216 into the spec instead.

Please stop with all the disinformation - it'd be way more constructive to invest your energy into improving XMPP than trying to make Matrix out to be evil.

Suggest a related project