6 ms·
Signal team fought a long war against any forks or unauthorised builds of Signal. There are (or were) FDroid repositories with Signal compatible builds, but Mox
by agilob 5y ago
Signal team fought a long war against any forks or unauthorised builds of Signal. There are (or were) FDroid repositories with Signal compatible builds, but Moxie stated that any such build will be considered malware. Signal team was making such builds increasingly difficult to produce.
Official F-Droid repo doesn't allow proprietary dependencies on which Signal depends for some messages (push?)
- paulcarroty 5y ago> Signal team fought a long war against any forks or unauthorised builds of Signal. Yeah, this is main reason why I avoid Signal together with Google Services usage.
- deleted 5y ago[deleted]
- fouc 5y agoWhy doesn't Signal maintain an F-Droid compatible build? (if there's a dependency problem, then they should considering dropping it, release a Signal lite perhaps)
- southerntofu 5y agoMaking your own F-Droid repository was harder a few years back, and UX client-side was bad. Nowadays setting up a 3rd-party repo is as easy as scanning/approving a QRCode (for example for Newpipe repo). Not that i approve Signal's attitude on this topic at all, but there are (were?) technical reasons for which they would do something else. Of course, F-Droid maintaining proper LibreSignal builds in their place alleviates the concern, and that's what Signal team famously opposed. For the uninformed, F-Droid has very serious review/build process for apps and i don't think malware was ever distributed on there (and antipatterns are listed in the UI client-side).
- h4waii 5y agoProbably the same reason they don't maintain a Flatpak, Snap, or any other package other than for Debian/Ubuntu for Signal-Desktop. Which according to the GitHub discussion, the answer is: ????
- SahAssar 5y agoSignal is open-source in the "look at it, but don't even try to tun it" way. I'd rather support a protocol that supports federation and encourages alternative clients.
- southerntofu 5y agoYou mean something like XMPP protocol, which is a widely-deployed IETF standard with robust free-software implementations?
- rakshazi 5y agohttps://matrix.org https://matrix.org is a good one
- southerntofu 5y agoNot upvoting or downvoting, but Matrix is an experimental choice at this point. I have some hope for the near future, but so far Matrix protocol is far from an established standard. > supports federation and encourages alternative clients Currently, the only featureful matrix server (synapse) uses gigabytes of RAM just for a handful of users (see also progress on dendrite and conduit). As for supporting alternative clients, Matrix ecosystem has an overdependence on 3rd party web widgets (eg. Jitsi) for client features because they are not supported by the protocol itself yet, making it harder to implement a native client with good performance and all Element features. As i'm writing this, i realize nheko client now supports WebRTC audio-video calls when a recent GStreamer is available, congratulations on that, and good luck for the multi-platform implementation!