Many trusted all the Apple marketing on privacy.
In China, Taiwan, and Hong Kong we saw apps and emoji used for dissent were banned, rooms on private networks like Telegram were pressured to be banned, and encryption keys for iMessage/iCloud were handed over to the CCP.
@lrvick nice thread Lance. I agree and bang on about this all the time.
It feels a bit lonely "out there" but there are many who do get this as well. If you've not done so yet, check out https://safenetwork.tech which has a great community, and I think ground breaking privacy tech. It's where I put most of my effort in this topic.
@lrvick i am perplexed at how we ended up in this absurd mess.
Decentralization is not some hard to achieve utopia, its the natural state of human kind. Personal spaces, agency built on privacy etc are all deeply ingrained behaviors.
Not to mention that without personal privacy there cannot be any commercial privacy (companies are made of people) and the whole premise of a diversified economy collapses
It think we are living through an aberration. This is not normal
@lrvick problem is, #Matrix is not officially a standard, #XMPP is. Also see https://libreplanet.org/wiki/XMPP .
@adfeno the matrix protocol is public and many are implementing clients and servers.
XMPP while first of its kind, is also heavily XML based and was largely developed without universal end to end encryption, or battery budget in mind.
Matrix corrects a lot of the XMPP failings that made it ineffecient and expensive to scale which is exactly why Facebook, Google, and others abandoned it for their large scale deployments.
@adfeno They intentionally didn't go the IETF route until all the major use cases are covered, however the IETF itself is in the process of moving to Matrix for their own internal use to discuss new internet protocols soooo.... Yeah.
https://mailarchive.ietf.org/arch/msg/tools-discuss/cUd9P35cj-nGsaioZ9HmMLmf1G4/
@federico3 @adfeno Briar is awesome but won't scale nearly as well. You can run your own server and house your own metadata on matrix though. Tradeoffs.
On that note, Matrix p2p is in testing now though where each client can be a server for itself automagically.
@valhalla @lrvick I agree with you.
The argument that “it's bad becaus of XML” is moot. Sure it does consume more resources depending on the message, but with the #XMPP #XEP for push notifications, it provides incentive for account providers to make those push services available for their own accounts, thus no longer depending on #GAFAM and such like.
@adfeno @valhalla @lrvick This old post comes to mind. https://xmpp.org/about/myths.html
Yet, both JSON and XML require linear parsing and do not support zero-copy operation. It's like racing donkeys VS mules.
@cwebber
Synapse is the proof of concept server, anyone is can make their own server code, Dendrite is one such example.
They just need to implement the different specs. This issue is that matrix is growing really fast and servers like dendrite are fairly new. There will soon be a time when dendrite catches up fully and only needs to add new features as and when they come.
@lrvick @adfeno
@lrvick @adfeno This is not true. XMPP works really well in resource constrained environments (and actually, it was developed for it, according to xmpp.org) It does scale far better than current matrix implementations. Missing E2EE definitely is not a problem, as the core XMPP protocol is deliberately minimal. Facebook and Google simply don't want compatibility
@lrvick I don't know why then #Matrix team didn't register the standards officially with a standards body such as #IETF, #W3C, #ISO or #OASIS. This is my major point. Without this, #Matrix team can change the specification as they see fit, without anyone even having a way to say no, nor a test period.
@adfeno Hi there, why wouldn't you mention this topic on Matrix's official forum? I think it must be worth doing so.
@adfeno we are seeing the test period right now. They want to see how the published spec works at scale before they take on the overhead of locking it in stone with IETF.
Meanwhile the IETF itself is using Slack and considering Matrix because there is nothing better atm.
@lrvick @adfeno Using slack is new to me in that context. The WGs I'm active in (CBOR, CoRE, ACE) still use EMail primarily, Jabber for chat during meetings, WebEx during interims and MeetEcho (which integrates Jabber) for the full meetings. Matrix and Zulip(?) got trials at the last full meeting, and at least the Matrix bridge is still up.
@lrvick I agree with you on promoting “protocols over products”.
Isn’t Signal all open source? https://github.com/signalapp
Including the core protocol implementations? https://signal.org/docs/
@bmann yes it is open in theory, but in practice if you run your own server you are not allowed to connect with the Signal network.
If you compile and distribute your own client with reproducible build accountability and external review etc, it is not welcome on the Signal network.
If you choose to write a custom client for a currently unsupported architecture like OpenPOWER or RISC-V it won't be welcome on the Signal network either.
Open source code you can't really use is just marketing.
@lrvick right. So federation not being built in is the core issue.
I’m simplifying obviously, but “go run your own separate network” is the current stance of Signal, vs the Matrix protocol which has federation built in.
Ok, thanks for the info!
@lrvick Don't forget about Keybase, a provider of E2E encrypted chat, being acquired by shady videocalling firm Zoom.
@lrvick what would you recommend instead of signal?
@lrvick If they sold Oculus to Facebook they , in fact, never cared about user privacy.
@lrvick I heard about the censorship, but didn't know about the private keys handover - can you share some details/sources?
@setthemfree china mandated all services that operate in their country must host all hardware and HSMs there and ensure a path exists for user monitoring.
Some left China over this. Apple readily complied. Some more evidence:
https://blog.cryptographyengineering.com/2018/01/16/icloud-in-china/
Apple can run different firmware with different rules on different HSMs, and even encrypt data to an extra special set of keys.
Apple web services in China are hosted locally and controlled by the CCP without question now.
@lrvick Thanks a lot. Wow.
The Oculus VR team intended to protect users on their network from excessive surveillance and abuse.
They sold to Facebook, who told them they would carry that vision forward and never require Facebook accounts.
Facebook changed their mind when they saw value in the data.