20 karma · joined May 25, 2012
So it seems to me at least one person has designed a system that allows this and keeps out spam without using a CAPTCHA.
Consider this:
CAPTCHA is prohibiting comments based on the manner in which they are submitted. But what are really trying to stop? "Spam". How do we know what is "spam"? We look at the content. It might be hard to define "spam" because it is a subjective determination. But we know it when we see it.
What if someone writes some interesting content that is "not spam" but wants to submit it in an automated fashion? CAPTCHA stops him from doing that.
CAPTCHA stops automation. It may stop spam. Or may stop something else.
That's my issue with CAPTCHA. It is not aimed at spam, at least not directly. It is aimed at automation.
We cannot just assume that everything that is automated is something we need to stop simply because it is automated.
Maybe the design of email is the problem?
Maybe the design of blog comment systems are the problem?
CAPTCHA's are aimed at stopping automation. That appears to be the only criteria they filter on. It just seems strange.
Of course CAPTCHA's will eventually be useless. Because most of us are working our tails off trying to push automation forward, not find ways to block it simply because it is automation.
Are you the type of person who like to take things apart and put them back together? Do you like to figure out how things work?
Here's how to set up your hobbyist .js TLD. First, run your own mirror copy of the internic root and add an entry for your authoritative .js server. Second, run a recursive server and prime it with your enhanced copy of the internic root. Finally, tell .js fans the IP of your recursive server. Voila, a new TLD for anyone that wants to use it. .js fans that want to use the TLD simply need to change their DNS settings to use your recursive server. The .js fans still get all the same TLD's everyone accepts as "ICANN-approved", plus they get the .js TLD. For those who don't want anything to do with this TLD (and prefer to endorse the ICANN protection racket approach to new gTLD's), this affects nothing. Unless they change their own DNS settings to use your recursive server, they will never see the .js domain. All clean. Zero pollution.
Learn enough to not be spied on and manipulated by sociopathic web developers and cybercriminals.
Maybe you can contribute something back to programmer/user community that demonstrates ethical principles. Maybe you found a startup. Maybe you make a career out of writing programs.
At the very least, you make it harder for the bad actors who use their coding skills to take advantage of people who are not tech savvy.
Or it could be some sort of language popularity measure.
Put two one-liners that do the same thing (not necessarily in the same language) side by side and let people choose.
Instead of gist maybe use rosettacode?
Why not just run the application from your own machine?
Same interface, same commands, superior performance and security.
How about letting users add abstraction if they want, but not forcing it on them?
Maybe Amzn is just not too skilled working with various bootloaders?