I'd add to that, "Not file a frivolous lawsuit over an unprovable breach of contract."
I started writing up a contract, and about halfway through I realized that it just wasn't worth the money. I'd seen them trump up ridiculous crap before when they knew it wouldn't fly in court, just from spite, and I'd seen them get all spite-y over acts of god.
Some people you just have to write off as too shady to work with.
I ended up turning him down, actually, though the reason he was willing to deal with me afterward was because I'd taken pains, even while they were screwing me over, to be professional.
In the end though, I decided that there was no amount that they could offer that would be worth the pain of dealing with them again. I put them off a few times, but finally I just came flat out and said that I didn't feel like I could trust them enough to do work for them.
Dude, they perp-walked him; he didn't do it on purpose. He started a process, and then they killed his userid, so the process went zombie and just sat around doing its thing without any control, and no one who knew to stop it.
I had a similar story; I got canned, and the second I left the building they started reformatting my equipment to make sure I hadn't left any time bombs. Due to server problem, I'd been using my desktop for development, and I had a huge code package sitting there waiting to be deployed (They fired me because I'd completed it).
So they ended up wiping out the code. Woops. The icing on the cake was that they changed all my passwords, and revoked all my access, but they didn't check for running sessions, so I got home and I was still remotely rooted in a pair of live servers. I changed the MOTD on all the machines I was still logged into to: "When terminating an employee, make sure to abort active sessions before you change the passwords." Then logged off.
I'm sure that sent them into a frenzy of paranoia, but frankly, they were acting like idiots. They went out of business in 3 or 4 months, and the guy who fired me spent a year or so after that trying to get me to do contract work for him.
If you were using perl, you could use the PDF::Reuse library or PDF::API2 to do all kinds of crap. If it's not a valid pdf, the libraries throw all kinds of errors when you attempt to open the file. With that, you can even look at things like the number of pages, the content on the pages, etc.
Mind you, if the rendering is fubared, like a font problem or something, so the page looks like crap, it may still be a valid pdf and pass through any sort of check with no problem. A corrupted image will still show up as an image, screwed up text will still be text, probably even the same text though mashed up and illegible outside the code.
I guess you could use imagemagick or something to render it into a tiff and then compare it...But basically it's a nightmare to try and find out if the page "looks right" without having a human-validated copy lying around, and if you're doing that, then this isn't all that useful.
That's why it's handy; spyware seldom uses a standard port, so if you're whitelisting outbound traffic, you keep a lot of nasties from doing their thing. They may get themselves installed, but then they can't do much.
On the other hand, a lot of spyware/malware can be installed by exploiting a vulnerablity on a listening port. This is the most common problem with the Windows machines, because a lot of unneeded apps are installed by default, and they bind to a port and wait for things to start talking to them.
By blocking inbound connections, you save yourself a lot of grief as well, and it is a feature of TCP/IP that you can determine whether an inbound connection is a new connection or an established connection, which means you can filter port 80(HTTP), for example, to allow only "established" inbound connections, and prevent any one out there from exploiting the IIS service that is likely running on your machine.
See, it just doesn't work that way. You're either a part of society, or you're not. People want to get the benefits without having to follow the rules. Part of what society is for is enforcing those rules, so yea, if you flaunt the rules of society, you get the boot.
If you can't find a single society whose rules you can live within, by all means, go live in the ocean and spare the rest of us from having to deal with you.
Most people who block things block ports, not web addresses. So you block all ports except the ones you use, inbound AND outbound, and then you log all outbound traffic that gets blocked.
Most of the time, that will let you know if you've got a virus or a rootkit, though if you have too many ports open, it may not.
On my personal setup I don't web browse or check email on my Windows box, but I do occasionally need to download things so I keep the antivirus around for that. Never had it actually find anything, however.
It is possible to be virus free if you're careful, but I prefer to be certain as much as it is possible to be certain.
I bet you don't use a multi-thousand dollar cisco security appliance either.
My home firewall router does everything a semi-equivalent cisco router would do; VPN, multi-ISP support, DMZ, firewall, etc, etc. The difference is mine is OSS based, running on an old desktop, and cost me, conservatively, 50 bucks, where their equivalent product runs $1000+ and doesn't have gigabit or fibre support.
For what they offer, their appliances are wildly overpriced.
How can you possibly compromise with someone who feels that the only way they can deal with you is to abandon the entire country? It's clearly their way, or they're going to go live on a tiny artificial island.
I'm sorry, I'm just not seeing how my ability to live in the same country with you bastards makes me intolerant. And frankly, I don't feel any special need to be tolerant toward groups whose agenda is so foreign to human experience that their only option is to create their own country.
I have plenty of tolerance for other people's views. I am usually willing to compromise. My views as a whole are pretty moderate, and in the places where they're radical, I am at least open to the possibility that it's me, and not the whole world, that is crazy.
I am certainly not the one who is so hysterically fringe that I'm considering moving myself to an extraterritorial oil rig so I don't have to deal with my fellow citizens. If there is a part of you that feels like that's a good idea, you've got problems.
It's not that bad until you get to shallow water, and even there your biggest problem would be being dashed against the bottom, or taking damage from flotsam and jetsam being pulled around by the tides. Considering that that may be something like cargo containers pulled off a container ship, or a large unmoored barge, the danger is significant.
Hurricanes are a big deal in the air, but their ability to affect water is comparatively minor, usually limited to "pushing" water in front of the hurricane (the so called "storm surge"). The wave action is significant, and in shallower areas it will temporarily rearrange currents dramatically, creating local riptides and such.
You'd probably want to be all the way under though, if that were possible. Wave action could expose a structure that was only a few feet under, and the wind has a much better chance of screwing you up than the water does.
Living in a society is about compromise and respect for other peoples opinions and beliefs. Groups inside a society who have no tolerance for other views are a serious issue. Most of the problems societies have are when these groups get too powerful.
Frankly sending them all out into the middle of the ocean sounds like a great idea. Living accommodations optional.
Well it's also finally come around that there are companies who have done it before...Both Mythic(DAoC) and Funcom(AO) have prior experience with long-running MMOs.
I was in the midst of a big coding crunch last year, and one of the random people who I used to indulge back in the glory days when I wasn't in charge of everything came in and started babbling something I couldn't hear because of the headphones.
I pulled them off, and gave him a look, and he said, "Uh, is this a bad time?"
I reached up and unplugged my headphones from the speakers, and from the speakers boomed "LET THE BODIES HIT THE FLOOR! LET THE BODIES HIT THE FLOOR!" Over the course of the day, the music creeps up, and up, and by this time it was deafening.
I turned the volume down, gave the guy another look, and he said, "Uhhh, I'll come back later."
I gave myself permanent hearing damage cranking up my music loud enough that I could no longer hear the screaming and crying going on in the room behind me.
At no point do they explicitly state that they're limiting their sample to big, fancy companies. They're saying their "10 worst jobs" are "Tech's 10 worst entry-level jobs."
Now either I don't work in tech, or they're full of shit. And since their "tech" jobs include administrative assistants, and salespeople, I'm calling the whole article a thinly veiled blowjob for VWs advertisers.
The real horseshit is that a year or two working for one of those companies will open so many doors...You deserve to be put through the wringer if you get to fricking start with an industry leader.
Where are all the dead end jobs that pay less, and demand more work? People don't really consider this stuff hard do they?
Buncha pussies. This is the worst they've got? I had a tech job once cleaning up database applications for a "Department of Family and Childrens Services"...State social workers, basically.
First, the apps were a nightmare. Kludgy vb, massive sourcecode duplication...If the guy needed new functionality he'd make an edit to his solitary library (more than a meg of code including huge chunks of hardcoded html) save it under a slightly different name, and include it in the application. Effectively the same code linked in a dozen times, but each piece very slightly different.
Second, all the data was child abuse, spousal abuse, etc. Imagine working with that data for weeks on end, wallowing in that hell, and you really had to dig in the data because there were tons of inconsistencies.
Third, the "server room" was a closet with one tiny window, and a floor air conditioner/dehumidifier that had to be emptied by hand. The only tech job I've ever had where toting a 5 gallon bucket of scummy water out of a server room was a daily job. The real icing was the location; the server closet was right off the "visitation room"...The only way into the rest of the building was to walk through a room where child abusers got to visit their abused kids. Yee haw! I could go on about the work environment, but you get the point.
Fourth, the pay. Yea. I could have made more waiting tables. No benefits, and I was a subcontractor, and the contractor was so crooked he kept trying to pay me under the table, basically so he could pocket the chunk of my check that was supposed to go to the government.
That is a shit job. Doing sales customer service for fucking Google does not compare.
It's still an environmental hazard. Better to know that this is an issue with nanotubes, so we can take early precautions and keep this from being like asbestos; a perfectly useful substance that was demonized because it was deployed poorly, and hurt a lot of people.
Not sure why this is a troll. This has been one of the probable issues with carbon nanotubes since day 1, and now there is evidence suggesting that yes, actually, it is an issue.
Anyone who is genuinely surprised should seriously evaluate their "New tech never has downsides" prejudice. When we refuse to acknowledge issues like this early, we end up confirming the paranoia of the anti-tech people, and making ourselves look like jackasses.
Slashdot Mirror
I'd add to that, "Not file a frivolous lawsuit over an unprovable breach of contract."
I started writing up a contract, and about halfway through I realized that it just wasn't worth the money. I'd seen them trump up ridiculous crap before when they knew it wouldn't fly in court, just from spite, and I'd seen them get all spite-y over acts of god.
Some people you just have to write off as too shady to work with.
I ended up turning him down, actually, though the reason he was willing to deal with me afterward was because I'd taken pains, even while they were screwing me over, to be professional.
In the end though, I decided that there was no amount that they could offer that would be worth the pain of dealing with them again. I put them off a few times, but finally I just came flat out and said that I didn't feel like I could trust them enough to do work for them.
Dude, they perp-walked him; he didn't do it on purpose. He started a process, and then they killed his userid, so the process went zombie and just sat around doing its thing without any control, and no one who knew to stop it.
I had a similar story; I got canned, and the second I left the building they started reformatting my equipment to make sure I hadn't left any time bombs. Due to server problem, I'd been using my desktop for development, and I had a huge code package sitting there waiting to be deployed (They fired me because I'd completed it).
So they ended up wiping out the code. Woops. The icing on the cake was that they changed all my passwords, and revoked all my access, but they didn't check for running sessions, so I got home and I was still remotely rooted in a pair of live servers. I changed the MOTD on all the machines I was still logged into to: "When terminating an employee, make sure to abort active sessions before you change the passwords." Then logged off.
I'm sure that sent them into a frenzy of paranoia, but frankly, they were acting like idiots. They went out of business in 3 or 4 months, and the guy who fired me spent a year or so after that trying to get me to do contract work for him.
If you were using perl, you could use the PDF::Reuse library or PDF::API2 to do all kinds of crap. If it's not a valid pdf, the libraries throw all kinds of errors when you attempt to open the file. With that, you can even look at things like the number of pages, the content on the pages, etc.
Mind you, if the rendering is fubared, like a font problem or something, so the page looks like crap, it may still be a valid pdf and pass through any sort of check with no problem. A corrupted image will still show up as an image, screwed up text will still be text, probably even the same text though mashed up and illegible outside the code.
I guess you could use imagemagick or something to render it into a tiff and then compare it...But basically it's a nightmare to try and find out if the page "looks right" without having a human-validated copy lying around, and if you're doing that, then this isn't all that useful.
When they did that with mine they cut the goddamn sprinkler line.
Yee haw, quality control. I'm not saying what cable company it was, but they were a bunch of Cox.
That's why it's handy; spyware seldom uses a standard port, so if you're whitelisting outbound traffic, you keep a lot of nasties from doing their thing. They may get themselves installed, but then they can't do much.
On the other hand, a lot of spyware/malware can be installed by exploiting a vulnerablity on a listening port. This is the most common problem with the Windows machines, because a lot of unneeded apps are installed by default, and they bind to a port and wait for things to start talking to them.
By blocking inbound connections, you save yourself a lot of grief as well, and it is a feature of TCP/IP that you can determine whether an inbound connection is a new connection or an established connection, which means you can filter port 80(HTTP), for example, to allow only "established" inbound connections, and prevent any one out there from exploiting the IIS service that is likely running on your machine.
See, it just doesn't work that way. You're either a part of society, or you're not. People want to get the benefits without having to follow the rules. Part of what society is for is enforcing those rules, so yea, if you flaunt the rules of society, you get the boot.
If you can't find a single society whose rules you can live within, by all means, go live in the ocean and spare the rest of us from having to deal with you.
Most people who block things block ports, not web addresses. So you block all ports except the ones you use, inbound AND outbound, and then you log all outbound traffic that gets blocked.
Most of the time, that will let you know if you've got a virus or a rootkit, though if you have too many ports open, it may not.
On my personal setup I don't web browse or check email on my Windows box, but I do occasionally need to download things so I keep the antivirus around for that. Never had it actually find anything, however.
It is possible to be virus free if you're careful, but I prefer to be certain as much as it is possible to be certain.
I bet you don't use a multi-thousand dollar cisco security appliance either.
My home firewall router does everything a semi-equivalent cisco router would do; VPN, multi-ISP support, DMZ, firewall, etc, etc. The difference is mine is OSS based, running on an old desktop, and cost me, conservatively, 50 bucks, where their equivalent product runs $1000+ and doesn't have gigabit or fibre support.
For what they offer, their appliances are wildly overpriced.
But all the money spent on Cisco's obscenely overpriced security appliances is well spent, right?
There are a lot of people profiteering in the computer security market, and Cisco is up there.
How can you possibly compromise with someone who feels that the only way they can deal with you is to abandon the entire country? It's clearly their way, or they're going to go live on a tiny artificial island.
I'm sorry, I'm just not seeing how my ability to live in the same country with you bastards makes me intolerant. And frankly, I don't feel any special need to be tolerant toward groups whose agenda is so foreign to human experience that their only option is to create their own country.
Typical response.
I have plenty of tolerance for other people's views. I am usually willing to compromise. My views as a whole are pretty moderate, and in the places where they're radical, I am at least open to the possibility that it's me, and not the whole world, that is crazy.
I am certainly not the one who is so hysterically fringe that I'm considering moving myself to an extraterritorial oil rig so I don't have to deal with my fellow citizens. If there is a part of you that feels like that's a good idea, you've got problems.
It's not that bad until you get to shallow water, and even there your biggest problem would be being dashed against the bottom, or taking damage from flotsam and jetsam being pulled around by the tides. Considering that that may be something like cargo containers pulled off a container ship, or a large unmoored barge, the danger is significant.
Hurricanes are a big deal in the air, but their ability to affect water is comparatively minor, usually limited to "pushing" water in front of the hurricane (the so called "storm surge"). The wave action is significant, and in shallower areas it will temporarily rearrange currents dramatically, creating local riptides and such.
You'd probably want to be all the way under though, if that were possible. Wave action could expose a structure that was only a few feet under, and the wind has a much better chance of screwing you up than the water does.
First time I've ever wanted to friend an AC.
Living in a society is about compromise and respect for other peoples opinions and beliefs. Groups inside a society who have no tolerance for other views are a serious issue. Most of the problems societies have are when these groups get too powerful.
Frankly sending them all out into the middle of the ocean sounds like a great idea. Living accommodations optional.
Arrr, but that's not me leg ye saucy strumpet!
//got nuthin
Well it's also finally come around that there are companies who have done it before...Both Mythic(DAoC) and Funcom(AO) have prior experience with long-running MMOs.
I was in the midst of a big coding crunch last year, and one of the random people who I used to indulge back in the glory days when I wasn't in charge of everything came in and started babbling something I couldn't hear because of the headphones.
I pulled them off, and gave him a look, and he said, "Uh, is this a bad time?"
I reached up and unplugged my headphones from the speakers, and from the speakers boomed "LET THE BODIES HIT THE FLOOR! LET THE BODIES HIT THE FLOOR!" Over the course of the day, the music creeps up, and up, and by this time it was deafening.
I turned the volume down, gave the guy another look, and he said, "Uhhh, I'll come back later."
And he never came back.
I gave myself permanent hearing damage cranking up my music loud enough that I could no longer hear the screaming and crying going on in the room behind me.
No, instead you get to agonize over which font the text should be in.
I'll keep my nice clean text, thanks.
At no point do they explicitly state that they're limiting their sample to big, fancy companies. They're saying their "10 worst jobs" are "Tech's 10 worst entry-level jobs."
Now either I don't work in tech, or they're full of shit. And since their "tech" jobs include administrative assistants, and salespeople, I'm calling the whole article a thinly veiled blowjob for VWs advertisers.
The real horseshit is that a year or two working for one of those companies will open so many doors...You deserve to be put through the wringer if you get to fricking start with an industry leader.
Where are all the dead end jobs that pay less, and demand more work? People don't really consider this stuff hard do they?
Probably to start a big discussion about tech's worst jobs. People here actually know, as opposed to VW where they clearly have no clue.
Buncha pussies. This is the worst they've got? I had a tech job once cleaning up database applications for a "Department of Family and Childrens Services"...State social workers, basically.
First, the apps were a nightmare. Kludgy vb, massive sourcecode duplication...If the guy needed new functionality he'd make an edit to his solitary library (more than a meg of code including huge chunks of hardcoded html) save it under a slightly different name, and include it in the application. Effectively the same code linked in a dozen times, but each piece very slightly different.
Second, all the data was child abuse, spousal abuse, etc. Imagine working with that data for weeks on end, wallowing in that hell, and you really had to dig in the data because there were tons of inconsistencies.
Third, the "server room" was a closet with one tiny window, and a floor air conditioner/dehumidifier that had to be emptied by hand. The only tech job I've ever had where toting a 5 gallon bucket of scummy water out of a server room was a daily job. The real icing was the location; the server closet was right off the "visitation room"...The only way into the rest of the building was to walk through a room where child abusers got to visit their abused kids. Yee haw! I could go on about the work environment, but you get the point.
Fourth, the pay. Yea. I could have made more waiting tables. No benefits, and I was a subcontractor, and the contractor was so crooked he kept trying to pay me under the table, basically so he could pocket the chunk of my check that was supposed to go to the government.
That is a shit job. Doing sales customer service for fucking Google does not compare.
It's still an environmental hazard. Better to know that this is an issue with nanotubes, so we can take early precautions and keep this from being like asbestos; a perfectly useful substance that was demonized because it was deployed poorly, and hurt a lot of people.
Not sure why this is a troll. This has been one of the probable issues with carbon nanotubes since day 1, and now there is evidence suggesting that yes, actually, it is an issue.
Anyone who is genuinely surprised should seriously evaluate their "New tech never has downsides" prejudice. When we refuse to acknowledge issues like this early, we end up confirming the paranoia of the anti-tech people, and making ourselves look like jackasses.