AnAmericanPotato

Almost, yeah. Certainly the big corps.

This is why I strongly favor services that use end-to-end encryption or do not store history in the first place.

There are not many times when I've needed to search back through history on a Discord server, and every time I have I thought to myself "this would be much better on any platform besides Discord". Discord would, IMHO, be a better product if they did not retain history forever.

Ditto for Slack. Slack has the additional gall to limit access to that data unless you pay for a premium plan, despite the fact that they keep the data forever regardless (as evidenced by their occasional free trials which magically bring all history back, and some search tricks you can use to access old posts regardless).

Both Slack and Discord have lulled their user base into a false sense of privacy. Nothing you post there should be considered private.

It doesn't really matter if they do or don't. What matters is that they can change their TOS at any time, they keep an archive of all historical data, and you will have pretty much no recourse no matter what they decide to do with it in the future.

Who knows what will happen to Discord in five or ten years?

They might get bought by a narcissistic billionaire.

They might sell all their data to Google for training AI.

They might go bankrupt and sell off their assets to the highest bidder.

They might have an IPO and begin the usual value extraction at the expense of their users.

I know, I know...crazy ideas, right? When has anything like that ever happened?!

I try not to judge people....unless I see them right-clicking to copy and paste. Ew.

My guess is that this is a teenager, and this is probably their first experience with git and version control in general. Just a hunch.

Anyway, it is reasonable to expect a mainstream GUI app from one of the largest companies in the world to be approachable for people who do not know all the inner workings of the command line tools that are used behind the scenes. And it is reasonable to expect any destructive action to have clear and bold warnings. "Changes will be discarded" is not clear. What changes? From the user's perspective, the only changes were regarding version control, so "discarding" that should leave them where they started — with their files intact but not in version control.

Have mercy on the poor noobs. We were all there once.

I feel bad for this kid. That really is a bad warning dialog. Nowhere does it say it's going to delete files. Anyone who thinks that's good design needs a break.

Half the replies are basically "This should be obvious if your past five years of life experience is similar to mine, and if it isn't then get fucked." Just adding insult to injury.

This is good advice, because email is very difficult to make reliably private. However, it's not the best you can get. Tutanota, for example, stores headers with E2EE, and still has a search function.

The goal should be to make it as private as it can realistically be. Ideally, any cloud service you use should only store end-to-end encrypted data.

I'm not trying to shit on Proton — it's a huge step up from the popular mainstream email services, and the inclusion of cloud storage makes it a much easier transition than going piecemeal with 2-5 different services.

Not the encrypted mail, mind you, because they can’t do that

Just want to point out for anyone new that ProtonMail does not use E2EE for email headers. That means they CAN access your subject lines, to/from fields, and other email headers. That means they CAN be forced to hand it over to the government.

Source: https://proton.me/support/proton-mail-encryption-explained

Subject lines and recipient/sender email addresses are encrypted but not end-to-end encrypted.

Personally I am disappointed in a lot of Proton's wording about this. They frequently promise they can't access "your data" and "your messages" when they do, in fact, store potentially sensitive data in a format they CAN access.

Using an ad-blocking DNS server solves most of those problems. Mullvad offers a public DNS server with no account required, but there are plenty of options out there.

You should still use a browser extension on top of that for pattern-based URL blocking, but a DNS-based blocker should be your first line of defense.

A good ad-blocker goes a long way. You can block all Google domains with minimal impact to non-Google services.

30 years ago, maybe. Post-Napster, not relevant. Most online piracy is non-commercial now, and it's still illegal across most of the world.

This is how Arc behaves by default, and it drove me crazy. The cons of it appearing when I don't want it far outweigh the pros of saving me a single click when I do want it.

A simpler, less ambitious alternative is Clickbait Remover: https://github.com/pietervanheijningen/clickbait-remover-for-youtube

It replaces thumbnails with stills from the video. You can select between beginning, middle, and end.

It doesn't change titles but it lets you force capitalization to lowercase, titlecase, or sentence-case. Keep in mind that this has no logic to retain capitalization of proper nouns no matter which option you choose. I set mine to lowercase just to have some kind of consistency, because I got sick of random ALL CAPS TITLES.

I haven't used DeArrow myself. Crowdsourcing titles sounds interesting but I appreciate that Clickbait Remover behaves exactly the same way with 100% of videos.