I don't have a single lamp in my house that is on for 3 hours a day. The one in my kitchen probably comes close during the week, but just barely. On average, across all the bulbs in my house, each one is used for just minutes a day.
Hence the minor modification to the code, and the manually integrated CAPTCHA. If you use the 3rd-party plugin, you're making the script-kiddie's life too easy.
Some 90% brain-dead excuse for human life takes something off the shelf and points it at whatever software you're running. Unless you're one of the most visited sites on the net, a minor modification to the code, and a manually integrated captcha is going to stop practically everybody from spamming your site.
...is the point going right over the author's head.
A CAPTCHA works well enough for the same reason greylisting works well enough. They may be trivial to bypass (for some definition of 'trivial'), buy many applications only need a tiny speed-bump to make a huge difference in undesirable traffic.
"Tourists probably won't find information about the Liberty Bell at a site ending in.philly just like they don't, for example, find anything useful at sites ending in.info."
If you see a company snap up a new TLD at the recommendation of their marketing department, it's time to sell their stock. Unless somebody comes up with a novel technical use for an entire TLD, this is going to be a massive flop.
They're likely to find from this that they lose 100% of their PDF revenue (after all, they're not selling them anymore) yet will see zero increase in revenue for their printed editions to compensate.
I've bought some WotC PDFs in the past. It's usually because I don't have time to drive to some distant hobby/comic shop to pick out a module, so I bought one online. Now I'll just buy from some other publisher. PDF copies of modules and sourcebooks far pre-dates online purchasing. Scans of modules and handbooks and maps and magazines was going on back in the BBS days over 1200bps modems. Stopping PDF sales isn't going stop piracy. It's a mere speed-bump.
So they cut off their nose. That'll teach their face!
The [citation needed] was posted in response to a comment saying that Bush didn't fire all the lawyers up front.
Adding "Unprecedented" to the title is editorializing. Any publication claiming to be unbiased should title an article about the scandal in the most quantitative way possible. Impressively, Wikipedia managed to make the right decision here despite the majority of contributors to the article having a partisan bias.
No. Citation isn't needed. This is a discussion board, not a term paper or encyclopedia article. You don't need a citation for common knowledge, and asking for one just admits you're lazy.
Now you can go bicker in a wikipedia discussion about whether or not the article about this 'scandal' deserves to contain the word "unprecedented" in the title.
Exactly. Want your average engineering student to build something that can hit 60 mph on 1000 watts? No problem.
The question is.... How long does it take to get to 1000 watts.
I've seen some pretty impressive cars powered by 2HP steam engines. They could go really fast.... But it took them several minutes to accelerate to top speed.
It's hard to argue that "the lesser of two evils" is bad policy when you're holding the greater of the two evils up as an example.
This story shouldn't shock anybody at all. Obama was open about this before the election. Many people, including myself, pointed out many times before the election that on issues of privacy Obama was the most Bush-like of the candidates in the last election. But he charmed the pants off everybody and convinced you all that McCain was Bush-2.
So now you can be surprised. And you can be surprised again in 10 years when you look back at how we used to have the best healthcare in the world until Obama flushed it down the toilet for a more European style system.
Your DNS cache only contains entries for names you've resolved already. Odds are, search results are going to return a bunch of sites you've never been to.
Besides, Google's DNS entries have a 300 second TTL, so if your DNS server is working correctly, you shouldn't be able to resolve Google anymore after 5 minutes.
Being on slashdot I assumed you were savvy and knew something about DNS and it's alternatives.
2000s Now people have high speed networks across wide distances Security and stability issues begin to happen so it is better to have your data and a lot of the processing done in one spot. So we repeatedly propose thin-client/hosted app/SAAS/etc solutions to customers that don't want them, or don't want to pay recurring fees for them, while the trade rags continue to fall for the marketing hype every single time. Yet here we are at the end of the decade, having seen at least four big pushes back towards thin client applications, and the only ones that have really stuck are webmail for consumers, and CRM for the enterprise.
Fixed that for you.
Don't worry, though. The 2010s will be the year of the cloud.... You should hold your breath for it...
While I agree with the general tone of your comment, your comparison is not really valid. TV signals are broadcast, all users get the same thing.
Not anymore. Read up on Switched Digital Video. It's not fun when you try to watch something in the evening or on the weekend, and you get a "try again later" error 'cause too many people on your segment are watching unique content.
Thankfully, FiOS came to my area and I sent Comcast packing.
Supply of text-messaging bandwidth across several providers is several orders of magnitude higher than demand. If you compare usage of the service to capacity, it doesn't seem all that popular. Usage is a drop in the ocean.
The only possible explanation for the price of text messaging in the US is collusion. It would simply be too profitable to lure customers from a competing carrier by giving away what you essentially get for free to otherwise explain why none of the major providers have reasonable SMS rates. They understand that it would lead to a price war and eliminate SMS as a profit center, so they collude not to do it.
To be fair, the extreme deployment cost for cellular bandwidth is largely due to these same companies bidding up the license fees on the expectation that they'd be able to gouge their customers by charging thousands of times extra for the lowest bandwidth services.
My company is big on using co-ops, as we can rape them in terms of pay.
[...]
It's annoying, as I don't want to be teacher. I'm a project lead. Give me people who can handle the tasks I assign them without hand-holding and explanations of basic technology.
News flash: Co-ops are working for you to earn college credit. You get them cheap because you're signing up to teach them.
Ugh. I'm only 30, and I think I fall into your "older" category.
Tend to be more stubborn for no good reason.
No apparent reason, perhaps. A stubborn older engineer usually has a good reason, but is merely struggling to verbalize it. Don't confuse poor communications skills for lack of a good reason.
They tend to dislike solutions using newer technologies.
They've been around long enough to have been bitten by immature technology.
There's a reason you think older engineers have this in common. As engineers gain experience, they all learn similar lessons. If an older technology solves your problem perfectly well, and there's no apparent danger of it going away, you should pick it over some whizz-bang new buzzword compliant model. The new one may work fine, but it's far more likely to bite you in the ass in a way that nobody has had the time to notice yet. The wheel doesn't need to be reinvented.
Tend to be much more anal about following procedures even in times of crisis which may require a solution "NOW! Not next month!"
There are very few crisis that require a solution "NOW! Not next month!". As you gain more experience with crisis in your career, you'll be able to look back and see just how few of those fires actually needed to be put out "NOW!" at the expense of doing things the right way. As an added bonus, you'll get to look back and see how much better off you'd have been in the long run if you fixed some of those issues the right way instead.
This is a lesson that would be good for management types to learn. Unfortunately, constantly fighting fires seems to make people look good to upper management and warrant promotion. If only upper managers would stop occasionally to ask why everything was on fire all the time.... This is not just a problem for managers of engineers. Look at our financial system. We'll throw a quick patch on that too though.
Oh, come on... This is the least obnoxious Slashdot April Fool's so far. Do you want them to go back to the entire day being fake stories? Or OMGPonies!!!?
Slashdot Mirror
I don't have a single lamp in my house that is on for 3 hours a day. The one in my kitchen probably comes close during the week, but just barely. On average, across all the bulbs in my house, each one is used for just minutes a day.
Don't you people ever turn off the lights?
Hence the minor modification to the code, and the manually integrated CAPTCHA. If you use the 3rd-party plugin, you're making the script-kiddie's life too easy.
Almost nobody takes the time to make a spam-bot.
Some 90% brain-dead excuse for human life takes something off the shelf and points it at whatever software you're running. Unless you're one of the most visited sites on the net, a minor modification to the code, and a manually integrated captcha is going to stop practically everybody from spamming your site.
...is the point going right over the author's head.
A CAPTCHA works well enough for the same reason greylisting works well enough. They may be trivial to bypass (for some definition of 'trivial'), buy many applications only need a tiny speed-bump to make a huge difference in undesirable traffic.
Remember back when the auctions were secondary at ebay.com, and you had to click through their main site to get to them?
I don't even remember what the main site was... And the Wayback Machine doesn't go back that far.
a novel technical use for an entire TLD
There already is one
Wouldn't that make it "non-novel" by definition?
"Tourists probably won't find information about the Liberty Bell at a site ending in .philly just like they don't, for example, find anything useful at sites ending in .info."
If you see a company snap up a new TLD at the recommendation of their marketing department, it's time to sell their stock. Unless somebody comes up with a novel technical use for an entire TLD, this is going to be a massive flop.
Quite the contrary.
They're likely to find from this that they lose 100% of their PDF revenue (after all, they're not selling them anymore) yet will see zero increase in revenue for their printed editions to compensate.
I've bought some WotC PDFs in the past. It's usually because I don't have time to drive to some distant hobby/comic shop to pick out a module, so I bought one online. Now I'll just buy from some other publisher. PDF copies of modules and sourcebooks far pre-dates online purchasing. Scans of modules and handbooks and maps and magazines was going on back in the BBS days over 1200bps modems. Stopping PDF sales isn't going stop piracy. It's a mere speed-bump.
So they cut off their nose. That'll teach their face!
Two things:
The [citation needed] was posted in response to a comment saying that Bush didn't fire all the lawyers up front.
Adding "Unprecedented" to the title is editorializing. Any publication claiming to be unbiased should title an article about the scandal in the most quantitative way possible. Impressively, Wikipedia managed to make the right decision here despite the majority of contributors to the article having a partisan bias.
No. Citation isn't needed. This is a discussion board, not a term paper or encyclopedia article. You don't need a citation for common knowledge, and asking for one just admits you're lazy.
In case you still don't have time, here, let me google that for you.
Now you can go bicker in a wikipedia discussion about whether or not the article about this 'scandal' deserves to contain the word "unprecedented" in the title.
Duh. Think-o...
"How long does it take to get to 60mph"....
I previewed, and it looked right... Then as I browsed away from the comment the "oh-shit" kicked in...
Exactly. Want your average engineering student to build something that can hit 60 mph on 1000 watts? No problem.
The question is.... How long does it take to get to 1000 watts.
I've seen some pretty impressive cars powered by 2HP steam engines. They could go really fast.... But it took them several minutes to accelerate to top speed.
It's hard to argue that "the lesser of two evils" is bad policy when you're holding the greater of the two evils up as an example.
This story shouldn't shock anybody at all. Obama was open about this before the election. Many people, including myself, pointed out many times before the election that on issues of privacy Obama was the most Bush-like of the candidates in the last election. But he charmed the pants off everybody and convinced you all that McCain was Bush-2.
So now you can be surprised. And you can be surprised again in 10 years when you look back at how we used to have the best healthcare in the world until Obama flushed it down the toilet for a more European style system.
Your DNS cache only contains entries for names you've resolved already. Odds are, search results are going to return a bunch of sites you've never been to.
Besides, Google's DNS entries have a 300 second TTL, so if your DNS server is working correctly, you shouldn't be able to resolve Google anymore after 5 minutes.
I just got trolled, didn't I?
Debian/Hurd was around before Gentoo existed.
Like Gentoo *BSD, though, it was never an official release.
Replace 'OpenOffice' with 'Netscape', and your comment could have been written in 1997.
(Posted from Mozilla Firefox)
If I type in 74.125.67.100 in my browser, google still shows up.
Sure, but the search results would be useless.
2000s Now people have high speed networks across wide distances Security and stability issues begin to happen so it is better to have your data and a lot of the processing done in one spot. So we repeatedly propose thin-client/hosted app/SAAS/etc solutions to customers that don't want them, or don't want to pay recurring fees for them, while the trade rags continue to fall for the marketing hype every single time. Yet here we are at the end of the decade, having seen at least four big pushes back towards thin client applications, and the only ones that have really stuck are webmail for consumers, and CRM for the enterprise.
Fixed that for you.
Don't worry, though. The 2010s will be the year of the cloud.... You should hold your breath for it...
While I agree with the general tone of your comment, your comparison is not really valid. TV signals are broadcast, all users get the same thing.
Not anymore. Read up on Switched Digital Video. It's not fun when you try to watch something in the evening or on the weekend, and you get a "try again later" error 'cause too many people on your segment are watching unique content.
Thankfully, FiOS came to my area and I sent Comcast packing.
Define "popular".
Supply of text-messaging bandwidth across several providers is several orders of magnitude higher than demand. If you compare usage of the service to capacity, it doesn't seem all that popular. Usage is a drop in the ocean.
The only possible explanation for the price of text messaging in the US is collusion. It would simply be too profitable to lure customers from a competing carrier by giving away what you essentially get for free to otherwise explain why none of the major providers have reasonable SMS rates. They understand that it would lead to a price war and eliminate SMS as a profit center, so they collude not to do it.
To be fair, the extreme deployment cost for cellular bandwidth is largely due to these same companies bidding up the license fees on the expectation that they'd be able to gouge their customers by charging thousands of times extra for the lowest bandwidth services.
News flash: Co-ops are working for you to earn college credit. You get them cheap because you're signing up to teach them.
Ugh. I'm only 30, and I think I fall into your "older" category.
No apparent reason, perhaps. A stubborn older engineer usually has a good reason, but is merely struggling to verbalize it. Don't confuse poor communications skills for lack of a good reason.
They've been around long enough to have been bitten by immature technology.
There's a reason you think older engineers have this in common. As engineers gain experience, they all learn similar lessons. If an older technology solves your problem perfectly well, and there's no apparent danger of it going away, you should pick it over some whizz-bang new buzzword compliant model. The new one may work fine, but it's far more likely to bite you in the ass in a way that nobody has had the time to notice yet. The wheel doesn't need to be reinvented.
There are very few crisis that require a solution "NOW! Not next month!". As you gain more experience with crisis in your career, you'll be able to look back and see just how few of those fires actually needed to be put out "NOW!" at the expense of doing things the right way. As an added bonus, you'll get to look back and see how much better off you'd have been in the long run if you fixed some of those issues the right way instead.
This is a lesson that would be good for management types to learn. Unfortunately, constantly fighting fires seems to make people look good to upper management and warrant promotion. If only upper managers would stop occasionally to ask why everything was on fire all the time.... This is not just a problem for managers of engineers. Look at our financial system. We'll throw a quick patch on that too though.
Oh, come on... This is the least obnoxious Slashdot April Fool's so far. Do you want them to go back to the entire day being fake stories? Or OMGPonies!!!?
Speculation, sure, but in true "company bought by Sun" fashion they fucked that up too.
Our first renewal cycle after the transaction, Sun tried to triple the price of our JDBC connector redistribution licenses. Non-negotiable.
So we switched to a different solution.