Beeper was made by the pebble dev. Eric should have read the goal by Eli goldratt, it's a case study of TOC. I still love my slides of time. Pebble: https://en.m.wikipedia.org/wiki/Pebble_(watch) https://www.kickstarter.com/projects/getpebble/pebble-time-a...
For anyone confused, "TOC" refers to "theory of constraints": https://en.wikipedia.org/wiki/Theory_of_constraints I also enjoyed The Goal and found it helpful for my manufacturing business, although I'm having trouble understanding how it connects to this blog post.
Show HN: Beeper Mini – iMessage client for Android
41–50 of 902 posts
Re: Show HN: Beeper Mini – iMessage client for Android
#42How does the generation of validation data for registration work? As far as I understand, this requires details from an actual Apple device (serial number, model, etc.)
Re: Show HN: Beeper Mini – iMessage client for Android
#43This write up adds so much more to that respect. It would have been easy to botch this, it would have been easy to do a worse implementation that would have caused problems for users whether they cared or not, but Beeper seemingly took the time to get right.
Congrats to Eric and the team on the launch!
Re: Show HN: Beeper Mini – iMessage client for Android
#44Earlier quoted context omitted.
What's Pebble? It's mentioned on the Beeper home page too with no context as though everyone should know what it is, sadly I don't.
One of the original smartwatches, if not the original: https://www.kickstarter.com/projects/getpebble/pebble-e-pape... (At least I think that's what the word salad of parent is referring to.)
Re: Show HN: Beeper Mini – iMessage client for Android
#45> Everything changed in August when a security researcher reverse engineered the iMessage protocol.
> At a high level, here’s our product plan for the near future (in very rough order, and very subject to change): > Add support for SMS, WhatsApp and Signal into Beeper Mini, using the same end-to-end encrypted client-side connection architecture. No cloud servers in the middle.
so they are changing their whole business model to rely on illegal proceedings, breaking the ToS of every service they want to provide an alternative for.
I'm pretty sure Apple isn't fond of random people using their servers and their proprietary protocol on a client they haven't created. Signal is the same, they C&D every fork that becomes popular, the only official clients are the CLI and the ones they release (Signal is open source though). WhatsApp is also similar.
It's interesting and disappointing to see that they are hoping to create a business model on top of that, and it will probably backfire and hurt Matrix users as well, because these chat companies will become stricter and completely forbid third-party clients.
Re: Show HN: Beeper Mini – iMessage client for Android
#46How does the generation of validation data for registration work? As far as I understand, this requires details from an actual Apple device (serial number, model, etc.)
Re: Show HN: Beeper Mini – iMessage client for Android
#47OK, took a while to figure out what it is, as I barely know anyone using iphone. Though it's not for me, BUT if they deliver this: > Over time, we will be adding all networks that Beeper supports into Beeper Mini, including SMS/RCS, WhatsApp, Messenger, Signal, Telegram, Instagram, Twitter, Slack, Discord, Google Chat and Linkedin. We'll also bring Beeper Mini to desktop and iOS. I'm interested, even if it's paid. I'…
Re: Show HN: Beeper Mini – iMessage client for Android
#48Re: Show HN: Beeper Mini – iMessage client for Android
#49I'm on the fence about using this. I don't want to switch all my conversations over to iMessage and then have Apple figure out how to ban this. That kind of feels like a recipe for lost messages.
They are looking to get banned and completely damage the Matrix/Mautrix bridge ecosystem.