darccio

This censorship mechanism comes from 2011, when it was created under the Spanish Socialist Party's government lead by Zapatero. There was a lot of backlash, but the Intellectual Property Comission (also known as "Comisión Sinde") was never dissolved under the next governments' rules.

Re: La Liga's censorship, it isn't promoted by the government but by La Liga itself with the collaboration of the largest ISP, Telefónica/Movistar. Movistar used one of the subsidiaries to denounce themselves and other IPs so they would reach a friendly agreement (again, with themselves) that the judge considered enough to enforce the current Cloudflare blocks.

Indeed, this approach sounds like the way to go for a really independent ecosystem. Thanks for the clarification and the additional insight!

Just to clarify, when you say "self host issues/PRs" is it mostly "self host a knot"? I kind of expected something similar to what you can do for CI but I'm not able to find any docs regarding self hosting issues and PRs outside of Tangled itself.

This approach feels just "add friction to your AI usage". It seems the worst of both worlds, both hand-coded and vibe-coded. You paste your code into a chat so it can tell you what to type yourself (the codebase access rule looks optional, but the copy-paste is one way by design). Replace "chat" with "Stack Overflow" and it'll sound familiar. You don't need to paste code into a chatbox if you're going to do an AI review later anyway.

The security argument is the strongest part of the post, and I don't disagree with it, but what it buys you is the review, and a review catches what you missed, whoever typed the characters. None of the ten dogmas follow from that.

My general approach is to design beforehand, do an adversarial review with AI, socialize it with humans (if needed), generate a plan, and start working item by item. Always keeping me, the human, in the loop (not that `/loop`), going through the steps generating code. Finally, a manual review and one AI adversarial review of the feature branch in a clean context, going section by section manually and discussing anything relevant, and off you go.

Writing code by hand feels great, but even local models can generate fine code. Deterministic linters and quality checks are what keep the quality in line. You can always modify things as long as you're in the process, but at the end of the day, you'll review more than you write. We're closer to being the assembly line's inspector than the crafters we once thought we were.