- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
All messages are end to end encrypted. Also you don’t need an Apple account and it connects directly to Apple servers.
All messages are end to end encrypted. Also you don’t need an Apple account and it connects directly to Apple servers.
For sure very interesting! And its open source and you can run it in your computer if you have the knowledge.
Yup, the PyPush python-based proof-of-concept can run pretty much anywhere there’s python.
I’m aware regular Beeper can be self-hosted, but Beeper Mini can too? Is there any more information on this or is that the “if you have the knowledge” part?
The mini version doesn’t need hosting, it doesn’t have a proxy middle man. A 16yo kid reverse engineered the protocol and then got contracted by beeper to implement it as beeper mini. It’s a client directly connecting to apple like imessage native.
Will it break? I’d argue if the cost of breaking it in engineer time is worth doing to Apple, yes. All they’d have to do is roll their own crypto and reverse engineering that might be impossible. Probably easier ways to break it but then maybe it turns into a cat and mouse game.
Legally it’s hard to say if it’s OK too, the end user is likely fine, but the developer especially being contacted may not be since to reverse engineer it could be breaking terms of service or licensing clauses though I’m not really sure what kind of damages could be claimed. To reverse engineer they had to use the original on jailbroken iphones to go through the engineering discovery.
Anyway the point is, it’s not going through beeper or anywhere other than Apple. So there’s no component to host. It’s different to beeper.
The problem is that breaking it will also break a lot of Apple devices.
Hmm you could be right. Keeping old protocols running for legacy compatibility reasons could in this case keep the solution working for some time.
According to Apple users, the color of their bubble has a lot of value
I don’t know about the app itself, but the blog article links to the PyPush python-based proof-of-concept, which you can run pretty much anywhere.
The difference between old and new is that all the services on the old one rely on Matrix bridges and the new one will not. They claim iMessage, Signal and WhatsApp will all be working on-device. So those obviously won’t be self-hosted. The rest they have yet to decide exactly how they will implement them but Matrix is going to be part of it.
Brad Murray said the end goal is to have everyone messaging each other directly on Matrix.