381–390 of 1001 posts
Earlier quoted context omitted.
Why let users send messages in the first place? Tell me how you can get any more secure than that.
If Apple had their way, they would LOVE to sell you a $2000 aluminum brick with no screen, speakers, microphone, etc., that still required a proprietary cable to charge.
I have a hard time sorting out the difference between a "restriction" and an "unwillingness to devote resources to making easy".
Restricting something isn't the opposite of devoting resources to make something easy. This is a false, and very strange, dichotomy.
From Apple's docs: https://support.apple.com/en-us/102842
"Message Access Profile (MAP 1.4)
This profile is compatible with iPhone 5s and later.
Message Access Profile allows devices to exchange messages. It's used to receive incoming message notifications on connected vehicles. iOS and iPadOS support these MAP functions on connected vehicles:
- Receive incoming message notifications
- Reply to incoming messages
- Compose new messages
- Browse message inbox
- Mark messages as read"
The documentation talks about "connected vehicles", but can totally be implemented by any Bluetooth accessory.
Earlier quoted context omitted.
Or they mean cap as 'lie' in genz speak. 'No cap' = 'No lie'. in a sentence "I saw an alligator today. No cap"
Gen Z speak? I thought it was 'hood speak' or something. Like: I'm going to cap your sorry ass. I'm not a native English speaker, so what do I know.
Earlier quoted context omitted.
You do realize this is a very infantilizing attitude? Why can't the end user choose its own level of security vs usability? Letting a corporation decide this for all users is just creating a nanny state in different clothing.
I tend to agree with this, but if you look at the PC ecosystem, you'll see that 'leave users to figure out their own security' is a shit show. Phones, for better or worse, contain much more private and personal information about users than their computer I would bet on average. So I understand the urge to make phones more secure by default and to help users avoid foot guns, even if it means restricting their choices.…
There's secure by default, and then there's stuff users can't override even with great effort. Android restricts some dangerous operations by default and makes users jump through a couple hoops to acknowledge the risk. iOS usually forbids them entirely.
Earlier quoted context omitted.
RCS is supported per the standard . Google's implementation uses proprietary extensions. It's not the ivory tower you seem to think it is.
RCS on iPhone just sucks though. All I have is anecdotal evidence, but it feels like I only get late or out-of-order delivery from iPhones. Plus iMessage doesn't allow you to send RCS messages from your laptop, whereas it's easy to do that with Google messages. That makes people with iPhones think RCS is worse than it really is. It's just iMessage that's intentionally hobbled. Not to mention the hostile UI decisions…
I think people forget that Apple is not making devices for the Hackernews community. They are making devices for people that just want something that works pretty well and has reasonable security - even to the extent of protecting them from themselves. They have other things to do with their time than learn about security vulnerabilities and how to avoid them. They want to just click 'yes' on every popup and expect t…
Earlier quoted context omitted.
This whole thread is chockful of thought-terminating cliches, and I say that as someone who grew from a waiter to a developer thanks to Apple and made a lot of these arguments. I also worked on Android Wear's iOS app for working with iPhones. The major problem I see now with these excuses, that I'd like to claim wasn't an issue when I was making them circa 2015-2017, is they're cargo cult (a la Apple likes making thi…
Sorry for going out of subject but I had to ask - how did Apple take you from waiter to developer?
(happy to detail more, like everyone, I love talking about myself :P but figured I'd start with the TL;DR, i.e. the App Store + subsequent boom happened at such a time that made it seems reasonable, years later, to dropout, and having 0 responsibility outside restaurant shifts gave me a fulcrum)
Earlier quoted context omitted.
Step 1: Have the iPhone pop up saying "do you want to be able to send messages?" and let the user decide which devices can send their phone messages. Step 2: Have the iPhone pop up saying "do you want to be able to send messages?" and don't just assume "yes" Both steps would improve security, even if they harm Apple's profits.
We have decades of experience that users will blindly click whatever prompts they need to make the app work.