#libresignal — Public Fediverse posts

If you take the time to read this. You will find that Signal App, like any company, when requested by law must provide the data they may have on a phone number. From the phone number, what meta data is available. That's not much but it's not zero. If you've donate to Signal App and have a little trophy icon on your image, you might be at a higher risk of being identified. If you use your normal bank card. Both the phone number and credit card are fairly easy things to mitigate with prepaid card or virtual cards, VoIP number you don't use anywhere else, and using Signals Apps phone number privacy and user names. And don't use your full fucking name. For fucks sake people, this is your private line. This is still the gold standard but you can do a tad bit more to make it substantially more secure. There even hardened versions of The Signal App like #Molly or #LibreSignal
#signalapp #privacy #encryption

https://signal.org/bigbrother/district-of-columbia/

@nikomat @appgefahren: Oder noch viel besser, man nimmt gleich freie Software mit einem förderierten Netzwerk (Jabber oder Matrix z.B.). Man könnte eigentlich meinen, Leute im Fediverse hätten sowas schon gelernt.

#Signal ist leider eine Firma, die explizit 3rd-Party-Clients von ihren Servern wie auch Förderation mit anderen Servern/Systemen ausschließt. Für mich damit ein absolutes NoGo. (Details: https://github.com/LibreSignal/LibreSignal#readme — Und auf gewissen Systemen war #LibreSignal der einzig mögliche Client.)

@oliver Wobei man da fairerweise sagen muss, dass aktuell mehrere Forks von #Signal gibt, die den offiziellen Server nutzen und (bisher) nicht unterbunden werden. Und nein, ich habe das Theater um #LibreSignal von damals nicht vergessen.
https://www.twinhelix.com/apps/signal-foss/
https://langis.cloudfrancois.fr/
@kuketzblog

@monoxyd, @Kadda: #Signal ist IMHO schlimm, weil es 3rd-party Clients explizit aussperrt. Damit ist mindestens eine der Freiheiten von Open Source passé: Du hast zwar den Source-Code, kannst ihn auch anschauen, aber nicht wirklich selbst modifizieren. Außerdem schränkt das die Nutzbarkeit ein auf Betriebssystem welche die Signal-Leute selbst unterstützen. So ist auch das #LibreSignal für #SailfishOS gestorben. Und Signal für mich.

Will https://github.com/jukefoxer/Signal-Android/tree/feature/wa-db-import get the same Moxie Marlinspike reacation as #LibreSignal did ( https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217211165 )?

"Tusky" isn't a generic word like "office", and the Free Tusky creators are probably at risk of #trademark action for using essentially the same name for such a similar app (#LibreSignal ran into threats of this: https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217664961 ). They might be better too use a tongue-in-cheek variant like Trunky or Toothy, that references its origins, but also gives it a unique identity. Like IceWeasel and IceCat do with Firefox, and IceDove does with Thunderbird.

@bikecurious
> There is Signal-weechat, Signal-cli and hopefully the new qt desktop client will be packaged soon. None were developed by OWS ppl it looks like.

If they're using "Signal" in their name, and they're not developed by OWS, they're likely to face the same fate as #LibreSignal. Moxie insisted that they stop using the Signal trademark, and then insisted that any app not using the Signal branding (and thus controlled by OWS) not connect to their servers.
@gentoorebel @noorul

Anyone else noted the irony of a guy who sells a company called "#WhisperSystems" to a corporation for a few million $, then starts a new company called #OpenWhisperSystems with a product call #Signal, then threatens to sue anyone who calls a fork something like #LibreSignal?

Anyone else noted the irony of a guy who sells a company called "#WhisperSystems" to a corporation for a few million $, then starts a new company called #OpenWhisperSystems with a product call #Signal, then threatens to sue anyone who calls a fork something like #LibreSignal?

@noorul looking to the future, #Wire is supportive of having their #Android app in #FDroid, and they are planning to implement server-to-server federation (possibly using #XMPP):
https://github.com/wireapp/wire-server/issues/631

#Signal have absolutely ruled out both. They have actively worked to block F-Droid from distributing their app (see the #LibreSignal debacle), and they believe federated services are obsolete:
https://signal.org/blog/the-ecosystem-is-moving/

@dgold there's also this piece, which was written in the wake of the infamous #LibreSignal debate:
https://sandervenema.ch/2016/11/why-i-wont-recommend-signal-anymore/

@bikecurious intriguing. Are you familiar with the history of #LibreSignal? Basically Moxie threw his toys about #trademark infringement. He's also said he doesn't want any third-party clients connecting to the Signal servers. If that policy has changed, that would be great, because it would allow another client that can talk to Signal users to be added to F-Droid. Not holding my breath though ...
@gentoorebel @noorul

@ghostdancer @clacke this is why I encourage people to use #Wire instead of Signal, as it is user-friendly for non-geeks, and the Wire devs are much more willing to work towards;
* removing any remaining non-free dependencies from their clients
* having their #Android client distributed through F-Droid
* federating with other E2E encrypted chat systems

If everyone who worked on #LibreSignal went and helped with this, maybe Wire could be in F-Droid in the forseeable future.