I was just wondering how many people opened an account with Citigroup after seeing this news.
Just understand that the "bank error in your favor" could just have easily been a "bank error in their favor". And which of the two do you think the bank is more motivated to fix quickly? Which of the two is going to cause a bunch of "payment denied" errors when, say, your power bill auto drafts on the 5th of the month? And, when that payment denial happens, of course the power company is going to report that to credit agencies. Where will Citi be then? My prediction is that after dragging their feet for a bit, they'll reverse the mistake from their end, consider their obligation complete, and leave you to deal with the aftermath.
tl;dr - run, as fast as you can away, not towards institutions that demonstrate this level of incompetence.
As long as almost everyone keeps buying phones over whose OS and updates they have no control, phone makers will keep getting away this kind of shit. If you "buy" a phone for which the provider can "alter the deal", then you didn't really buy it - you just paid them for your ability to carry it around and use it. If they can alter its function without your permission, then it isn't really your phone.
I'll assume good intent here. What do you propose as an alternative?
If it turns out everyone buys both a seat and an overhead slot, they'll go back to bundling them.
I don't think so. In the same way as a $5 box of breakfast cereal used to contain (say) 48 oz of product but now contains 40 oz for the same price, this is the airlines' way of engaging in shrinkflation.
Did you forget that iMessage currently HAS E2EE? Apple has E2EE. They are not implementing someone else's E2EE that is not part of the standard.
I did not. I also did not forget that Apple has deigned it (in this case, security) only necessary for their users. Everyone else can go suck rocks I guess? Also, why does Apple get a hall pass on creating their own thing and Google does not? Related, to what commonly agreed to standard does iMessage conform?
What part of "BEFORE" was not clear? I am referring to the time in the past when HTTPS did not exist as a standard. I am not creating a hypothetical world in 2023 when there is no HTTPS.
But there was a world BEFORE (I guess we're yelling now?) it. Then (if the wikipedia article on https is to be believed) Netscape added it to their browser in 1994 and it was adopted as a standard in 2000. I know that we have the benefit of over 20 years of hindsight on that one, but was Netscape wrong to implement security on top of an existing transport layer? Or should they have waited for everyone to agree all the while leaving internet users in an insecure state?
But if Firefox decided not to adopt Microsoft's custom encryption system, would you complain about Firefox?
In your hypothetical scenario, if Firefox was being intransigent and refusing to implement any sort of encryption, yes I would. And, to extend your straw man, how many http-only browsers do we have in 2023?
RCS is not end to end encrypted.
Oh? https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fsupport.google.com%2Fmes...
So, phone, phone, phone, and an impractical expensive USB toy.
I know that the post to which you replied had a lot of words in it, so let me help you focus
and you can also print some backup codes just in case
I know what you're thinking... "paper? in this economy?". Yep. Sorry, mate.
It's 2023 and we figured out that mint, a thing you HATE, isn't a necessary ingredient a long damn time ago. Grow up.
Clearer?
One possible reason that things aren't going according to plan is that there never was a plan in the first place.