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.
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.
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.
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:
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.
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.
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.
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.
Send a confirm e-mail if the user is not a registered user. Ban any registered users that spam.
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.
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).
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?
Fuck internships. If "trying to pay the bills" got you stuck where you are now, an internship isn't going to help your financial situation. Keep your day job, learn PHP and start freelancing as a PHP programmer. If you need experience tailored toward desktop apps, try ASP.NET instead. The IDE and language are the same you'd be writing desktop applications for. In this day, web apps (especially in companies like Google and Apple) are on the same tier as desktop apps.
It's ok. The "iBrick" billet aluminum rumors were only half true. To put your fears to rest, it turns out it's made of adamantium rather than aluminum. At least, that is what my inside source tells me.
I may be horribly naive, but I was under the impression that the FCC checked things like output of devices as part of the approval process, which the iPhone passed. I'm not saying it's better than any other device, but it seems to have met some standard level of safe output. (Conspiracy theorists need not reply.)
Re:Why didn't they just kill the lawyer?
on
Batman Discussion
·
· Score: 1
Then there wouldn't have been that nice moment between Bruce Wayne and that "lawyer" (I thought he was an accountant since he was going over the books, but whatever) after Bruce saves his ass at the stop light. That was a nice little moment that showed Bruce's true "incorruptible" nature that was easily overlooked.
It seems almost unforgivable that this is happening now with our engineering tools having advanced so much in the last 40+ years, especially now that computers are there to do a lot of the work. Why is it that we can't do now what we were doing in the 60s? Is there too much red tape? Are the engineers less competent? I don't get it.
It's hard to feel sorry for any site admin who doesn't do this. If they are using header includes or a template engine or even DreamWeaver templates, it's easy to add. If they aren't and they are running Apache, all they have to do is add a line to their.htaccess files to add the HTTP header. If they don't have either, many text editors support replacing across multiple documents, so replacing <head> with head and the meta tag will make quick work of that.
Unfortunately, it's the users that suffer, not the site administrator. I think The Web Standards Project should start an initiative to get major sites (e.g. banks) that don't have the meta tag that have broken sites to add it for free for the sites. I'd say Microsoft should do it, but WaSP seems to be a bit more agile.
The Dutch have been living below sea level for a long time. New Orleans has, too. Both have suffered great casualties because of it. I guess it depends on what you mean by "really compelling reason."
Theists do better in society, so that's what he should remind people of, "survival of the fittest". Dawkins should promote theism, as those who embrace God are the fittest to survive in our society, due to social stigmatism on atheists.
I think a lot of the people with a lot of money are Scientologist. That doesn't make them "more fit to survive" than Christians, Buddhists, or atheists, and it certainly doesn't mean we should subscribe to their dubious dogma.
Ability to make money means nothing in the wild. Ability to lead the sheep may be a good trait, but it has nothing to do with religious beliefs. It has more to do with the ability to manipulate the hearts/minds of the people by whatever means available. Religious leaders have a leg up in that area because they are taking advantage of a common thread in humanity (that Dawkins attempts to get people to dispel).
As a developer, Yahoo's work on their JavaScript library, ignoring their other freeware projects like the pattern library and Doug Crockfords talks on YUI Theater, is worth more to the web community than double the stock price. I can't expect share holders to know the good stuff Yahoo is doing for the community, and how things may change if Microsoft buys Yahoo. I think respect is what Yahoo Management thinks they have that is worth so much.
I still use Google for search (and I don't use Y!UI), but I respect the hell out of Yahoo. I don't think Microsoft can cultivate the kind of environment Yahoo has in recent years.
I hope to all that is good in the web community that Yahoo manages to resist a Microsoft takeover.
It was the W3C that decided to make HTML a subset of SGML. They could have done what HTML 5 is doing by creating a "serialization" that doesn't care about the DTD (HTML5 doesn't call for one in the DOCTYPE). As it is, theoretically, I can write my own DTD (a modification of the HTML4 DTD, for example) that adds new elements. Technically, the SGML parser should know and understand those DTDs. To do such, it must download the DTD. Browsers are supposed to be handling SGML docs, but chose to implement against the W3C recommendations instead of caring about the DTDs; the popular ones don't download the DTD at all... they don't even care if it exists or not, which is why the short HTML5 DOCTYPE works as a quirksmode switch but is still valid HTML and renders like HTML should.
Should SGML renderers cache it? Yes. Should W3C bitch that some SGML renderers are downloading their DTD? No. They should have thought about that before they made HTML a subset of SGML. I don't feel sorry for them.
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.
We all know Moss grows in the basement with Roy.
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.
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.
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:
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.
It's in the works. Still plenty of time to meet a 16 month deadline.
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).
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?
I'm expecting a real-life Spider-man by the end of the week.
Fuck internships. If "trying to pay the bills" got you stuck where you are now, an internship isn't going to help your financial situation. Keep your day job, learn PHP and start freelancing as a PHP programmer. If you need experience tailored toward desktop apps, try ASP .NET instead. The IDE and language are the same you'd be writing desktop applications for. In this day, web apps (especially in companies like Google and Apple) are on the same tier as desktop apps.
It's ok. The "iBrick" billet aluminum rumors were only half true. To put your fears to rest, it turns out it's made of adamantium rather than aluminum. At least, that is what my inside source tells me.
I may be horribly naive, but I was under the impression that the FCC checked things like output of devices as part of the approval process, which the iPhone passed. I'm not saying it's better than any other device, but it seems to have met some standard level of safe output. (Conspiracy theorists need not reply.)
Then there wouldn't have been that nice moment between Bruce Wayne and that "lawyer" (I thought he was an accountant since he was going over the books, but whatever) after Bruce saves his ass at the stop light. That was a nice little moment that showed Bruce's true "incorruptible" nature that was easily overlooked.
It seems almost unforgivable that this is happening now with our engineering tools having advanced so much in the last 40+ years, especially now that computers are there to do a lot of the work. Why is it that we can't do now what we were doing in the 60s? Is there too much red tape? Are the engineers less competent? I don't get it.
It's hard to feel sorry for any site admin who doesn't do this. If they are using header includes or a template engine or even DreamWeaver templates, it's easy to add. If they aren't and they are running Apache, all they have to do is add a line to their .htaccess files to add the HTTP header. If they don't have either, many text editors support replacing across multiple documents, so replacing <head> with head and the meta tag will make quick work of that.
Unfortunately, it's the users that suffer, not the site administrator. I think The Web Standards Project should start an initiative to get major sites (e.g. banks) that don't have the meta tag that have broken sites to add it for free for the sites. I'd say Microsoft should do it, but WaSP seems to be a bit more agile.
The Dutch have been living below sea level for a long time. New Orleans has, too. Both have suffered great casualties because of it. I guess it depends on what you mean by "really compelling reason."
I think a lot of the people with a lot of money are Scientologist. That doesn't make them "more fit to survive" than Christians, Buddhists, or atheists, and it certainly doesn't mean we should subscribe to their dubious dogma.
Ability to make money means nothing in the wild. Ability to lead the sheep may be a good trait, but it has nothing to do with religious beliefs. It has more to do with the ability to manipulate the hearts/minds of the people by whatever means available. Religious leaders have a leg up in that area because they are taking advantage of a common thread in humanity (that Dawkins attempts to get people to dispel).
As a developer, Yahoo's work on their JavaScript library, ignoring their other freeware projects like the pattern library and Doug Crockfords talks on YUI Theater, is worth more to the web community than double the stock price. I can't expect share holders to know the good stuff Yahoo is doing for the community, and how things may change if Microsoft buys Yahoo. I think respect is what Yahoo Management thinks they have that is worth so much.
I still use Google for search (and I don't use Y!UI), but I respect the hell out of Yahoo. I don't think Microsoft can cultivate the kind of environment Yahoo has in recent years.
I hope to all that is good in the web community that Yahoo manages to resist a Microsoft takeover.
Seriously. They found a bug. Opera is now 99/100. Game's still on.
But when the test still has bugs that are being fixed, I don't know if getting it out of the labs the fastest is a great idea for consumers.
I suggest watching Douglas Crockford's JS trilogy on YUI Theater.
It was the W3C that decided to make HTML a subset of SGML. They could have done what HTML 5 is doing by creating a "serialization" that doesn't care about the DTD (HTML5 doesn't call for one in the DOCTYPE). As it is, theoretically, I can write my own DTD (a modification of the HTML4 DTD, for example) that adds new elements. Technically, the SGML parser should know and understand those DTDs. To do such, it must download the DTD. Browsers are supposed to be handling SGML docs, but chose to implement against the W3C recommendations instead of caring about the DTDs; the popular ones don't download the DTD at all... they don't even care if it exists or not, which is why the short HTML5 DOCTYPE works as a quirksmode switch but is still valid HTML and renders like HTML should.
Should SGML renderers cache it? Yes. Should W3C bitch that some SGML renderers are downloading their DTD? No. They should have thought about that before they made HTML a subset of SGML. I don't feel sorry for them.
insensitive: showing or feeling no concern for others' feelings
unbiased: showing no prejudice for or against something; impartial.
Seems to me Wikipedia is unbiased, not insensitive. They are attempting to present information, not offend.
Signs was pretty close to that.
Any web developer who uses alpha PNGs or CSS wants it on every Windows machine, whether the user runs it or not.