Well, 1) the people around you are already getting half of the conversation and 2) I bet it would be hard to 'wander off' to a secluded area near a one of these hotspots so someone couldn't eavesdrop, so only really stupid people would have problems.
Mitnick, Kevin
a lecturer who is paid handsomely by corporate executives to explain to their employees what the management apparently doesn't understand either, that people are gullible.
People often accept this sort of "reasoning" because particularly vivid or dramatic cases tend to make a very strong impression on the human mind. For example, if a person survives a particularly awful plane crash, he might be inclined to believe that air travel is more dangerous than other forms of travel. After all, explosions and people dying around him will have a more significant impact on his mind than will the rather dull statistics that a person is more likely to be struck by lightning than killed in a plane crash.
def thatsFunny():
"I bet you can see the whitespace to my left just fine, because you can see when it stops."
if poor_argument:
"I also bet you can tell that this is intented farther!"
def evenMoreFunny():
"I also bet you can tell when the previous block ended!"
let me just say that, as a slashdot troll, i have a firewall which allows me to dynamically modify my o/s fingerprint, a highly adaptive cookie manager/poisoner that can decode many cookies in realtime (stop using urlencode!), a browser plugin that lets me modify my entire http header including user agent, a database-driven transparent proxy tracker which harvests new proxies 24/7, scripts to generate free email accounts by the 100's, good web scripting skills, and on a good day around 500 moderation points on slashdot from over 1,000 monitored accounts.
please allow me to introduce myself.
i wandered onto this article through a link on k5. abusive users are generally much more capable people than you seem to give them credit for.
let me give you 3 things that are actually hard to defeat:
credit cards.
captcha. (i hate good captcha).
SSL. trivial? no. you can't access an SSL site through almost all transparent proxies. it makes it very hard to switch ip addresses.
So all you really have to do is choose one of the three. (And unless you are going to include an audio version for the visually impaired, don't go with captcha.)
They don't try. They're not there for an education. They're there for a degree. A piece of paper that says give me more money. That's why I have disdain.
Oh, and having '.' in your path is a security risk. Sure, it's less of a security risk at the end of the path. But it's still a security risk!
Hehe. The person who tried to evangelize Visual Basic to me was Junior when I was a lowly Freshman.
But the Prof?!? C'mon, who leaves '.' in their path? (Don't get me started on the admin, who actually allows it.)
As for the rest of the quips, they all happened with people that were in the same course as I was at the time.
The huge recursive routine? It took those two students at least 20 hours between them to get it working accurately. Not once did it occur to them to scrap the damned thing and start over.
Build and test your CSS in the most advanced browser available before testing in others, not after.
If you build a site testing in a broken browser, your code begins relying on the broken rendering of that browser. When it comes time to test in a more standards-compliant browser, you will be frustrated when that browser renders it improperly. Instead, start from perfection and then hack for the less able browsers. Your code will be more standards-compliant from the start, and you won't have to hack as much to support other browsers. Today, this means Mozilla, Safari, or Opera.
It seems that not only have we slammed the site into the ground, but their servers aren't very well secured. Score one for the slashdot script kiddies out there.
Yeah, but at least in Windows I don't have to work with text. I can't even sit with a book for more than thirty seconds, you expect me to type and thenread?? Sheesh, next you'll want me to understand how to update Windows. Puh-leez.
Slashdot Mirror
Well, 1) the people around you are already getting half of the conversation and 2) I bet it would be hard to 'wander off' to a secluded area near a one of these hotspots so someone couldn't eavesdrop, so only really stupid people would have problems.
Of course, there are a lot of stupid people...
Atonement? Are you kidding? I'll let the Devil's Dictionary X say it:
Mitnick, Kevin a lecturer who is paid handsomely by corporate executives to explain to their employees what the management apparently doesn't understand either, that people are gullible.
Grrr.
Without the Amazon-referer whoring:
I'm currently running
Reminds me of a post I made a while ago.
They are that bad.
So all you really have to do is choose one of the three. (And unless you are going to include an audio version for the visually impaired, don't go with captcha.)
Even includes nmap training, where by 'training' I mean 'obviously reading a script off an iBook and then masturbating for no reason'.
Try not to kill Fyodor's server.
Exactly. But this is show is so recockulously bad that it's funny.
One of the tools they plug, though--Knoppix STD--is pretty damn cool.
I'm betting that there are a large number of sysadmins who pay more attention to /. than they do to keeping systems up to date.
Actually, it's another slashdot user .
use strict; exists for a reason.
security is always inversely proportional to convenience.
I know a large number of people (OS X users) who would disagree with you.
The GPL isn't about the freedom of the people who use it, it's about the freedom of the *software*.
Of course, 'free' isn't probably the best word here; the Creative Commons licenses hit the nail on the head with "share alike".
They don't try. They're not there for an education. They're there for a degree. A piece of paper that says give me more money. That's why I have disdain.
Oh, and having '.' in your path is a security risk. Sure, it's less of a security risk at the end of the path. But it's still a security risk!
Hehe. The person who tried to evangelize Visual Basic to me was Junior when I was a lowly Freshman.
But the Prof?!? C'mon, who leaves '.' in their path? (Don't get me started on the admin, who actually allows it.)
As for the rest of the quips, they all happened with people that were in the same course as I was at the time.
The huge recursive routine? It took those two students at least 20 hours between them to get it working accurately. Not once did it occur to them to scrap the damned thing and start over.
Right now I am in a Computer Science program. I have had the pleasure to see:
I don't think the whole proper education thing is going to happen any time soon.
Build and test your CSS in the most advanced browser available before testing in others, not after. If you build a site testing in a broken browser, your code begins relying on the broken rendering of that browser. When it comes time to test in a more standards-compliant browser, you will be frustrated when that browser renders it improperly. Instead, start from perfection and then hack for the less able browsers. Your code will be more standards-compliant from the start, and you won't have to hack as much to support other browsers. Today, this means Mozilla, Safari, or Opera.
(From the CSS Crib Sheet)
You see, if you design for IE flaws and the market shifts, you'll have designed yourself into a corner.
You're also hindering the adoption of alternative browsers because "it only works in IE."
Also, IE-only sites tend to be inaccessible, and inaccessible sites may have nasty consequences, like ADA lawsuits.
It takes only marginally more effort to create a cross platform site.
Designing with Web Standards is an excellent book on cross platform design.
And for those not convinced of CSS's inherent flexibility, there's the CSS Zen Garden. Cross platform, any browser. (Yes, even Lynx.)
It seems that not only have we slammed the site into the ground, but their servers aren't very well secured. Score one for the slashdot script kiddies out there.
"Click on any of the pictures to get an enlargment."
Yeah, but at least in Windows I don't have to work with text. I can't even sit with a book for more than thirty seconds, you expect me to type and then read?? Sheesh, next you'll want me to understand how to update Windows. Puh-leez.
I just refreshed kernel.org and there's a new 2.4.x line.
Not quite on topic, especially because it's a different blinkenlights, but this article reminded me of it:
$ telnet towel.blinkenlights.nl 24
Terminal window should be 200x59, with black text on white background for best results.
Some people have way to much time.