Dang, I support your efforts but I just don't have any incentive to pay for a texting app. Normal texting and WhatsApp and discord and Instagram and tiktok messages etc etc are all free. So I just don't really have a reason to subscribe to this.
I recently paid >$1000 for the privilege of access to iMessage when switching from Android to iPhone. I'd have been _much_ happier staying on my preferred operating system and paying $24/yr. (iMessage has, for me, actually been worth it - but still, I frequently find myself wishing that something like Beeper Mini existed so I could go back to android).
Show HN: Beeper Mini – iMessage client for Android
771–780 of 902 posts
Re: Show HN: Beeper Mini – iMessage client for Android
#772Earlier quoted context omitted.
I get spam messages on iMessage and never on WhatsApp, weird
I don't know if I have ever received an iMessage spam, and I have 6 addresses associated (5 emails, 1 phone number). SMS I get spam almost daily.
I've never gotten an automated spam via iMessage protocol.
Re: Show HN: Beeper Mini – iMessage client for Android
#773Earlier quoted context omitted.
Does this still work? that repository appears to be abandoned.
Apple did actually open up the network, there are plenty of third party devices that are 'Find My' compatible. It's intended for integration into things like bikes or scooters. You can buy tags from AliExpress for $5 that implement it. I've been using a few for a couple of months, and no issues so far.
You are referring to being able to track devices via the Find My portal on Apple.com or your Apple devices, but I am referring to being able to merge the networks so that Apple devices will forward pings onto Android's Find My network and vice versa.
Re: Show HN: Beeper Mini – iMessage client for Android
#774Earlier quoted context omitted.
Apple or Meta (WhatsApp) trying to take down something like this would almost certainly be viewed unfavorably by the ever-lurking EU regulators.
Please read this: https://gist.github.com/smashah/667d4d5cf31670ee87547450861a... The game being played here is poker. If they call beeper's bluff then they risk setting a whole industry wide precedent that interop supercedes ToS (that's the only angle). As it stands, ToS based C&D for interop is untested afaik. We as a community need to discuss ToS-trolling and fight against it.
https://github.com/signalapp/Signal-Android/issues/9966
https://github.com/libresignal/libresignal/issues/37
unless the EU rushes out their legislation that interop is not grounds for terminating someone's account, I'm sorry, but they can do whatever they want to with their app.
Would you feel happy if someone used your home network to seed torrents? Using your bandwidth to seed them?
Re: Show HN: Beeper Mini – iMessage client for Android
#775Earlier quoted context omitted.
over 50% of US market (and a few other countries), for starters. Not EU's jurisdiction, but it is a major messaging service.
Yes, I know but I was specifically talking about the EU, since that's the only government legislation for open access.
Re: Show HN: Beeper Mini – iMessage client for Android
#776Earlier quoted context omitted.
How does this address iMessages sent from non-iPhone devices?
If in the data sent across (via Apple servers) the IMEI and serial no of the device are also transmitted, then Apple can in that millisecond query on their various lists/inventories that this device is legit (activated device + IMEI + serial) and if all lights are green, proceed to deliver, otherwise drop it. (perhaps different sets of data can be used, but it must be something that Apple already has, and the user ha…
Re: Show HN: Beeper Mini – iMessage client for Android
#777Earlier quoted context omitted.
But why can you register an iMessage account with no email and no phone number? It doesn’t make any sense to me. Signal avoided that and that protocol is documented.
You can't. Either it sends an SMS to an Apple server, or you need to sign in with your Apple account.
Re: Show HN: Beeper Mini – iMessage client for Android
#778Earlier quoted context omitted.
Well messaging for one thing... Some others: - Find my device features including Bluetooth ping networking (airtags, Tile, Android's upcoming network) - Airdrop/Nearby Share - Bluetooth LE proximity pairing (at least I doubt this works when pairing cross ecosystem) - Carplay/Android Auto - Airplay/Google Cast
> Find My / Airtags Another Apple ecosystem that can be used by non-Apple devices. OpenHaystack [0] has been working well for quite a while. [0] https://github.com/seemoo-lab/openhaystack
Re: Show HN: Beeper Mini – iMessage client for Android
#779Earlier quoted context omitted.
Well messaging for one thing... Some others: - Find my device features including Bluetooth ping networking (airtags, Tile, Android's upcoming network) - Airdrop/Nearby Share - Bluetooth LE proximity pairing (at least I doubt this works when pairing cross ecosystem) - Carplay/Android Auto - Airplay/Google Cast
- Carplay/Android Auto Are there any headunits that only support one or the other? The cheap Chinese unit I got last year supports wireless for both. It would be nice to have an open protocol though, so third parties could develop alternative UIs.
Re: Show HN: Beeper Mini – iMessage client for Android
#780Earlier quoted context omitted.
> apple's unique level of control allows it to produce a superior product with more consistency Another way to read this: Apple has a superior product because they perform anti-competitive practices and don't allow other companies to out-product them. And when they do, they buy them/shut them down before anyone is the wiser.
editorialization. you know as well as anyone that restricting your feature development to your own platform rather than doing a retarded design by committee helps one innovate faster.
You can definitely make the argument about innovation in the messaging space, but RCS is very extensible. RCS Encryption definitely needs to be standardized, but I recommend you check out how Google layered it on top of RCS [1] including handling fallbacks for corner cases like switching your RCS client away from Google Messages before the system realizes it.
This is to say that RCS is pretty flexible, the key is handling the fallback paths in the extension design and working with other vendors to standardize promptly, so we don't end up with the same kind of broken mess that the carriers made.
[1] https://www.gstatic.com/messages/papers/messages_e2ee.pdf