551–560 of 1001 posts
Some useful history, the AOL/MSN chat wars: https://www.nplusonemag.com/issue-19/essays/chat-wars/ AOL finally "won" that one by making a buffer exploit in their own client part of the required protocol. Later a court required them to allow messaging interop (as part of the Time Warner merger). They never implemented it.
I think one of the underlying issues is that many are now going to be hesitant to even bother with Beeper Mini anymore. I don’t think there is going to be a high tolerance for this game of cat and mouse from the end user perspective I also don’t think goading apple is going to do much here either. Regardless of the current feelings around apple’s walled garden, they are not going to suddenly keel over and give up on…
All Apple needs to do is send a few scary C&D letters from their army of lawyers and this will be done. If they run the infrastructure for imessage, I'm sure there's something in a ToS somewhere that talks about spoofing device IDs and unauthorized use of their services blah blah Apple's sole discretion. In theory I love it but in reality it'll be dead soon as Apple has too much to gain from the walled garden they've…
Earlier quoted context omitted.
Default option is still usual phone call/iMessage in a lot of places - in some you can long press and select another option, but not all. Also, merely opening a separate app doesn't really help. How about instead of having 5 different apps (that the system one sometimes generously allows you to open), you had one app that can seamlessly speak all protocols? You can add multiple e-mail or contacts accounts (even from…
Or just one app that spoke a single protocol that all phones implement, like SMS used to be. That way you wouldn't have to install and juggle 20 apps to cover all of your friend's preferences, and manage which type of messenger they prefer over time.
There was no push for RCS until iMessage came along.
Earlier quoted context omitted.
Acquiring Beeper would paint a giant target on the iMessage team. "Reverse engineer iMessage to make an Android app and get a payday from Apple, guaranteed!" 0% likelihood of that. It would make more sense for Google to acquire them, and start the inevitable court fight with the best legal team money can buy instead of whatever Beeper can afford right now. But Google would probably prefer to stay out of it, so it rem…
For sake of argument, if they acquire the Beeper team and continue supporting it, there is no further incentive for more Beeper-like apps to emerge. Apple would at that point have a leg to stand on when they go after non-native apps, and I think this would actually be a deterrent for copycat attempts and not something that encourages the behavior.
Maybe this came up in the earlier threads (announcement, outage) so I apologize if it's been discussed ... This project is fantastic. The hacker spirit is in full force, and I love a good David and Goliath story. However, all the comments about demanding interoperability and protocols keep confusing me -- I don't consider APNS a protocol (like TCP anyways), it's also not incidental, extra header space to stuff data i…
Uhhhh, what does APNS have to do with any of this? Correct me if I'm wrong, but people want iMessage to be an open protocol. You're talking about APNS, the "apple push notification service", which is something completely different than what beeper is doing and what folks are asking for. The message schema, format, types, encoding, max length, delivery guarantees, etc, like jabber/xmpp [1]. Push notifications are sent…
I’m curious what their best-case outcome is here. It’s fully transparent at this point that Apple has no appetite for a third party iMessage client on any platform and will take whatever technical steps needed to prevent this from happening. I’d wager heavily that even if Beeper plays cat-and-mouse to the point where they’ve exhausted Apple’s budget for blocking them and somehow managed to avoid Apple’s legal team pu…
The best case outcome is to get publicity leading to US and EU antitrust regulators to file a lawsuit against Apple, both of which Apple loses. The conclusion of this lawsuit is that not only must Apple allow access to iMessage, they also must allow changing the default for every component of iOS - messaging app, browser, app store, let you replace Siri with other voice assistants - and to lower the 30% app store fee…
Maybe this came up in the earlier threads (announcement, outage) so I apologize if it's been discussed ... This project is fantastic. The hacker spirit is in full force, and I love a good David and Goliath story. However, all the comments about demanding interoperability and protocols keep confusing me -- I don't consider APNS a protocol (like TCP anyways), it's also not incidental, extra header space to stuff data i…
Uhhhh, what does APNS have to do with any of this? Correct me if I'm wrong, but people want iMessage to be an open protocol. You're talking about APNS, the "apple push notification service", which is something completely different than what beeper is doing and what folks are asking for. The message schema, format, types, encoding, max length, delivery guarantees, etc, like jabber/xmpp [1]. Push notifications are sent…
Earlier quoted context omitted.
iMessage is not about the color of the bubble. While the color is what's most noticeable to the end user, a non-iMessage chat means: 1. Unable to rename group chats 2. Photo sharing quality is lowered 3. Video sharing quality is abysmal 4. Messages traverse carrier networks in plain-text 5. Loss of undo send and delete 6. Loss of inline replies 7. Loss of typing indicators and read-receipts (if enabled) Just to name…
I won't doubt the fact that you know that other cross-platform messaging apps exist.
Earlier quoted context omitted.
The hackintosh community has tools to generate those #s. e.g. https://dortania.github.io/OpenCore-Post-Install/universal/i...
But why is it Apple's responsibility to accept a non-legit/unknown serial #?
I don’t think anyone is arguing that it’s Apple’s responsibility to accept fake serial numbers.
The serial number is an implementation detail and not the core issue, which is Apple’s intentional degradation of the non-iMessage experience, and their stance against interoperability.
If this was all about security, they could accept something other than an Apple serial #, and provide a UX that makes it clear the user is interacting with a non-Apple user. This would address most spam/abuse issues.
But we know that this is about lock-in and not security.
Maybe this came up in the earlier threads (announcement, outage) so I apologize if it's been discussed ... This project is fantastic. The hacker spirit is in full force, and I love a good David and Goliath story. However, all the comments about demanding interoperability and protocols keep confusing me -- I don't consider APNS a protocol (like TCP anyways), it's also not incidental, extra header space to stuff data i…
https://www.wsj.com/tech/personal-tech/why-teens-hate-androi...