Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
For sure very interesting! And its open source and you can run it in your computer if you have the knowledge.
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.