The only way to change the situation is to force those social networks to use their powers more responsibly. Europe’s GDPR law with its right to data portability is a step in the right direction, but it’s not enough. I believe we need more to regain our right to choose what services we use.
I wouldn’t bet much on these laws, because it’s the same EU that’s drafting bills for lawful access to encrypted data - https://www.cyberscoop.com/encryption-europe-tutanota-protonmail-threema-tresorit/
The adoption of the encryption resolution in the European Union does not affect the landscape for encrypted services in Europe immediately, as the resolution is non-binding. But its adoption suggests a “shift in tone and puts pressure on the European Commission to propose anti-encryption legislation in the near future,” the encrypted email service provider ProtonMail has argued.
After portability, we need to discuss about interoperability, which in this case is the ability to contact people that are are using different chat applications than the one you are using. The way email and SMS already work.
I don’t see a possibility for this in Signal, at least as long as Moxie is there pulling the strings and here are his views on federation - https://signal.org/blog/the-ecosystem-is-moving/
When someone recently asked me about federating an unrelated communication platform into the Signal network, I told them that I thought we’d be unlikely to ever federate with clients and servers we don’t control.
An open source infrastructure for a centralized network now provides almost the same level of control as federated protocols, without giving up the ability to adapt. If a centralized provider with an open source infrastructure ever makes horrible changes, those that disagree have the software they need to run their own alternative instead. It may not be as beautiful as federation, but at this point it seems that it will have to do.
This is the first time that I’ve come across this site. That being said, I hoped to see Firefox in mid - high tier, based on the articles I’ve read about Firefox and it’s privacy protection out of the box, like tracking protection.
Is this a legit analysis? Would Firefox move up the ladder if we tweak its config like this?
Decentralized Social Networks vs The Trolls - https://conf.tube/videos/watch/d8c8ed69-79f0-4987-bafe-84c01f38f966
Yeah, that’s a bit bugging. Checking Signal commits could give a clear idea about this.
deleted by creator
I had the same query as well. I don’t know if it has any direct relation to LibreSignal, since it was abandoned sometime back. But, both aims to remove dependency on Google components.
https://github.com/mollyim/mollyim-android#disclaimer
This project is NOT sponsored by Signal Messenger LLC or Signal Foundation.
Absolutely love it!
Any idea how we can get an option to search gifs?
how’s the speed on riseup?
I wonder if Facebook & WhatsApp took us for total idiots. The moment they had set their eyes on WhatsApp, all they saw was data! data! data! and loads of it to make money from.
Check these out. These are like 4 years old, but couldn’t find any recent discussions on that.
I think there’s an issue for this already, but if you write and maintain a place picker library which doesn’t use Google Maps that’s API compatible with the one from play services, we could look at including it.
https://whispersystems.discoursehosting.net/t/share-location-without-gapps-on-android-phone/1246/2
Thanks but I don’t think we’re going to do this. We’d have to rewrite the entire placepicker, and it looks like the OSM Android SDK is a ways behind in MapView compatibility.
https://github.com/signalapp/Signal-Android/issues/5042#issuecomment-170055276
At which point it can become too overwhelming.
Yeah can understand, for ex: when targeted individuals are considered, they probably would be using a de-googled version Android, so either the location services won’t work or, they will use clients like Molly-Foss.
Mullvad has been pretty good so far!
Thanks, will give it a read.
https://signal.org/blog/there-is-no-whatsapp-backdoor/
It is great that The Guardian thinks privacy is something their readers should be concerned about. However, running a story like this without taking the time to carefully evaluate claims of a “backdoor” will ultimately only hurt their readers. It has the potential to drive them away from a well-engineered and carefully considered system to much more dangerous products that make truly false claims. Since the story has been published, we have repeatedly reached out to the author and the editors at The Guardian, but have received no response.
We believe that WhatsApp remains a great choice for users concerned with the privacy of their message content.
There we have it, let’s all switch back to WhatsApp and be done with this issue :D
Jeez, I just looked at moxie’s comments here, and was like woahhhh! - https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217339450
> Some time ago you federated with CyanogenMod. What has changed since then?
What changed was going through that experience. It seriously degraded the UX for our users and held us back in the development process at many times. I'd estimate that all told, we lost about 6 months to a year of progress. It's something we'll probably never do again, and has fully convinced me that federated protocols are a thing of the past in this world of ours.
> I hope you see the difference between LibreSignal and the SignalPlus-like apps that just want to earn something using somebody else's work. I really see the space for a good cooperation here.
If people want to use our source code to develop their own products, that's fine, so long as it's done under the terms of the license. That's the deal we're making with everyone, and I agree that it allows for possible collaboration. However, we are not running a service for other people's products, and we are not letting other people use our name in their products. Those things aren't part of the deal.
> Let's just use XMPP/Conversations and be done...
You have no idea how much I would love it if you did, but the fact that you don't is sadly telling.
It’s something we’ll probably never do again, and has fully convinced me that federated protocols are a thing of the past in this world of ours.
This one!
While I can see the perspective from which this blog has been written. If I understood correctly, centralization makes it easy for the users & reduces friction in switching services, while allowing the services to adapt to the changing landscape.
But, many of the points here, which might have been well intended, doesn’t rhyme well (with me at least). For example, the thing about clients or server in a federated landscape not supporting the same thing, that’s a bit blowing it out of proportion IMHO. When we look around, the devices, the software we use, aren’t the same and don’t work the same for anyone, but it works nonetheless. A standard is something that is hard to adapt quickly or implement, in a diverse ecosystem as this. The talk about IP version being stuck in time, I’m wondering what Moxie thinks should’ve been done about that?
This is like wanting to make everything "Apple"ized, if that’s even a proper word. Everything from hardware to software, built to a specification and custom protocol. If hardware and software are under centralized control, sure you can eliminate most of the compatibility problems and provide what you envisioned. But, that would take way the ability to have something that is different, yet is interoperable.
What we have is an ok’ish ecosystem, where things confirm to some standard, at some capacity, while I at the same giving us the freedom to tinker and have something different.
Yeah, wondering why Signal isn’t federated yet. Is it because they can’t ensure that the federated servers confirm to the same standards or something?
I totally get that. But, it’s an uphill battle to make people you know well, to switch to a centralized alternative, let alone a decentralized/p2p/self hosted one.
KOReader is pretty good in terms of usability and features. Haven’t had any major issues so far.