Had to look that up too. My immediate reaction was wondering if Thalasin works for them too?
That’s literally exactly what I said.
Geez, you make some good posts sometimes but interacting with you is a really horrible experience every time. So needlessly hostile.
I said that the DNC should run someone who is more charismatic and younger so that they could more easily beat Trump. Where are you getting the dictator garbage?
You clearly didn’t read what I wrote, but you sure took the time to start talking some more.
The only reason to blindly insist on Biden as the only possible nominee, a bad-mouth someone who discusses an alternative approach, is if you want Trump to win.
I bet we could get Hillary Clinton to run again.
The only reason to vote for Biden at this point is anti-Trump and Blue No Matter Who. Those still apply to anyone else that the DNC puts forward, as a base score, with any actual merits, charisma, or vigor adding to that. This should have been an easy decision six months ago and doing-nothing-and-hoping-for-the-best doesn’t seem to be making the prospects any better.
No, the immediate problem is that we know that people make decisions based on a vibe and who orates better and (out of all of the qualified people in the country) we still hang our hat (and the future of the country) on a poor orator with a bad vibe. It’s 2016 all over again and it seems like nobody’s learned a thing.
This shouldn’t be a hard race at all. Why are we insisting on handicapping ourselves like this?
E2EE is not part of the standard and only exists as a proprietary Google extension, using Google’s servers. Implying that implementing RCS would get everyone cross-platform E2EE is misinformation.
No they don’t (well… they do, but not for this). Bump stocks are a stupid gimmick that were only ever banned in the first place to appease low-information hysterical types.
It’s another tool for the toolbox. How can being more prepared with a more diverse set of tools be bad for any situation? Right now the only tool seems to be posting outraged comments on the internet.
So many weasel words in this declaration, from “major” invasion to stopping the supply of “the weapons that have been used historically to deal with Rafah.”
Next we hear that what’s happening now is only a minor invasion, but they’ve halted the supply of US catapults and siege engines just to be on the safe side.
Poverty and mental illness control, now
That’s exactly what he was saying.
This actually looks like an improvement in policing overall.
-
Shooting an unarmed man isn’t any worse than what we have today and to be fair the guy actually had a gun and not a phone or something.
-
More impressively, it shoots him dozens of times and every bullet connects with the intended target. Not even the window behind him breaks. Cops these days dump their magazines without any regard to the surroundings and hit bystanders or just lose most of the bullets somewhere down range.
This scene may not be dystopian after all.
RCS, as adopted by GSMA , is zero encryption text messaging. RCS with encryption is a proprietary Google product and relies on Google servers.
On my phone, so links may come later. It’s hard to find solid documentation on it, since their encryption extension is proprietary, but it’s been referenced as being based on the Signal Protocol. The Signal Protocol, or every implementation of it that I’ve seen, uses a central “trusted” repository of public keys to tell message originators query to encrypt the message to. For Signal, and I assume Google RCS, that central repository is Google. The protocol doesn’t allow for federation, so any system that is interoperable with Google RCS will rely on Google as the trusted authority.
The private key part I’m much less sure of, since both the Signal and Google RCS clients are closed source. Signal makes you jump through hoops to add a new client, involving one of your currently installed clients. This suggests that Signal isn’t in possession of your private keys. On the other hand, all you need to set up a new Google client is your account password. This suggests that either your keys are held by Google (perhaps encrypted by your account password) or that new keys can be added without needing explicit involvement from current keys.
Of course this is all speculation because the implementations aren’t available for inspection.
So is this going to be standard RCS, which has no encryption and the telcos need to support, or the Googlified version that does E2E encryption but requires storing keys on Google’s servers?
RCS has interoperability issues itself and Google hasn’t been making the situation better.
Yes, so now ceasefire resolutions have been vetoed by Biden, Putin, and Xi. Good company.
This is all such absolute insanity. So disappointed in the human race these days.
Oh yay! Biden is on the same side as Putin and Xi, in disagreement with the rest of the world.
Not quite the win I think you’re going for there.