Hacker News new | past | comments | ask | show | jobs | submit login

> Worst case is Apple keeps escalating the fight knowing that Beeper can't outlast them.

I feel like this is in Apple's DNA. Perhaps Beeper is lucky that Apple needs to support a lot of legacy devices and they might not be able to fully plug this hole without creating a big support nightmare.




Please explain to me why that wouldn't be in anyone's interest?

Why should I pay costs for server uptime and maintenance for clients that I a) did not authorize and b) did not pay for me keeping up my servers and c) actually accept that a third party is getting money for providing said access to my servers?

I really don't get how Apple is to blame for protecting what they pay for.


Apple also uses a lot of infrastructure that they don't pay for on their devices. Everything from open source code used in Darwin to public internet infrastructure. Besides that, if that is the reason that they don't want to offer this, they could offer a paid subscription for Android users.

The reason they block this is not that they cannot afford the infrastructure, it's peanuts for them. It's because they want to continue maintaining the schism in the US where Android users are stigmatized for green bubbles, pushing them to buy iPhones. (AKA exploiting teenagers' insecurity for profit.)


Apple has every right in the world to use open source software if they comply with the code's license. The Beeper client has no right to interact with Apple's servers in a way that involves faking an Apple authorization.

Apple has chosen not to provide an iMessage client. The mere possibility for one existing does not mean Apple can be forced into providing or tolerating one, given that it involves cost on Apple's server side, no matter how small that might be to them (how can you even tell?).

The fact that US teenages stigmatize each other has nothing to do with Apple's business. Apple has always advertized iMessage as an Apple-only messaging platform. If teenagers are to be protected here, it is up to US legislation to create a law that prevents the undesired behavior. Until such a law is present, what Apple is doing is legal, and what Beeper is doing is probably not, they're certainly creating server upkeep costs that they do not pay Apple for, despite Apple telling them clearly not to do so.


> The Beeper client has no right to interact with Apple's servers in a way that involves faking an Apple authorization.

I'm not completely down on the implementation details but is there really anything "faked" here. If they have a service that client and authenticate against using an Apple ID and I just use a different client with my Apple ID then nothing is "faked". It's just implementing the protocol.

> Apple has chosen not to provide an iMessage client. The mere possibility for one existing does not mean Apple can be forced into providing or tolerating one, given that it involves cost on Apple's server side, no matter how small that might be to them (how can you even tell?).

I agree. But if they're going to provide these servers on the Internet without any sort of paid authentication and I can utilize them with an alternative client then I'm going to do that. They don't have to tolerate it.

I also use an adblocker when I browse the web.


>If teenagers are to be protected here, it is up to US legislation to create a law that prevents the undesired behavior.

The Sherman Antitrust Act is broad and vague. It's practical definition depends on common-law precedent. While the system may seem baroque, it offers a kind of stability that has made common-law jurisdictions the preferred arena for most international business across the world. Hence, this fundamentally misunderstands the nature of the relevant competition law.


Who do you think maintains all that OSS in Darwin?


What OSS - why do we have homebrew - Apple stuff is years behind current ever since GPL V3 murked the waters.


> Why should I pay costs for server uptime and maintenance for clients that I a) did not authorize and b) did not pay for me keeping up my servers and c) actually accept that a third party is getting money for providing said access to my servers?

Because you designed the system in such a way that interoperability was impossible without non-customers using your servers?


> I really don't get how Apple is to blame for protecting what they pay for.

I don't think Apple is going to get bankrupt for forwarding a few SMS, they'll be fine don't worry.


"They can afford it" is a terrible argument. There's literally no upside for Apple providing their infrastructure for free to third parties, particularly given that it's a potential vector for flooding their customers with spam.

Up until quite recently, most phone carriers metered the number of texts you could send per month and then charged extra. Many still charge per text when you're roaming overseas. Perhaps Apple could offer API access on commercial terms to third parties but that's their decision.


I really don't think anybody should think about their decision, they are too big for fully owning the platform.

Additionally, iMessage is full of scams and spams already, it's not hard to buy a box of old iphones and turn them into spam relays and that's exactly what is happening now.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: