The correct way to get someone to move to FOSS is to show them how to do it, not tell them it exists. OP already said they can do the YouTube -> captioned gif in 10min so you need to provide a simple tutorial that identifies the tools to use, how to set them up, and how to create a workflow to achieve the goal of some format with captions in under 10min.
Notice how I explained what was wrong and how to do it? That’s what’s missing from most “you need to use FOSS” posts, including yours.
This is the house that Jack Welch built, not Thomas Edison. Welch tore down anything that came before and threw up some particle board facades to convince the market there was a skyscraper there.
It doesn’t sound like you’re aware of PCI DSS
Regulatory burden aside, you don’t do data analysis at scale running “some big wigs’ nephew’s VB/C# app.”
I feel like that’s a false dichotomy because it implies there’s a valid reason for the government to physically hurt you. Sovcits have a few screws loose. On a bad day I might have a few screws loose. Do I deserve to be injured because I’m acting erratically? Where’s the line where it’s okay for the government to injure you on side and not okay on the other? I feel like that line is probably much closer to “actively shooting people” than “reacting poorly because they’ve lost connection with the reality of government.”
What evidence did you find to support Substack’s claims? They didn’t share any.
You can quickly and easily find good evidence for things like Reddit quarantining and the banning of folks like Alex Jones and Milo Yiannopoulos.
Which claims are empirical again?
I think you very ably demonstrated my point. Thanks!
You’re getting into very sketchy territory by saying a dev who is using a public GitHub repo to solve their problems needs to take it down because of how others are abusing it. Should the original dev be punished by their email provider because they shouldn’t be allowed to use this? Should anything that has potential harm be required to be a private repo? Who gets to decide all of that?
In the interest of specifics, can you point to where this specific list has done harm? I spent a fair amount of time looking around to make sure I wasn’t going out on a limb for someone with neutral views.
But it’s not public. It’s a private blockchain. The immutable ledger aspect only matters if everyone can see the ledger. Otherwise we take at face value all of the things you said. Assume they run one node and that one node is compromised by a malicious actor. The system fails. Extend it to a limited number of nodes all controlled by SREs and assume an SRE is compromised (this kind of spearphishing is very common). The system fails again.
Sure, you can creatively figure out a way to manage the risks I’ve mentioned and others I haven’t thought of. The core issue, that it’s not public, still remains. If I’m supposed to trust Proton telling me the person I’m emailing is not the NSA pretending to be that person (as the Proton CEO suggested), I need to trust their verification system.
The important stuff for privacy is his stance on “accidentally” injecting Brave crypto referral links into user sessions and defending it as a way to make money because he got Mozilla to use Google for cash. Eich will sell your data when he decides it’s the best way for Eich to make money. I got into a Twitter slap fight with him around then about the incongruity of his desire to track and sell users. He doesn’t care. Brave also has VC funding from non-privacy actors which means it’s only a matter of time before everything is monetized. Brave’s layoffs come as Brave is working on monetizing everything its free users do.
You’ve done a great job summarizing the bad things they’re doing!