European. Polite contrarian. Insufferable green. History graduate. I never downvote reasoned opinions and I do not engage with people who downvote mine (which may be why you got no reply). Low-effort comments with vulgarity or snark will also be ignored.
What he said is obviously technically correct, and we all know that he’s playing a difficult game where he has to keep a mad king on side.
Storm in a teacup that only became a news story because social media is encouraging politicians to shout at each other from behind the safety of their screens (like everybody else in society is doing).
if they can read the messages then its not strictly speaking e2ee
Yes, it can absolutely still be E2EE: the message is encrypted and the central server does not have the key. The issue is that the clients (i.e. the "E"s) are controlled by the same entity as the central server, and we don’t know exactly what the client (app) is doing. So the fact that it’s E2EE is somewhat moot.
This is exhibit #1 in the case for open-source software.
PS: you obviously get this, I’m just trying to make it clearer for anyone who doesn’t.
OK. Oz might be a bit of an outlier situation but I stand corrected.
OK I understand better. Interesting information, too.
Indeed. Saigon was effectively renamed by a conquering foreign army, after its leader. Really not a good look but most Westerners don’t know the story. If ever the communist government falls, or opens up a bit, nothing is more certain than that Saigon will become the official name again.
Given those figures, the numbers absolutely would have run out many years ago if every mobile contract was permanent and free of charge. The operators rent numbers from a central registry, just like with domains but with a much more finite namespace. There’s no way you still have access to a number “well over a year” after last paying anything for it. In any country. Perhaps there’s a misunderstanding.
Of course it expires. Otherwise the numbers would have run out decades ago. Depends on the contract but usually it’s around 4 months, you need to check the smallprint
Very weak argument
Lessons are doomed to be forgotten. In this case the lesson of the Mao era, that concentration of power in one person always ends badly.
Another fork freeloading off the Mozilla security team’s work.
To be clear, that SIM will expire after 2-4 months, somebody else will be assigned the number and they will be able to kick you off your account (though not access any undelivered messages messages except undelivered ones).
To avoid this possibility you need to have ongoing access to the phone ID.
The fact that emergency calls still work suggests that it must be doing some minimal pinging.
But that will be root-level stuff, apps are not going to have access to it and apps are most of the game with privacy these days.
Could have written this whole account verbatim. You’re not alone.
Recently I had a related experience when checking into a small hotel:
Etc. For many (most) people it seems it’s becoming all but unimaginable not to be connected and available to anyone who wants to contact them, round the clock. This is not healthy. The fact that a technology exists does not mean we have to adopt it.
Just waiting for a way to show-on-hover the address bar (i.e. the logical companion to vertical tabs) then I can finally scrap my chrome.css
Helpful article. Chinese kremlimology is even tougher than the original version.
Horse door bolted. But better late than never.
This problem is reminiscent of the web-browser conundrum. Perhaps the project is, by its nature, just too ambitious to be left to a small handful of volunteers. An organization, with reputation (and maybe money) at stake, needs to take the reins.
Currently, Flatpak still uses PulseAudio even if a host system uses PipeWire. The problem with that is that PulseAudio bundles together access to speakers and microphones—you can have access to both, or neither, but not just one. So if an application has access to play sound, it also has access to capture audio, which Wick said, with a bit of understatement, is “not great”. He would like to be able to use PipeWire, which can expose restricted access to speakers only.
Oof. Seems that snap (to take the obvious comparison) separates these two permissions. As it should.
Unusually clear and sharp image. Just did some research. This Sherman, the Tarentaise, seems to be named after the beautiful Tarentaise valley in the Alps (home of the ski resort Courchevel). The photo is dated 1 August 1944 but that seems a bit late for a beach landing. In any case it was destroyed on 12 August. The crew escaped with only only minor injuries.
Beyond this project, Ho Chi Minh City plans to complete several other metro and rail lines by 2030
Metro lines in East Asia are like buses. You wait forever and then 3 come along at once. I was in Saigon (the real name of HCMC) a couple of years ago and was disappointed to find that the first line was still not open. But now things are really taking off.
Here’s to copying Hangzhou’s, which opened in 2012 and already has 12 (sic) lines.
PS Entirely to boost the fediverse I make the effort of contributing some light-hearted remarks and even a relevant link. And get downvoted for my troubles. No wonder so many people think social media is toxic.
Yeah sure, I understand all that, indeed it’s pretty much exactly what I wrote. You are simply taking an expansive definition of E2EE where I am using a narrow one. As far as we know, Meta is indeed sending its messages in an encrypted state, end to end, so technically it makes the grade as E2EE. That debate is kinda boring, I was simply trying to point out that this case study illustrates the importance of FOSS. And since you are downvoting me, that’s all I have to say here.