I have a significant visual impairment and love EE. But the number of EE-powered sites that use CAPTCHAs to combat comment spam is disconcerting. I cannot read them at all. I would appreciate it if someone could look into getting an audio CAPTCHA bundled with the visual one.
Here’s a first approach to the subject: Audio CAPTCHA.
What the module does is pretty straightforward. There is one single tag that returns the URL to a dynamically created .wav-file.
You can use this tag as if it was the URL to an ordinary .wav-file and include it in your templates, probably in the vicinity of the {captcha} variable, in any way youu see fit.
Some basic examples.
It may be because I have no 1.wav etc in the audio folder, must we use “audio” as the folder? I’m already using that and all. I did try renaming the top folder to lisajill-audio with all the .wavs in the top level, but got the same problems.
Ok yes, was able to correct the URL issues by editing the template in Firefox. Nevertheless it’s trying to use 60meg of memory. Is that because of the size of my audio files or is something else up?
Eh, nevermind. I’m going to just record them in something other than Audacity, I think there’s a confused MIME type issue. Meh.
They were on mono and the lowest sample rate, but Audacity was being a pain in the neck. I’ll try again and get it going =) It’d be nice to use MP3 though because I already have my flash mp3 player set up for this, so I’m going to wait anyway.
Works great, but my flash player hates it. Which one are you using, silenz? Mine is balking at something, though I’m not sure what, since it works with my entries the way I have it. The second I substitute the hard URL your module creates, it hates me. So time for something that’ll work with it
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 301989873 bytes) =/
This still keeps me wondering…
I ran some tests on the memory consumption of the module. Roughly speaking it seems to usenot much more than about 2,300,000 bytes base memory + the combined sizes of the audio files used.
Even if your files are 100k each, which is a lot, a 6-letter CAPTCHA would leave you below 3M memory usage. Why on earth would it want to allocate 300M?
Works great, but my flash player hates it. Which one are you using, silenz? Mine is balking at something, though I’m not sure what, since it works with my entries the way I have it. The second I substitute the hard URL your module creates, it hates me. So time for something that’ll work with it
I think I know what you mean. I encountered the same. Most players don’t seem to like the URL. I have no idea why, actually.
Back in times of Flash 5 I’ve written some games in Flash but afterwards never got around to do something in Flash anymore.
I’ve been using XSPF Music Player which can play single files as well as xspf-playlists.
So what I did is create an XML-template in EE to work as playlist. In there I use the {exp:audio_captcha:mp3link}-tag to output the URL.
Hrm, see, mine can take a playlist, but since it was just a single audio file I figured I’d just feed it the URL. That’s how I do my “talk to people” entries, but I don’t have anything odd in the URL string in those.
Your code just confused the heck out of me, not in the code manner, but in the, “what about all those other playlists?” manner. Nrr. I’ll have to think on this some more. =)
Your code just confused the heck out of me, not in the code manner, but in the, “what about all those other playlists?” manner. Nrr. I’ll have to think on this some more. =)
I don’t know which other ones, the ones from all the other CAPTCHAs and entries? Seems utterly silly to need an entire playlist simply for one darn mp3 file. I still can’t figure out why it won’t take this URL. The others all have ampersands and =, the only difference in this URL is the addition of a question mark. :(
No, this is just a bogus playlist. It will always contains one title - the URL generated by the module-tag.
There is only one playlist, for all captchas, for all entries, for all users.
The only difference with this approach is just that the module-tag is called when Flash loads the playlist.
Instead of being called in the main template when you would add the URL to the Flash-<object>.
Still confused? Once you grasp the concept, it all makes sense. Just like EE