I'm going to be spending the $2. I don't care about blue bubbles, but I do want the pictures I send and receive not to be massively overcompressed to the point that I can't read the sign or menu or whatever that was just texted to me.So I’m an iPhone user and I use iMessage because it seems convenient and it’s what my family uses.
However, if I were not an iPhone user it wouldn’t even occur to me to use third party apps to try and use iMessage to get the coveted blue (who gives a shit). Partially due to security/privacy concerns, and partially because I want my messages to be delivered reliably, not only until Apple figures out how to patch it’s system.
SMS, email, signal and telegram all work just fine, with WhatsApp and FB/Instagram messenger being fine apart from their ownership.
The real answer is it's complicated. If you go into the Discord channel where all this was reverse engineered they'll have more technical explanations. But from what I gathered if Apple blocks the way this works, they would subsequently break iMessage for all iPhones prior to one of the more recent models. They would also break iMessage for almost all international iMessage users. It's not as simple as patching something. I'm wishy washy on whether Apple will move to break it but if they do it will probably take some number of years to do so.He has no satisfying answers to the "won't Apple just block this?" question.
Apples RCS implementation won’t have encryption because it’s not part of the standard.Apple's rcs implementation doesn't include e2e encryption.. And this system can presumably deregister as well as register, and I doubt Apple will nerf deregistration..
In fairness $2/month isn't terrible and they also allow you to self-host the server yourself for free. It's also built on the matrix API and uses community managed bridges that already exist. I'm of the mind that if they offer self-hosting, it's fine to charge to maintain their workforce and turn a profit.WTF... even if all the ifs already mentioned can be answered or worked around, who in their right mind would pay $2/month to securely message an iOS user, when there are free alternatives that offer more features (ie. video capability)?
Apple doesn’t need this guy to make Android devices iMessage-capable. If they wanted to do it, they would have already. Apple might be interested to make this go away, but now that there’s a demonstration that this can be done, there’s probably a whack-a-mole game coming up.Two things I predict: Apple will shut this down and/or offer him and NDA/position with their Android integration group. (not that it exists to adopt Android but to convince Android users to Get An Iphone..drink AAPL juice!
I'm with you, but some people are not being completely accurate when they say, "all we want to do is talk with friends and family." What they really mean is they want to send high-resolution images and video, audio messages, stickers, reaction gifs, etc., basically, things that require higher-level, more-capable protocols. They're not content with sending text messages.So just use SMS?
That's a rather disingenuous way of phrasing it. Apple know what iMessage can handle. They're not in charge of SMS, MMS, RCS, HMS, or whatever the present lingua franca is between carriers. iMessage is currently only available on Apple devices so if you wish to send a message from an Apple device to a non-Apple device, they simply use that lowest common denominator; it's not that they're bent on preventing encryption.Eric Migicovsky said:Our viewpoint starts from how Apple is forcing iPhone users to send unencrypted messages to Android users.
Good thing Apple announced they were gonna support RCS.To me, it's less about the blue coloring, and more the other features like group chats, high-resolution images and video and voice messages, stickers and GIFs, reply threads, and sent/delivered/read/typing status.
Like, this is what I see on Android when someone on iPhone "reacts" to my message (I was recovering from a cold):
View attachment 69018
It's small, but it's annoying.
Ideally, I'd rather Apple start supporting an open standard like RCS instead of people hacking into their proprietary protocol and system, since it'd be nice if there was something better than SMS/MMS that people could reliably count on everyone with a cell phone number having.
Since spammers can send sms messages a million ways already, I don't see the advantage of using beeper - I am no more likely to believe a scammer because their stupid messages are blue.iMessage spammers are going to crack open that APK to figure out how they did this. Then there will be a flood of iMessage spam, and Apple will have “no choice” but to block their reverse-engineering.
Hmm, I thought Google’s spec for rcs has had encryption in it for years, but the telcos have been dragging their feet on implementing that part of the spec (like Apple)?
When I went to middle school there were classic in and out group dynamics between the kids with generic MP3 players and those whose parents had money for an iPod. Then we went to high school and the kid whose daddy bought him a Mercedes showed us that we could up our social exclusionary game to a whole new level.I should preface this by saying I'm not one of them.. but lots of people do. From my much-younger siblings, who have told me they all (jokingly) say "ew" when they see a green bubble text, to Apple themselves (see the memo in the article).
To technically literate people, it likely doesn't matter as much. But we'd do well to remember we're a small minority. My wife gets almost irrationally angry when she sends me videos of our dogs and I show her the blocky, VGA-resolution video that I received. Explanations of all the layers that Apple puts into iMessage to abstract away the details of sharing high-resolution videos and photos are lost on her. To her and I'm sure many others, the green bubble says "hey, shit's not going to work right when you're communicating with this person."
Which is exactly what Apple wanted. These are classic in-group/out-group dynamics. For those who don't know, this sort of stuff is kind of a big deal to most humans.
The difference is you don't need a Mac, and you don't have to give a third party your apple ID, unlike beeper itself. That'a pretty huge. I wouldn't pay 2 bucks a month for it, though.So what's new then?
Beeper renamed to beeper mini?
Previously it was green and now blue? But even when it was green, still have the same imessage features as right now, just it's now blue?
But Apple built iMessage to facilitate communication between people on Apple devices (Aka their paying customers). Why do you expect them to also provide high quality features to Android, instead of switching to a different platform?I don't care about the blue, I don't want all my shit compressed in chat because I'm not on Apple
I hate RCS...seemed like when I got a new phone that had RCS I started getting a mountain of spam (mostly USPS scams from UK prefixes?) multiple times a day. I disabled RCS and it almost completely stopped.I'll just wait for RCS. I use Google Messages on my Android as well as their web interface on my Windows computer - switching back and forth between Messages and Beeper depending on what kind of device the other user has is just too annoying
But Apple built iMessage to facilitate communication between people on Apple devices. Why do you expect them to also provide high quality features to Android, instead of switching to a different platform?
Yes.In other news, isn't apple going to soon start supporting RCS? Still might be a green bubble, but most of the basic features should be getting added I think?
I have no experience sending files over SMS. However, for what it’s worth, Telegram seems to absolutely butcher image quality, turn all photos into 1MB max files. And yet, I find it adequate for most snapshot sharing.Okay. So if Apple uses SMS fallback and the videos/images are compressed to the point of uselessness, why when i send the same files android-to-android using SMS are those files the exact same as when they were sent? High quality service is worthy of providing use to, but here it seems it's an intentional degradation.
I recall using Meebo in 2006/7 which tied in almost all of the chat apps at the time into a single AJAX web app. It was pretty revolutionary and useful at the time and also added features that didn't exist in the native clients.
That got swallowed up into Google, unfortunately. Though I can't see any reason why this can't be made secure. I also can't see any reason for there not to be a secure app that links accounts like this though there it'd be costly to create and maintain.
If you're sending Android-to-Android, you're probably using RCS, not SMS. SMS/MMS has very low file size limits that necessitate some level of degradation (though, of course, some apps can degrade images more gracefully and less noticeably than others)Okay. So if Apple uses SMS fallback and the videos/images are compressed to the point of uselessness, why when i send the same files android-to-android using SMS are those files the exact same as when they were sent? High quality service is worthy of providing use to, but here it seems it's an intentional degradation.
"Reverse-engineering", oh yeah, that notorious hacking method called "looking at something to figure out how it works".I hope Apple blocks this shit ASAP!!! Especially since it's "reverse-engineered", sounds like a hack that needs to be DMCA'ed into oblivion!
Trillian before that was my go-to in the even earlier 00's. This is what annoys me the most about the modern chat landscape: we've been through this multiple times before. It's supremely annoying to have to keep up on whatever the latest chat app fad is if/when everyone you know swaps to it. New accounts to make, new things to learn, old things to unlearn. If interoperability were just mandated then it wouldn't matter and I could use $whatever_app while others use their preferred app to converse.I recall using Meebo in 2006/7 which tied in almost all of the chat apps at the time into a single AJAX web app. It was pretty revolutionary and useful at the time and also added features that didn't exist in the native clients.
Must be folks by you are different. I have 2 messaging apps, wife has at least three, daughter has at least three. That doesn't include apps like Discord. This is for iPhones in the US (northeast). Is your experience a regional thing?Have you ever tried to have this conversation with a typical iPhone imessage user?
The reason they care about the color is precisely all the other stuff that comes with it. Whether the average user knows it's encryption, high res media, reactions, etc. is another story. But it is most definitely all those other things that made them care about the color.I like how there's all these comments about it being more than just the colour involved, but for the average user who apparently cares about this nonsense, that is literally all they care about. Not like we don't have much bigger fish to fry, or anything. I weep for humanity's future when this is the sort of thing that gets the attention.
But Apple built iMessage to facilitate communication between people on Apple devices (Aka their paying customers). Why do you expect them to also provide high quality features to Android, instead of switching to a different platform?