I upvoted because the phone number requirement is the n°1 problem with Signal.
But to be clear, Signal does meet F-Droid’s policy (albeit with a “centralized service” antifeature flag). The only reason Signal is not distributed on F-Droid is because Signal threatened legal action if it ever was (LibreSignal scandal).
Also, i appreciate that Matrix (Element is just a client) is a federated protocol. Unfortunately, it consumes a lot of resources server-side (like A LOT of RAM and disk storage), and the default client Element is nearly unusable with high-latency links (eg. over Tor). I personally recommend getting into XMPP… there is no default client because XMPP is an ecosystem not a government-backed startup and some of them really suck (see joinjabber.org for the better clients) but at least the client and server don’t eat all your resources (a “big” XMPP server for hundreds of users uses <500MB RAM, a similar matrix server uses 5-20GB RAM).
Yup Jabber/XMPP has some interesting properties, although the ecosystem is far from the potential it could achieve with more full-time dedicated efforts (and/or more funding to employ people for that). What’s DNM though?
I thought the reason they doesn’t at F-DROID is that they’re using google firebase (I think session uses that too because it’s a signal fork but I’m not sure).
Well that’s the reason upstream Signal was not packaged on F-Droid, that it required Google Play Services to run. That’s why Signal was forked into LibreSignal (which didn’t change anything beyond removing this dependency) which could be distributed on F-Droid. [This ticket]https://github.com/LibreSignal/LibreSignal/issues/37) is where the discussion took place. m0xie from Signal team said:
I’m not OK with LibreSignal using our servers, and I’m not OK with LibreSignal using the name “Signal.” You’re free to use our source code for whatever you would like under the terms of the license, but you’re not entitled to use our name or the service that we run. (…) It is unlikely that we will ever federate with any servers outside of our control again, it makes changes really difficult. (…) I understand that federation and defined protocols that third parties can develop clients for are great and important ideas, but unfortunately they no longer have a place in the modern world
This discussion ultimately led to an article (and a CCC talk) called The ecosystem is moving, to which Conversations developer Daniel Gultsch replied. There was also a more XMPP-centric reply to the talk. Happy reading.
I upvoted because the phone number requirement is the n°1 problem with Signal.
But to be clear, Signal does meet F-Droid’s policy (albeit with a “centralized service” antifeature flag). The only reason Signal is not distributed on F-Droid is because Signal threatened legal action if it ever was (LibreSignal scandal).
Also, i appreciate that Matrix (Element is just a client) is a federated protocol. Unfortunately, it consumes a lot of resources server-side (like A LOT of RAM and disk storage), and the default client Element is nearly unusable with high-latency links (eg. over Tor). I personally recommend getting into XMPP… there is no default client because XMPP is an ecosystem not a government-backed startup and some of them really suck (see joinjabber.org for the better clients) but at least the client and server don’t eat all your resources (a “big” XMPP server for hundreds of users uses <500MB RAM, a similar matrix server uses 5-20GB RAM).
XMPP+OMEMO or OTR is a great alternative, lots of people use it in the DNM realm.
Yup Jabber/XMPP has some interesting properties, although the ecosystem is far from the potential it could achieve with more full-time dedicated efforts (and/or more funding to employ people for that). What’s DNM though?
Dark net markets .
TIL. Tnx.
I thought the reason they doesn’t at F-DROID is that they’re using google firebase (I think session uses that too because it’s a signal fork but I’m not sure).
Well that’s the reason upstream Signal was not packaged on F-Droid, that it required Google Play Services to run. That’s why Signal was forked into LibreSignal (which didn’t change anything beyond removing this dependency) which could be distributed on F-Droid. [This ticket]https://github.com/LibreSignal/LibreSignal/issues/37) is where the discussion took place. m0xie from Signal team said:
This discussion ultimately led to an article (and a CCC talk) called The ecosystem is moving, to which Conversations developer Daniel Gultsch replied. There was also a more XMPP-centric reply to the talk. Happy reading.