Announcing: Slashdot Deals - Explore geek apps, games, gadgets and more. (what is this?)

Thank you!

We are sorry to see you leave - Beta is different and we value the time you took to try it out. Before you decide to go, please take a look at some value-adds for Beta and learn more about it. Thank you for reading Slashdot, and for making the site better!



Hulu May Begin Charging For Video Content

somethinghollow Cable? (313 comments)

I have one of these already. It's called "cable." You pay a monthly fee and you get to watch a bunch of different channels with lots of different content. The only difference I can tell between a paid Hulu and cable is that Hulu is only "on demand," has less content, and wants to be PC-only. So, basically, Hulu will be the crappy version of cable.

more than 5 years ago

Brendan Eich Explains ECMAScript 3.1 To Developers

somethinghollow Re:Specification does not dictate implementation (94 comments)

Any "forking" I've had to do is, e.g.:

if(window.addEventListener) {
window.addEventListener('load', init, false);
} else if(window.attachEvent) {
window.attachEvent('onload', init);

It's unfortunate, but not a huge bother. It's rare in my day-to-day JS programming that I run into major compatibility issues beyond whether or not a particular feature is implemented in various JS engines.

more than 5 years ago

Obama Taps a 5th Lawyer From the RIAA

somethinghollow Re:He's lost my vote in next election (587 comments)

Something about Microsoft, Virus, Linux, and looking at things from another perspective. I can't be bothered to flesh that out because I'm too busy downloading MP3s and Obama speeches over P2P.

more than 5 years ago

Why the CAPTCHA Approach Is Doomed

somethinghollow Re:That wooshing sound.... (522 comments)

I don't want to be another "Me, Too" but here are some things I've done that work that don't require annoying, hard to read CAPTHCA images:

  1. Check the HTTP_REFERER for the correct post page. This used to work really well several years ago, but bots have started sending the correct referer. You may filter some this way, still, though.
  2. Put a text field hidden with CSS with name="phone". Bots will automatically try to fill in the information. Before you add the post to the database, make sure the "phone" field is empty. You could also do the same with name="email". If you actually do collect e-mail addresses or phone numbers, you name those fields something else. If they do figure out to leave it empty, you can easily change your code from (example in PHP) if($_POST['phone'] !== '') to if(isset($_POST['phone'])) and pull the field out of the form.
  3. A simple "type 'code' in the following field." Out-of-the-box bots aren't smart enough to figure this out, and if they do figure it out, it's trivial to change the code.
  4. Random challenge / response questions. Make a list of 10 questions with obvious answers (e.g. Q: Fire is what? A: Hot, Q:TV is short for what? A: Television). On the form, display one random question, and 4 random answers and one correct answer.
  5. Send a confirm e-mail if the user is not a registered user. Ban any registered users that spam.
  6. Monitor your spam and have an index of spammy keywords. Often you just need to put the site they link to's domain as one of the keywords. Other times, it'll be some pill.

There are probably more advanced methods (e.g. checking headers, cookies, etc) to detect common bot attributes, but I haven't spent a lot of time researching my spam for that.

Most of the off-the-shelf bots are made to perform well on typical forms. If you do something atypical or actively respond to new spam techniques, you can very, very easily defeat a spam bot while investing minimal time without annoying the shit out of your users with CAPTCHAs they can't read.

CAPTCHAs are the worst usability anti-pattern and they need to go away.

more than 5 years ago

Mozilla Contemplates a Future Without Google

somethinghollow Silly For Both (200 comments)

Google would be silly not to renew.
1. Firefox users make up a huge market of potential revenue.
2. Chrome users + Firefox users make up an even bigger market.
3. Chrome users make up a much smaller market than Firefox users.
4. It may put hurt on the Mozilla foundation, which may effectively kill a great standards based browser. That doesn't mesh well with what I understand to be the goals of Google.

If they do, I can't imagine the majority of Firefox users leaving the default search in place. Rather, they would set it to Google anyway. So, unless the new default is really compelling, Mozilla won't benefit much, anyway (unless they get paid JUST for having it as default, not based on how many queries are run).

more than 5 years ago

Oklahoma, Vatican Take Opposite Tacks On Evolution

somethinghollow Hypocritical? (1161 comments)

Is the bill not itself guilty of demonstrating an intolerance of diversity by attempting to prevent someone with opposing views from speaking about those views?

more than 5 years ago

Spider Missing After Trip To Space Station

somethinghollow Re:Radiation + a spider (507 comments)

I'm expecting a real-life Spider-man by the end of the week.

more than 6 years ago



Acid 3 Test Problematic

somethinghollow somethinghollow writes  |  more than 6 years ago

somethinghollow writes "The Acid 3 test, despite the Opera / Safari battle, is still under scrutiny. Apparently, OS X (independent of other platforms) has some font rendering issues (a recent development) that are causing problems on the Mac platform for Safari. According to the proprietor, Ian Hickson, there may be:

...a few more minor changes as people track down the last few remaining problems...

While the Acid Tests have been a major boon to the web standards community, the coverage of the Acid 3 test has been problematic. There has been quite a few errors in the test due to immaturity. The fact that this has been seen as a race reveals problem. Acid tests, out of the box, are not a panacea. To the web standards community, this is not a race, but a step in the greater goal of bringing a compliant, cross-platform system for development. This tit-for-tat is boring and irritating to real web designer / developers since the release versions are still far away. What's important is that browser vendors (specifically Opera and WebKit, whatever order you prefer) are dedicated to the goal of web standards.

Who crosses the goal first isn't important. What is important is that all the browser vendors work hard to implement web standards, and release browsers when they are mature enough to improve the landscape."

Link to Original Source



somethinghollow somethinghollow writes  |  more than 11 years ago

As of May 30th, my karma officially became neutral.

I'd like to thank the moderator who modded me up. It's been a long haul, but I'm finally out of the red.

And I also got to meta-moderate...

Slashdot Login

Need an Account?

Forgot your password?