...but of course everyone had to immediately jump about three hundred feet vertically to a conclusion. ZOMG TEH SENSORSHOOPZ! BOIKOTTZ NAO!
Never attribute to malice that which can be adequately explained by stupidity. Or in this case, a weekend NOC guy shutting off a network flood. Basically, you're making the assumption that they blocked the site knowing it was 4chan, rather than knowing it as yet another faceless IP address that was the source of a flood. Even if they had done a reverse name lookup, you can't even assume that they would know what 4chan was. It hasn't exactly made the national news. (local news every now and then when a local TV station wants ratings, but not national) Maybe the NOC flunkie knew what it was, but his boss or his boss's boss didn't, and said to cut it off.
Part of the problem is the "Tell us what you did and why RIGHT NOW OR ELSE!" attitude of so many internet users. Sorry, folks, big companies just aren't set up to give you instant answers about what some sub-department did two hours ago, much less on a weekend. That's not "evil", that's just BIG.
As someone on a Digg thread said, the regular 'channers knew the site had been under attack for a couple of weeks. The once-in-a-whilers didn't know anything until they heard it was blocked.
Well, duh. I switched over to routing my outbound mail through them years ago because I thought they might, then I never checked until recently when I was setting up SMTP auth so that my mom could have some sort of outgoing mail from her new laptop.
And not all their fixed IP customers are business customers, though they offer essentially the same product at the same price as their top-tier home service. Someday I'll check and see if they've ever started offering fixed IP with more than 6 mbits download through a U-verse connection, since I'm 500 feet from the pedestal. I just don't want the stupid pay TV; my antenna brings in nice DTV, including an out-of-market PBS station.
Unless of course it's the scilons behind the DDoS. I'd laugh more parts of my body than just my ass off if a couple of scilon morons got locked up for something stupid like this. But I'm not going to sit around waiting for that to happen.
So the problem isn't AT&T, and the problem isn't really even the users (or more likely zombie bots) who are DDoSing AT&T, the real problem is the networks that are allowing the spoofed packets out. Because if you receive an IP packet from an end user with a source address that's not from your network, you should assume that it came from a new legitimate routing path and forward it right up. Because it's normal for your end users to set up crazy routing without even having an AS.
A big problem on the internets is ISPs that are run by idiots or assholes who don't understand (or care about) basic TCP/IP etiquette. It's not just spoofed packets, it's also spoofed BGP announcements. And freely allowing outbound port 25 access.
(I noticed recently when I was setting up and testing SMTP auth on my own mail server that AT&T apparently now blocks outbound port 25 for dynamic IP users, hooray for them. It still works from my AT&T static IP, though.)
It's kinda funny, but it also shows the ignorance of some people who used to (and maybe still do) think there is only one web browser out there and it's IE.
Or exactly two, and the second is Firefox.
Or exactly three, and the first two are IE6 and IE7.
If you're lucky, they'll have even heard of Safari.
(This message posted with none of the above mentioned browsers, nor Opera.)
Launch windows dictate what time of the day you have to launch. The ISS has a rather eccentric orbit to make things easier for Russia, and it precesses relative to the ground, so you have to wait for it to cross the right longitude. And of course after Challenger, they really don't like to launch at night if they don't have to.
Except that they launch from a latitude not far south of Houston. If LBJ could've moved it to Corpus Christi, I'm sure he would have.
Still, the Cape is a nicely convenient bump, and all that water around the area probably had a lot to recommend it in terms of keeping the Ruskies out back in the '60s.
FFXI has both, but job (class) level tends to be more important than the individual skill levels. Job level also limits the individual skill level caps, as you can gain skills from other jobs, and there are also situations that cap your job level, again capping your skill levels.
And then of course there is player skill. In any game you're going to be better simply from learning the maps, but there are also skills such as learning crowd control (sleeping or kiting monsters when there are more than can be handled), and learning hate management (which can be really important with FFXI's somewhat complicated enmity system).
For instance, a while ago I was just wandering around looking for something specific to farm, when I noticed a monster suddenly throw a spell on someone. I instantly knew that the monster had noticed him walking by, and that he probably was about to get beaten to a pulp. So I attacked the monster, which made it want to attack me and not him, and since it was a much lower level than me I had no trouble fighting it.
So when the file can fit in 8.3, it is saved as such, and when it can't, the long file name is saved in the directory, but a corresponding short name is created with a bunch of bogus random garbage. TFA doesn't explain what happens with mixed-case 8.3 filenames (VFAT long names would be case-preserving, but it may not be a great idea to use mixed-case in 8.3 directory entries), and that would be interesting to know.
The only real problem I can see if you name stuff with long names (or maybe use mixed-case short names) and then try to use them with equipment old enough to only support 8.3 names, or equipment that only supports 8.3 names to avoid the VFAT patent.
Slashdot Mirror
See above where it is pointed out that he has already been missing for at least seven months.
No, "they" are.
...but of course everyone had to immediately jump about three hundred feet vertically to a conclusion. ZOMG TEH SENSORSHOOPZ! BOIKOTTZ NAO!
Never attribute to malice that which can be adequately explained by stupidity. Or in this case, a weekend NOC guy shutting off a network flood. Basically, you're making the assumption that they blocked the site knowing it was 4chan, rather than knowing it as yet another faceless IP address that was the source of a flood. Even if they had done a reverse name lookup, you can't even assume that they would know what 4chan was. It hasn't exactly made the national news. (local news every now and then when a local TV station wants ratings, but not national) Maybe the NOC flunkie knew what it was, but his boss or his boss's boss didn't, and said to cut it off.
Part of the problem is the "Tell us what you did and why RIGHT NOW OR ELSE!" attitude of so many internet users. Sorry, folks, big companies just aren't set up to give you instant answers about what some sub-department did two hours ago, much less on a weekend. That's not "evil", that's just BIG.
As someone on a Digg thread said, the regular 'channers knew the site had been under attack for a couple of weeks. The once-in-a-whilers didn't know anything until they heard it was blocked.
Well, duh. I switched over to routing my outbound mail through them years ago because I thought they might, then I never checked until recently when I was setting up SMTP auth so that my mom could have some sort of outgoing mail from her new laptop.
And not all their fixed IP customers are business customers, though they offer essentially the same product at the same price as their top-tier home service. Someday I'll check and see if they've ever started offering fixed IP with more than 6 mbits download through a U-verse connection, since I'm 500 feet from the pedestal. I just don't want the stupid pay TV; my antenna brings in nice DTV, including an out-of-market PBS station.
Questions? Not properly categorized?
I'm sure they're missing a few categories in that list.
But is it "censoring" if they are blocking it for solely technical reasons? Like a jillion ACK packets coming in from spoofed SYN-floods?
Damn. I was sure they came from eBaumsWorld.
Unless of course it's the scilons behind the DDoS. I'd laugh more parts of my body than just my ass off if a couple of scilon morons got locked up for something stupid like this. But I'm not going to sit around waiting for that to happen.
So the problem isn't AT&T, and the problem isn't really even the users (or more likely zombie bots) who are DDoSing AT&T, the real problem is the networks that are allowing the spoofed packets out. Because if you receive an IP packet from an end user with a source address that's not from your network, you should assume that it came from a new legitimate routing path and forward it right up. Because it's normal for your end users to set up crazy routing without even having an AS.
A big problem on the internets is ISPs that are run by idiots or assholes who don't understand (or care about) basic TCP/IP etiquette. It's not just spoofed packets, it's also spoofed BGP announcements. And freely allowing outbound port 25 access.
(I noticed recently when I was setting up and testing SMTP auth on my own mail server that AT&T apparently now blocks outbound port 25 for dynamic IP users, hooray for them. It still works from my AT&T static IP, though.)
Indeed. I only watch Legend of the Seeker because it is so bad that it's awesome. It is every swords & sorcery cliche there ever was, and then some.
No one but Sam Raimi could ever do justice to this movie.
Also, random Ted Raimi cameo FTW. He should be Leeroy Jenkins!
It makes even more sense if you know about Tetraphobia.
It's kinda funny, but it also shows the ignorance of some people who used to (and maybe still do) think there is only one web browser out there and it's IE.
Or exactly two, and the second is Firefox.
Or exactly three, and the first two are IE6 and IE7.
If you're lucky, they'll have even heard of Safari.
(This message posted with none of the above mentioned browsers, nor Opera.)
I for one, am downloading the complete works of James Brown as we speak.
Do you feel good?
...the cake is a li--ne drawing?
Actually, the cake is an 'i'.
Just be careful - remember what happened to Bambi.
What, this?
By the way, Falco died 11 years ago, and apparently no one noticed.
Yeah, that's a good idea. Aren't you glad you're the first to think of it?
Launch windows dictate what time of the day you have to launch. The ISS has a rather eccentric orbit to make things easier for Russia, and it precesses relative to the ground, so you have to wait for it to cross the right longitude. And of course after Challenger, they really don't like to launch at night if they don't have to.
Except that they launch from a latitude not far south of Houston. If LBJ could've moved it to Corpus Christi, I'm sure he would have.
Still, the Cape is a nicely convenient bump, and all that water around the area probably had a lot to recommend it in terms of keeping the Ruskies out back in the '60s.
Oh noes! Candlejack got to his unpat
memory of the independence day UUUUUUUUUUUUUUUUUUUUUUUUUUU can haz cheezburger
FFXI has both, but job (class) level tends to be more important than the individual skill levels. Job level also limits the individual skill level caps, as you can gain skills from other jobs, and there are also situations that cap your job level, again capping your skill levels.
And then of course there is player skill. In any game you're going to be better simply from learning the maps, but there are also skills such as learning crowd control (sleeping or kiting monsters when there are more than can be handled), and learning hate management (which can be really important with FFXI's somewhat complicated enmity system).
For instance, a while ago I was just wandering around looking for something specific to farm, when I noticed a monster suddenly throw a spell on someone. I instantly knew that the monster had noticed him walking by, and that he probably was about to get beaten to a pulp. So I attacked the monster, which made it want to attack me and not him, and since it was a much lower level than me I had no trouble fighting it.
Someone should make those. It would be so awesome.
M$?
So when the file can fit in 8.3, it is saved as such, and when it can't, the long file name is saved in the directory, but a corresponding short name is created with a bunch of bogus random garbage. TFA doesn't explain what happens with mixed-case 8.3 filenames (VFAT long names would be case-preserving, but it may not be a great idea to use mixed-case in 8.3 directory entries), and that would be interesting to know.
The only real problem I can see if you name stuff with long names (or maybe use mixed-case short names) and then try to use them with equipment old enough to only support 8.3 names, or equipment that only supports 8.3 names to avoid the VFAT patent.