undefined | Better HN

0 pointsethbr11y ago0 comments

Exactly. It's amazing how often the nuance between may and must is missed by Apple fans.

Apple should be able to lock down their ecosystem as a default -- plenty of people will be happy to use that default experience.

But Apple should absolutely be prohibited from not allowing users the choice of unlocking their own device, for additional functionality, if they choose.

It's also glaringly obvious that many of the "freedoms" Apple affords its users (freedom from iMessage spam!) help drive its revenue...

0 comments

thebigman4331y ago

> It's also glaringly obvious that many of the "freedoms" Apple affords its users (freedom from iMessage spam!) help drive its revenue...

Yea I mean this isnt really hard to understand. 99.9% of users would rather have no iMessage spam and also not be able to publish messages from their 3rd party watch. This works in Apple's favor revenue wise because people value having clean and familiar experiences, and dont feel like they are leaving anything behind

fastball1y ago

Not sure you understand the argument. If you allow people the ability to access iMessage however they want, how do you prevent iMessage spam? You may not care about this, but a lot of people do.

TheBicPen1y ago

How does connecting to a smartwatch enable spam? None of the comments here explain in detail how that would happen. The messages still get sent through an iPhone and through Apple servers. It's not like Apple is giving up any control over those.

moron4hire1y ago

How do you prevent iMessage spam, indeed? Because it's not being prevented right now.

protimewaster1y ago

Can't you already send iMessage spam using Apple Script on Mac? Would it be that much worse if it was also possible from iPhone?

Also, I'm pretty sure you can just set up a click farm to spam from iPhone right now, so there's also that.

VogonPoetry1y ago

It isn't easy to do with just AppleScript on a Mac. I run a sports team and I wanted to send out a message to people for special situations. Some of the challenges are that you cannot script sending a new message if there isn't already a thread -and- it seems like you must use the same contact info (email or phone number). There isn't much feedback when it goes wrong. Some of these do make sense for preventing spam. I suspect I could have used the accessibility APIs to drive the UI. I eventually gave up.

1 more reply

j / k navigate · click thread line to collapse