S/MIME is insecure, outdated, depreciated, and should be discontinued; yet people don’t want to adapt or grow or change.

Because some organizations do use S/MIME; all email software is required to implement it, that is if they want to be adopted and used by said influential organizations.

OpenPGP and PGP in general is secure but suffers from usability issues and is often wrongly painted as user-unfriendly. (it’s really no worse than S/MIME, installing and managing keys is exactly the same hassle as it is with S/MIME.) The main issue is that some people are too lazy or resistant to change to adapt to it.

Lack of detailed audits…only in this case specifically…does not imply lack of security and/or privacy.

The protocol that Signal uses, which is in fact firmly audited with no major problematic findings, plus the fact the client is OSS is generally enough to lower any concerns.

The server side software in production for Signal.org is not OSS. It will not be. You are required to trust the server to use Signal; because the protocol and the client renders it factually impossible for the server to spy on your messages. The server cannot read messages; or even connect who is messaging who if the correct client settings are used. (Sealed Sender).

Non-OS stats software in general is not automatically lacking in privacy or security, particularly not in this case where the affected software does interact only with software that is verifiably open-source and trustworthy in general due to the protocols and how they are implemented correctly in a verifiable manner.

E2EE is, theoretically, secure. It certainly prevents a government from hoovering up your data when they casually cast too wide of a dragnet while “chasing a criminal”. …At least, when it is implemented honestly and correctly.

Now if governments wanted to properly backdoor some E2EE implementation; all they really need to do is compromise one end of the conversation. Of course, they want to be able to do it auto-magically; through delivering a court order to a single point; and not through busting down the door, or capturing the user of, one end or another of the conversation and compromising the device.

The question therein lies; do you as a person want the government to be forced to bust down a door? Some people think they should be forced to break doors and others do not feel that it is necessary. There are many diverse stances on this question; all with unique reasons.

It’s clear to me that E2EE works properly…the governments would not be trying to “end Encryption” if it did not work. Therefore it stands to reason that E2EE is not compromised, if a government is forced to pass a law in order to compromise the encryption or turn it off entirely. That proves it works.

I just logically proved Encryption works, without even taking a stance on the matter. For the record however; I do support Encryption. I think this law undermining it is a massive governmental overreach that will quickly lead to that same government finding out how critical Encryption actually is to their people. Just give it time.

All that being said; I’m going to be watching carefully.

I still think they have time to backpedal, make it right, and clarify. I don’t permit my installations to talk to their data collection services anyways; via network policies. I have no problem tightening those screws and forcefully disabling their telemetry in other ways as well.

If I have to migrate; well; I already have LibreWolf installed. I might try a few other forks next; to see which ones ‘just work’ with the web properly to protect my privacy while still allowing all websites to work properly as intended so long as I give that website appropriate permissions as I see fit.

I don’t believe that anyone misunderstood the wording.

The problem lies within the broad meaning of the chosen words. If you are angry, you have absolutely every right to be.

Regardless of Mozilla’s intent here they have made a rather large mistake in re-wording their Terms. Rather than engaging with a legal team in problematic regions; they took the lazy way out and used overbroad terms to cover their bottom.

Frequently when wording like this changes it causes companies to only be bound by weak verbal promises which oftentimes go out the door whenever an executive change takes place, or an executive feels threatened enough.

Do not be deceived; this is a downgrade of their promise. It is inevitable that the promises will be broken now that there is no fear of a lawsuit. There’s nothing left to bind them to their promises.

The Mozilla foundation wasn’t ever intended to remain “financially viable”; it was supposed to remain non-profit. They should be “rightsizing” and taking pay cuts instead of slipping a EULA roofie into their terms of use.

It is not only true; it is required by the WMF. Wikipedia and Wikimedia will go dark before it compromises those values.

Wikipedia can always be revived by it’s massive worldwide community; on Tor even. Trump taking down the WMF servers won’t help; the databases probably get backed up daily and would likely end up on torrents within moments of it being taken down.

As an editor with advanced rollback rights on Wikipedia; I can agree with the above statement.

It is Extremely Difficult; even with slighly escalated rollback rights such as mine; to push an agenda on Wikipedia.

WP:NPOV is a good read and the editing community and contribution culture on Wikipedia enforces it strongly.

EnWiki itself for certain has some very strong Page Protection policies that prevent just any editor from munging up the encyclopedia or changing history.

It’s safe to say that Wikimedia cannot be bent or broken easily by special interest groups…Vandalism and PoV pushing is quickly quelled by sysops on Wikipedia. There are more of us editors than Elon could ever possibly hope to take on.

Not even Elon Musk gets to ignore Wikimedia policies. That will never change. They are written in blood and sweat and cannot be manipulated. The entire foundation is set up in a way that it always, eventually, cracks down on corruption and greed. Not even a cabal of admins, bureaucrats and Wikimedia Stewards can help you.

This just means you wrap your signal links in a URL shortener.

A slight hassle; but all the more reason to hate the muskratt.

We should be quietly linking anyone with a need to send a signal link to a nice privacy respecting URL shortening instance somewhere that will basically delete the link in 3-7 days unless told otherwise to keep it around by the user at creation.

Heck; host your own URL shortener while you’re at it.

Vanilla Ice ICE baby…

I.C.E. is obviously overstepping their boundaries here and needs to be pared down.

Someone should get on publishing EFF’s surveillance avoidance tactics in all the languages…or at least teach the immigrants in their lives to make sure to use throw-away emails, prepaid sim cards and pseudo-identities to criticize government.

Genuinely it’s not hard to not provide real world information online; you just keep your identities separated by a few things first. VPNs and Tor help as well to prevent tapping into data.

Actually it’s not that hard and it’s even probably possible to even host SearXNG on the same hardware, or kind of hardware, that you’ve hosted your Pi-Hole or DNS server on.

I actually self-host my own SearXNG and Invidious instances and customize the settings on both, and it’s super useful. (Example: My SearXNG instance is aware of my Invidious instance on my network and will use it to load videos when Invidious is queried via the !iv bang. By doing this I’m not relying on public invidious instances so much; which oftentimes experience downtimes…because youtube hates those more, and frequently bans the public instances.)

This is all doable with a little bit of Docker or Podman action and a bit of editing the appropriate YAML files prior to composing the containers.

So you might be able to spin up a SearXNG instance locally on your network for her to use and configure it to use Google and any other search engines she might prefer. Then use something like LibRedirect (Firefox and Chrome plugin) to redirect her to the local SearXNG instance. (instead of using Google)

A video about setting up SearXNG: https://www.youtube.com/watch?v=UBLypfM9U-g

For some concerning reason; Fwy can’t even find the YouTube version of this video without manually concatenating the video ID to the watch page of fwy’s personal invidious instance. Please, make sure the video is searchable if it’s intended to be live.

An invidious link; this one will take you to public instances so you can find one that’s up and running.

https://redirect.invidious.io/watch?v=B9BWXvn-rB4

Fwy’s own instance, unfortunately, isn’t public; it’s only shared with fwyfwy housemates on a VPN solution.

This is unsurprising. A Chinese model will be filled with censorship.

Ah; yeah. Mullvad Browser is what I mean clearly; as I mentioned it’s maintained by a company, which while they are currently trusted by most people; are always a few management changes away from becoming corrupt and abusing customer trust.

In general Fwy does not agree with the Privacy Guides assessment; and feels that the concerns about the project are simply not credible without stronger evidence of excessively slowed or missed updates.

Project devs do have lives and I’m not personally going to punish that; so long as the software remains reasonably maintained and free of bugs while still considering the project’s number of devs.

Is it better than Mullvad Browser? Probably not in the strictest sense; but I’m also not happy with “Mullvad Browser” either; as this browser makes more choices that breaks functionality than Librewolf does in the pursuit of privacy.

Additionally; I cannot trust that “Mullvad Browser” will not enshittify; it is maintained by a company who is REQUIRED to some extent to make profits. That breeds enshittification. Mullvad would be one bad CEO or core executive team shift away from potentially being targeted as a profit vehicle and it’s privacy benefits weakened or removed entirely so the company can make money.

In general I trust Librewolf on a pretty regular basis to protect my privacy when my Addon-driven version of manually hardened Firefox breaks up a websites functionality too badly. It provides essential privacy protections without breaking too many things and serves as a good baseline browser.

As a rule; I keep several different browsers installed to mitigate lack of website function and isolate away any websites that would be more invasive in what privacy protections must be disabled to use properly. “Setting-Hardened and Privacy-Addon-driven Firefox” is what I use day to day, but “a semi-Amnesic* Librewolf (Incognito windows if untrusted website)” is second and is used daily in trusted website scenarios or in case a website is breaking too badly from plugin interactions. Finally; a fairly vanilla and infrequently used copy of Ungoogled Chromium is kept on hand for situations where Chromium is just required; where I can spin up empty profiles easily for anything I don’t trust and configure it to just flush everything on exit.

Nice writeup as always. I always wondered about Session but it seems like they have the same “I rolled my own” crypto nonsense as Telegram has; and we all know how bad that one actually is as it’s not correctly implemented at all; even if the underlying protocol is otherwise good.

FreeTube is a useful project as it allows you to “fallback” on a non-preferred frontend.

https://github.com/FreeTubeApp/FreeTube

This allows you to continue to use Youtube irregardless of which frontend is (potentially not) working.

In ‘Settings > General’ you’ll want to select “Invidious API” as your “Preferred API backend” and specify your favorite invidious instance in the “Current Invidious Instance” field and click “Set Current Instance as Default”. This locks FreeTube into the specified instance.

Then, when you notice that FreeTube is issuing notices to you about your favorite Invidious Instance being down, you can wander back to ‘Settings > General’; hit the “Clear Default Invidious Instance” Button and wait as FreeTube magically contacts the “https://api.invidious.io/” page for you and selects a new, and hopefully online and working Invidious instance. (You may have to hit this button several times to roll a working instance, Hit the button, check the subs page and see if everything loads, repeat if it falls back on the Local API.)

When you run into instances where you can’t roll up a good Invidious instance; the built in Local API is running a NewPipe Extractor like API directly from your FreeTube client. Not the best; but at least it keeps things working while you wait for the Invidious devs to fix things up; and it still reasonably preserves as much of your privacy as it can while doing this to the best effort it can.

…Sadly this doesn’t work when Google manages a double combo of breaking both Invidious and NewPipe; but I have found that this is less often the case and the devs of either project are usually fairly quick about getting fixes out. Bless their hard work with a donation sometime maybe, if you can.

I find it frustrating that no discernable effort is being visibly made to pass this project on to another dev or group of devs.

Just unceremoniously announcing it’s going down. After a successful fundraiser at the beginning of this year.

I don’t know where the funds went, nor do I understand the abruptness of the closing of the project. I’m suspecting that this is a ragequit. Something happened somewhere quietly that led to the developer deciding that they cannot maintain any longer.

This is, in short, quite disappointing.

To anyone; if you do respond to this comment; do not try defend them. Instead, try to provide more context, or evidence that shows I have misread the situation. Arguing about how long he worked, or how passionate he was in the past, does not change the current facts. Provide more facts if you must argue.

Hearing this sort of law go into effect just makes me sadly want to ban anyone from the UK from my small communities.

I’d hate to be forced to do it; but I certainly would immediately start swinging the hammer with IP range bans and banning anyone who is clearly professing to be from the UK.

Unfortunately the kind of laws they’re trying to pass do nothing to fix whatever problems they have Online; and are basically meaningless political posturing. I feel sorry for people in the UK and strongly recommend they start using VPNs; as it’s the only way to ensure they won’t get snared up in the ensuing waves of bans when compliance with the OSA law that they let get passed is mandatory

The shoe is clearly on the other foot. It’s not so easy to manage when politicians are allowed to get so uninformed that they go out of their way to pass bad laws.

That’s not third person; those are specific pronouns that Fwy uses personally.