AI Agents robots.txt Builder | Dark Visitors
A handy resource for keeping your blocklist up to date in your robots.txt file.
Though the name of the website is unfortunate with its racism-via-laziness nomenclature.
See, this is exactly why we need to poison these bots.
A handy resource for keeping your blocklist up to date in your robots.txt file.
Though the name of the website is unfortunate with its racism-via-laziness nomenclature.
We’ve been taught that technological change must be chaotic, uncontrolled, and socially destructive — that anything less isn’t real innovation.
The conflation of progress with disruption serves specific interests. It benefits those who profit from rapid, uncontrolled deployment. “You can’t stop progress” is a very convenient argument when you’re the one profiting from the chaos, when your business model depends on moving fast and breaking things before anyone can evaluate whether those things should be broken.
We’ve internalized technological determinism so completely that choosing not to adopt something — or choosing to adopt it slowly, carefully, with conditions — feels like naive resistance to inevitable progress. But “inevitable” is doing a lot of work in that sentence. Inevitable for whom? Inevitable according to whom?
Generated code is rather a lot like fast fashion: it looks all right at first glance but it doesn’t hold up over time, and when you look closer it’s full of holes. Just like fast fashion, it’s often ripped off other people’s designs. And it’s a scourge on the environment.
This is depressing.
The hard part of computer programming isn’t expressing what we want the machine to do in code. The hard part is turning human thinking – with all its wooliness and ambiguity and contradictions – into computational thinking that is logically precise and unambiguous, and that can then be expressed formally in the syntax of a programming language.
That was the hard part when programmers were punching holes in cards. It was the hard part when they were typing COBOL code. It was the hard part when they were bringing Visual Basic GUIs to life (presumably to track the killer’s IP address). And it’s the hard part when they’re prompting language models to predict plausible-looking Python.
The hard part has always been – and likely will continue to be for many years to come – knowing exactly what to ask for.
From a browser bug this morning, back to the birth of hypertext in 1945, with a look forward to a possible future for web browsers.
You’re in a desert, you see a tortoise lying on its back, and your call is very important to us.
Knock, knock! Who’s there? Control freak (now you say “control freak who?”)
Wake me up when we get to the plateau of productivity.
Language matters.