91–98 of 98 posts
Earlier quoted context omitted.
Great work! So this is mostly on Google's implementation? Or is RCS insecure in general?
TFA: >SRLabs didn't find an issue in the RCS standard itself, but rather how it is being implemented by different telecos
> Because some of the standard is undefined...
When did carriers ever get anything tech based right? In fact to expect them is wrong as their business model is very different to a tech company. They are beneficiaries of law-bound limited duopolies or oligopolies. In most countries the only audience they care for are the regulators, and not consumers or their security and safety. Regulatory capture is a wonderful thing for these companies and not for consumers.
If Ericsson is considered a carrier, then I'd say Erlang is a good counter-example to this. Though it might be the classic "exception that proved the rule".
Earlier quoted context omitted.
While in RoW iPhones are definitely luxury items, by this very property about half (or more) of people whose decisions matter would have one, and you often wouldn’t want to use technology that doesn’t work on your bosses’ phone.
Is this a troll? You think half of the world's decision makers are in the US?
(aside: is there a name for the extension of Hanlon's razor where one shouldn't attribute to stupidity a simple miscommunication?)
Earlier quoted context omitted.
E-mail doesn't have end-to-end encryption either. PGP doesn't count.
Why doesn't PGP count?
Ideally when talking about e2ee it's not an optional opt in either but that's a whole different debate.
It's so unfortunate that Google couldn't stay focused and make Hangouts competitive with iMessage. I would guess that the issue stems from Hangouts' legacy code base that harkens back to Google Talk. However, it appears their 3rd(?) attempt to replace it with RCS/Messages is failing once again. Google engineers if you're listening - FIX AND IMPROVE HANGOUTS AND STOP WASTING YOUR EFFORTS ON NEW MESSAGING PROJECTS
Now 6 years later there is nobody else (free or paid) that offers what Google offered for free in 2013. Google itself has disabled functionality in Hangouts and put out a deprecation notice. The replacement options have been spread across multiple individual app attempts, some of which have already closed down, none of which actually got to the point of replicating the functionality.
Hopefully some service will come along that mimics what I was able to do in 2013, I just hope Google Voice doesn't get gimped before then.
And of course, RCS is not even end-to-end-encrypted so there is no reason whatsoever to use it over SMS or any other messaging platform. I hope we'll see a good and federated instant-messaging platform that respects privacy and is easy to adopt.
https://www.privacytools.io/software/real-time-communication...
I do think that Matrix really has the chance to stand out from the competitors here.
Particularly in regard to: https://www.privacytools.io/software/real-time-communication...
It's so unfortunate that Google couldn't stay focused and make Hangouts competitive with iMessage. I would guess that the issue stems from Hangouts' legacy code base that harkens back to Google Talk. However, it appears their 3rd(?) attempt to replace it with RCS/Messages is failing once again. Google engineers if you're listening - FIX AND IMPROVE HANGOUTS AND STOP WASTING YOUR EFFORTS ON NEW MESSAGING PROJECTS
No don't fix hangouts, help out with matrix.org. They are really offering what nobody else is these days and making huge progress in the short period of time they've been around.
Earlier quoted context omitted.
Contactless is capped if you're not using Apple / Google Pay. You need the chip for anything over the cap.
Withdrew $1,500 from Bank of Millenium ATM using contactless card and BLIK in Europe. If by Cap we define I could not withdrew it all then that's correct.