Samsung has me seriously considering... (Page 4 of 4)
|
Originally Posted By scuba_steve: JFC, seriously? |
"As God is my witness, I thought turkeys could fly." A. Carlson
|
Originally Posted By M855Bukkake: You are trusting words, not code. The list of exploits that have been found, often deliberately placed, in closed source systems from big tech companies is miles long. If they won't publish the code, it cannot actually be trusted. Originally Posted By M855Bukkake: Originally Posted By C3H5N3O9: Originally Posted By M855Bukkake: Originally Posted By scuba_steve: Originally Posted By 1775: Honestly the iPhone people who are actually like this in real life are one of the reasons im still on an android. If a text message being in a different color bothers you that much, you're a tool and I dont want associated with your cult. Really, the iPhone controls annoy me. The keyboard sucks, having to swipe instead of hitting a button to see open apps, and not having a close all apps button keep me from switching It's not just the message bubble color. There is (or at least was) a functional reduction to the chat. Adding an Android user to an iMessage chat previously forced the swap of the app from an Apple-proprietary messaging protocol to standard SMS/MMS, which reduced some features for the users in that chat. Some examples include loss of read receipts / typing indicators, reduced quality of media pasted into the chat, and breaking group chats, requiring creation of a new group chat to accommodate the Android user. And although users likely didn't notice, falling back to SMS/MMS instead of a more modern protocol, like RCS, also broke encryption for the chat. Of course, iPhone users hated this and would blame the Android user, instead of Apple, for creating a messaging app that used a proprietary protocol that wasn't compatible with 70% of the mobile devices in the world. And Apple doubled down on this limitation for years, even though creating an Android version of iMessage would have been fairly straightforward. One might infer they failed to do so to give their users a sense of superiority, or perhaps just to lock them in, for fear of being a green bubble, but whatever the reason, it's clear creating a cross-platform version would have been easy for one of the wealthiest companies in the world. Whatsapp did it. So did Signal. But they chose not to, continuing to imply Android users were to blame. The greatest trick the Devil ever pulled was convincing the world he didn't exist.  Apple did eventually agree to at least adopt the open RCS standard for communicating with Android users, after being publicly shamed by Google in a media campaign they ran several years ago.  https://www.youtube.com/watch?v=N_B0riy__rwAnd I believe that has addressed most of the major issues. https://www.youtube.com/watch?v=dBWFVAoNuZUTrusting a closed source messaging app from Apple to use meaningful encryption is like trusting some skank from a bar to be STD free and on the pill. You have no way to know it's true and a dozen ways to get fucked. The iMessage encryption was formally verified by third parties and the source code was reviewed by a third party. It's been post quantum since 2024. https://security.apple.com/blog/imessage-pq3/ You are trusting words, not code. The list of exploits that have been found, often deliberately placed, in closed source systems from big tech companies is miles long. If they won't publish the code, it cannot actually be trusted. You’re trusting someone is reviewing and patching the open source, and that everyone working on the projects are good people. https://infosectoday.com/cybersecurity-threats/malicious-actors-are-currently-taking-advantage-of-weaknesses-in-the-open-source-ecosystem-to-distribute-harmful-software/ Everyone has to trust someone at some point. |
We're getting close, real close. And now for some more bad news... Ready?