Adolf Hitler may have been a mass murdering, country invading, ethnic cleansing dictator that we all despise, but he was still a human being that had done more in his life for his beliefs than we can only hope to achieve. I send condol.... Wait a second...
So you've made it quite obvious that you are able to recognise this situation as a hazard. Now all you need is the ability to drive at a speed appropriate to those conditions.
Right, because my post implied "speed up in these situations", you fucking twit.
The worst time to drive in my experence is after a small sprinkle, or when the rain starts. This is where road oil floats to the surface and makes the roads more slick. Slamming on the brakes would be "unsafe driving for conditions". Safe driving would be to extend your estimated stopping distance. This IS a reasonable explanation.
Small amounts of water on the road can also cause "dry hydroplaning" at fairly low speeds - small amounts of water fill the valleys in the texture of the road and because water doesn't compress very well, you get a situation where the tire glides over the valleys on a cushion of water. Not much friction in that situation....
No, not necessarily. Several municipalities that have installed red light cameras have also shortened the duration of the *yellow* lights at those intersections.
But the government is infallible and would never do anything dishonest...
So what exactly, pray fucking tell, is "not too close" when driving a compact behind a semi? Really, I'd like to know, because even 3 or so car lengths doesn't always let you see the lights when driving at normal speeds in the city.
Fire a.22 from a rifle at a shallow angle towards a 1/4" deep puddle on top of mud/dirt and you'll get the bullet whizzing about 9 times out of 10. Too steep and you'll just get a splash and the mud eats the bullet. Not really any way to be too shallow.
When the bullet hits the water at the right angle, you don't get much of a splash, but the impact destabilizes the round enough for it to start spinning rapidly.
Of course, there becomes a point where throttling and shaping just isn't an appropriate description of what is happening.
Take the case of Portland State University - all bitorrent traffic to the dorm subnet is "throttled" to 20k. Not each connection, the whole subnet. Although it isn't blocked in the strictest sense, it might as well be because a 20 meg file takes a week to download. That, of course, in addition to the occasional bouts of 800+ms ping times to their gateway.
2) 1.5 GB a week is a lot. The limit is actually now 2.0 GB a week, and there are plenty of ways to make things not count against you. Use the University-provided e-mail server means your e-mail is in-network and doesn't count. Using the University-provided HTTP proxy keeps your web browsing in-network, and it doesn't count.
1.5 GB a week is an shamefully low figure, especially for an educational institution. You could break that if you were using dialup. In fact, it's baffling that people can even defend a cap that is lower than _every_ single major ISP in the country except for ISPs running over cell networks. Guess VOIP, WorldWind, streaming webcasts or anything even remotely bandwidth intensive is out of the picture. I wonder what the upstream cap is...
3) Do you even know why that bandwidth cap was instated? Back in the days of the original Napster (not the subscription Napster (which is free at Penn State), there was a group of 8 students that were using up the bandwidth for the entire University. Not just the residence halls, but the entire campus. The swipe card readers on the dorms wouldn't work, because the network was saturated with illegal downloading. By limiting each jack to 2 GB a week, you can actually use the network in labs and classrooms when you need it, too.
If your card readers break because someone is downloading (or doing anything) in the dorms, you ought to be working for Geek Squad. Incompetence and disgustingly inept network design are responsible for outages in that scenario, not a few morons downloading something in their rooms. Unfortunately, it seems that most people who work as "IT" in colleges and universities are mainly concerned with not rocking the boat so they can stay there the required 25 years to get a pension. With "support" like that, it's no surprise that American students are getting beaten in programming and other competitions by students from poor former Eastern Bloc countries like Poland, Ukraine and the remote parts of Russia.
They say that spelling is the first thing to go when you're drunk. And after working in a place like that for a few years, the guy has the right to get a little shitfaced every now and then;)
Software really isn't all that great either, for what it costs. Not that it isn't possible to learn how to get around in it, but lets just say not many backup apps have won usability awards...
Hardware is also generally pretty crummy. Know of several folks in the area who have gone through the ordeal of us installing an IBM tape drive, finding out it's DOA, coming back, pulling the sucker and replacing it with another goddamn DOA drive before finally realizing the second replacement actually works. These drives retail for over a grand a piece, the tapes aren't exactly cheap either. Even buying supposed "quality drives" doesn't mean everything will go smoothly...
Needless to say, I hear "I hate fucking tape" a lot.
Don't forget the color of the plastic in the connectors is usually black, making it damn near impossible to see which way is the right way if you're in the dark.
Re:Any advantages over having only one connector?
on
eSATA Connectors
·
· Score: 1
So "does" a phone cable. Worked for an DSL ISP for a while and I got a few of those calls (what do you mean I have to plug the DSL modem in?)
Re:Are they better, or just different?
on
eSATA Connectors
·
· Score: 1
Yeah, so when the flimsy 0.5mm plastic breaks, you have to replace a motherboard instead of a $1 cable. Brilliant.
Except that the caps for business accounts through cable and dsl providers are often the same as for residential customers. So, uhh, yeah, fuck off and die.
Your average blank disk out there is pretty poor quality, if anything, this lets you burn on crap disks with at least the chance of reading the data a year or more down the road. Par does take a while to generate the recovery files though...
Well.. except for those few YEARS that blizzard didn't do jack shit to fix the flaw with windows 2000 networking, causing people to drop all the fucking time.
Their hosting... Dear God. How incompetent. They claim daily backups, but every time they fuck something up and have to restore it on my end, they restore a backup from March of this year. I have recordings of their techs stating that they don't actually do daily backups and if I had a bit more time I'd put up all that stuff on a website, but I don't feel like wasting more time at this point on them.
They don't "backup" emails either (at all) - something which isn't clear at all on their website. They gave me a few months free as a "sorry, we fucked up" but I had to call in and spent like 45 minutes trying to get them to give the 3 promised months to me.
They also pulled my entire site one day and said it was "due to copyright infringement". When I tried to find out more info, I couldn't get an explanation out of them and almost a year later, I still don't know fucking why. Or what. I'm guessing they just deleted the server by accident or something and needed an excuse. Just a lot of *sigh* dealing with this company.
And before the apologists chime in, yeah, ok, I have a local backup so why should this be an issue? Because I don't look forward to upload 5 fucking gigs over my capped connection. Thanks for your future smart ass comments though.
This information, freely available on CNN gave the enemy real time reports on the US troop movement and lost many US lives because of US reporters not thinking about their actions.
So exactly how many of the 147 US deaths in GW1 can be attributed to this? Well, 147-35-11=101, if you pull out the friendly fire deaths. And can you find a source? Because I'm having a bit of a hard time finding one.
Just asking, since you're obviously a fucking authority on such things...
Slashdot Mirror
nah, you can get a decent barrel and sit on a corner of the field, pecking at people across the field. Won't have to move an inch!
Adolf Hitler may have been a mass murdering, country invading, ethnic cleansing dictator that we all despise, but he was still a human being that had done more in his life for his beliefs than we can only hope to achieve. I send condol....
Wait a second...
Funny thing is he also looks a tad bit evil in his pic.
So you've made it quite obvious that you are able to recognise this situation as a hazard. Now all you need is the ability to drive at a speed appropriate to those conditions.
Right, because my post implied "speed up in these situations", you fucking twit.
The worst time to drive in my experence is after a small sprinkle, or when the rain starts. This is where road oil floats to the surface and makes the roads more slick. Slamming on the brakes would be "unsafe driving for conditions". Safe driving would be to extend your estimated stopping distance. This IS a reasonable explanation.
Small amounts of water on the road can also cause "dry hydroplaning" at fairly low speeds - small amounts of water fill the valleys in the texture of the road and because water doesn't compress very well, you get a situation where the tire glides over the valleys on a cushion of water.
Not much friction in that situation....
No, not necessarily. Several municipalities that have installed red light cameras have also shortened the duration of the *yellow* lights at those intersections.
But the government is infallible and would never do anything dishonest...
So what exactly, pray fucking tell, is "not too close" when driving a compact behind a semi?
Really, I'd like to know, because even 3 or so car lengths doesn't always let you see the lights when driving at normal speeds in the city.
Fire a .22 from a rifle at a shallow angle towards a 1/4" deep puddle on top of mud/dirt and you'll get the bullet whizzing about 9 times out of 10. Too steep and you'll just get a splash and the mud eats the bullet. Not really any way to be too shallow.
When the bullet hits the water at the right angle, you don't get much of a splash, but the impact destabilizes the round enough for it to start spinning rapidly.
Fortunatley, if you call and complain about the voip issues, they have a $10 a month package that "prioritizes" your traffic.
Thanks Shaw!
Of course, there becomes a point where throttling and shaping just isn't an appropriate description of what is happening.
Take the case of Portland State University - all bitorrent traffic to the dorm subnet is "throttled" to 20k. Not each connection, the whole subnet. Although it isn't blocked in the strictest sense, it might as well be because a 20 meg file takes a week to download.
That, of course, in addition to the occasional bouts of 800+ms ping times to their gateway.
2) 1.5 GB a week is a lot. The limit is actually now 2.0 GB a week, and there are plenty of ways to make things not count against you. Use the University-provided e-mail server means your e-mail is in-network and doesn't count. Using the University-provided HTTP proxy keeps your web browsing in-network, and it doesn't count.
1.5 GB a week is an shamefully low figure, especially for an educational institution. You could break that if you were using dialup. In fact, it's baffling that people can even defend a cap that is lower than _every_ single major ISP in the country except for ISPs running over cell networks.
Guess VOIP, WorldWind, streaming webcasts or anything even remotely bandwidth intensive is out of the picture. I wonder what the upstream cap is...
3) Do you even know why that bandwidth cap was instated? Back in the days of the original Napster (not the subscription Napster (which is free at Penn State), there was a group of 8 students that were using up the bandwidth for the entire University. Not just the residence halls, but the entire campus. The swipe card readers on the dorms wouldn't work, because the network was saturated with illegal downloading. By limiting each jack to 2 GB a week, you can actually use the network in labs and classrooms when you need it, too.
If your card readers break because someone is downloading (or doing anything) in the dorms, you ought to be working for Geek Squad. Incompetence and disgustingly inept network design are responsible for outages in that scenario, not a few morons downloading something in their rooms.
Unfortunately, it seems that most people who work as "IT" in colleges and universities are mainly concerned with not rocking the boat so they can stay there the required 25 years to get a pension. With "support" like that, it's no surprise that American students are getting beaten in programming and other competitions by students from poor former Eastern Bloc countries like Poland, Ukraine and the remote parts of Russia.
They say that spelling is the first thing to go when you're drunk. ;)
And after working in a place like that for a few years, the guy has the right to get a little shitfaced every now and then
Software really isn't all that great either, for what it costs. Not that it isn't possible to learn how to get around in it, but lets just say not many backup apps have won usability awards...
Hardware is also generally pretty crummy. Know of several folks in the area who have gone through the ordeal of us installing an IBM tape drive, finding out it's DOA, coming back, pulling the sucker and replacing it with another goddamn DOA drive before finally realizing the second replacement actually works. These drives retail for over a grand a piece, the tapes aren't exactly cheap either. Even buying supposed "quality drives" doesn't mean everything will go smoothly...
Needless to say, I hear "I hate fucking tape" a lot.
Don't forget the color of the plastic in the connectors is usually black, making it damn near impossible to see which way is the right way if you're in the dark.
So "does" a phone cable.
Worked for an DSL ISP for a while and I got a few of those calls (what do you mean I have to plug the DSL modem in?)
Yeah, so when the flimsy 0.5mm plastic breaks, you have to replace a motherboard instead of a $1 cable.
Brilliant.
Except that the caps for business accounts through cable and dsl providers are often the same as for residential customers.
So, uhh, yeah, fuck off and die.
1) good luck getting a sophisticated transceiver on board a plane disguised as anything
A radio works well enough as a disguise. Not like the mouthbreathing monkeys at the TSA can tell. Ooh green circuitboards!
and rest assured your not smart enough to be one of them.
Sais theh moran whoo kant spel.
Your average blank disk out there is pretty poor quality, if anything, this lets you burn on crap disks with at least the chance of reading the data a year or more down the road.
Par does take a while to generate the recovery files though...
great support (BNET, patches)
Well.. except for those few YEARS that blizzard didn't do jack shit to fix the flaw with windows 2000 networking, causing people to drop all the fucking time.
Their hosting... Dear God. How incompetent.
They claim daily backups, but every time they fuck something up and have to restore it on my end, they restore a backup from March of this year. I have recordings of their techs stating that they don't actually do daily backups and if I had a bit more time I'd put up all that stuff on a website, but I don't feel like wasting more time at this point on them.
They don't "backup" emails either (at all) - something which isn't clear at all on their website.
They gave me a few months free as a "sorry, we fucked up" but I had to call in and spent like 45 minutes trying to get them to give the 3 promised months to me.
They also pulled my entire site one day and said it was "due to copyright infringement". When I tried to find out more info, I couldn't get an explanation out of them and almost a year later, I still don't know fucking why.
Or what.
I'm guessing they just deleted the server by accident or something and needed an excuse.
Just a lot of *sigh* dealing with this company.
And before the apologists chime in, yeah, ok, I have a local backup so why should this be an issue? Because I don't look forward to upload 5 fucking gigs over my capped connection. Thanks for your future smart ass comments though.
Maybe you should get it repaired, you fucking twit.
I don't know about the lathes you've worked on, but in my experience, they are kind of loud....
This information, freely available on CNN gave the enemy real time reports on the US troop movement and lost many US lives because of US reporters not thinking about their actions.
So exactly how many of the 147 US deaths in GW1 can be attributed to this?
Well, 147-35-11=101, if you pull out the friendly fire deaths.
And can you find a source? Because I'm having a bit of a hard time finding one.
Just asking, since you're obviously a fucking authority on such things...