I've spent a number of long hours on the phone to Enterasys's GTAC. I usually do this at night and I've been fortunate to get the same tech most of the time, Todd. Last time I called he told me about a photo he was expecting to arive from another customer. If I remember the story behind the photo correctly, apparently this university shut down their network over spring break a number of years back. Over the spring break, the maintenance crew did work on the floor above a wiring closet. Apparently there was a large crack in the ceiling above the rack in that closet. The concrete flowed down into the rack (nice one with sides, doors, etc..) and encased the hardware inside. The picture supposedly showed the cat5, fiber, and power cables sticking out the front of a block of concrete where an old MMAC8 once sat. Supposedly the nutty thing still worked. That is one picture that I have to see. The credit for this one goes to Todd and the other customer with the block of concrete.:-)
Sure, any aircraft should be able to fly in that zone without hassle. That said if we were flying in a definite path than we shouldn't have anyone flying into us. If both our plane and China's plane had the same flight path, they should both change course. Of course if we were flying along and their plane elected to get in our way (read make their flight path our flight path), that's their fault and they should change. We were there first. Who knows what really happened. Knowing exactly where the incident occured would be nice though.
One thing that was broadcast far and wide when the collision first went public was that we (the US) were in international airspace. Since then I have heard nothing about that. If we were in international airspace, why would the Chinese plane be near us? To provoke us? Obviously our plane couldn't fight back. If we were in China's airspace than I can understand their plane buzzing us to convince us to leave. We all know that those planes are very accurately tracked via GPS, radar, and every other means available at the moment. Why don't they just show us were exactly those two planes were when they collided? If we were in China's airspace, apologize and get on with life. If we were in international airspace, China should return the crew and plane immediately. Either way, there is no excuse for China's boarding and dismantling of the US plane, especially since we are not at war. That's an act of war I think. Now we all know that it would happen one way or another but normally it's private. In a case like that,the plane would not be sitting on a runway out in the open. It would be in a closed hanger. I also don't by the video of the Chinese widow who's supposedly in the hospital because of her husband's death. I don't mean to sound unsympathetic, but it looks like quite an act to me. The movie "Wag The Dog" is probably much more realistic than we think. Which country is covering their ass? Who knows. I think the only way of establishing who was at fault begins (and possibly ends) with the location of the planes when they collided.
My former university had a security issue during the Fall of 98 I believe it was. Perhaps it was the Spring of 98. Either way, mandatory passwords changes soon followed. Initially the faculty/staff were given until January '99 to change their password or their account would be disabled (I think it was Fall which would have given them 2-3 months warning). That's about 5000-7000 faculty/staff. Roughly 1/4 didn't change them and had their accounts were disabled. They were forced to come to our helpdesk and present their campus ID to get the accounts re-enabled with a new (acceptable password). That wasn't initially received well but a little PR work via our campus paper helped. 6 months or so later and all the existing accounts (students) went through the same scenario. Shortly after the breakin, one of our sysadmins wrote a quick script to crack our central password file (around 35,000 entries) and IIRC roughly half of them had easy to guess no-brainer passwords. Now every 6 months all passwords must be changed. Previous passwords can't be reused. Since then hacks via social engineering have gone way down. I just wish I could do something similar at the ISP contract admin for.
I don't claim to be an expert or anything but I think it would be blatently obvious if Microsoft pulled something like that. Besides, their crimes have already been committed in this country and before any potential move to a foreign country. They are still responsible for their actions in this country. Whether or not they are here to defend themselves or not, they can still be tried and damages can be asessed. If they manage to make accusations against anyone person, couldn't they extradite those parties? Doesn't the US have an extrasition thingy with Canada? If they really wanted to hurt M$ and they moved to Canada, apply heavy tariffs to imported commercial operationg systems. Drive Canada so mad that M$ will either have to move back or get the hell out of Canada. Anyhow, this was something I thought.
If they were hit by a lot of classactions suits and they're pocket book is actually starting to suffer, they'll just find another way to fsck the consumer. Maybe they'll go tp all subscription based software. Hell maybe they'll do the same to their hardware. "Your optical mouse driver expires will expire on 6/6/6." Maybe they'll back their installation support down to 30 days, free tech support down to 30 from the purchase date, and charge for everything after that. As much as I'd like to see M$ take one up the ass for a change, I have doubts as to this being the Kodak moment we've all dreamed of.
How can that be offtopic? I'm talking about sex.com and that's what the article talks about. I personally think that whenever a moderator uses his/her points to lower a person's rating, it should cost them double. It's too easy for a person's personal beliefs to impact one comment in a setting such as this. There is a major lack of checks and balances here.
Obviously they must not have counted the number of personal pron sites. Frankly I think including those would get those numbers up above the million mark easy. How many of you/.ers out there made your personal collection available on one of you Linux boxes?
For my April Fool's joke, I think I'mm going to write a cron job to change the bridge priority on our acting root bridge every 5 minutes. ie, every 5 minutes our entire campus network will respan.:-)
...thanks. Many people get overlooked in the process of contributing to such a grand project, so let's not neglect to commend them for their efforts. All of us appreicate your what you do!
If New Line was making a movie about something related to the game, I could understand Blizzard's concern, but they aren't. Not even close. Drug lords... Fantasy role playing game. Can someone show me a similarity here? Would Blizzard still bitch if they called it "Mr Diablo" or "The Diablo"? What about if I made a movie about a grand earthquake that changed Earth and humanity as we know it and I simply called the movie "Quake". Would ID sue me? My step uncle owns a business called NCR. Yes, like the cash register company. National Computer Retail. They aren't in competing arenas so they aren't stepping on each other's feet. I don't see how the movie "Diablo" could even be compared to the game. Now if I had a movie called "Unreal Tournament" or "Starcraft" I could see some concern. Those are fairly unique words or phrases. Shit I think I trademark the words "the", "of", and "day". Most movies uses one of more of those words. I could write a shitty little game and call it "day" or "the" and then cry trademark infringment when someone used one of those words in the title of a movie. How many past movies have used the word "Diablo"? There's probably a John Wayne movie that used it. I'm going to bed; enough preaching to the choir. g'nite
I'm listening to it right now, after the break. Throughout the arguements I repeatedly found myself screaming at my computer, wishing I could be in the court room to slap the DOJ when the say something stupid (not helping our cause) and help the "Your Honors" understand something they don't quite get. It's very frustrating. Now they're talking about Quicken and how IE is such an intregral part of it. These people are fucking idiots! ARGH!!
Ok, by birth I'm a Mac fan. (Doesn't the nick make that obvious? I love Apple.) I love their hardware. I love their software. Don't get me wrong, there are plenty of things that Apple does to piss me off. Can anyone say One-Click (tm)? That's a big black eye as far as I'm concerned. This themes shit is just as big a black eye in my opinion. Not only is it a black eye, but it's a bloody nose, cut lip, and a kick to the cojones. As a Mac guru, I'm embarassed as hell at things like this. How am I supposed to evangelize the Mac platform if Apple fuels the fire of the opposing team? Come Apple, quick fscking around. You don't have to act like others in the industry to win over new clients.
What an asshole that guy is. He's not doing this for the good of the economy or the artists that make that music. He's doing this to make a name for himself.
Now that I think about it, Apple has the same feature. What about the autorpm stuff for Linux? Now granted, it's not patching a binary, but it is updating them.
Whomever granted that patent must have been a royal dumbass. Tell me something. Would GNU "patch" be prior art? I know what Symantec is talking about here. It's now part of InstallerMaker. I forget it's original name (UpdateMaker?) but you basically give it two files to compare and tell it which one you want it to look like in the end and it generates an installer to do just that. I've used it before on numerous installers I've built. That's not exactly a fancy thing though. In fact I would think it's pretty common. I write an AppleScript to take a binary (Apple binaries have two forks, data and resource--the resource contains stuff like sounds, picts, strings, menu info, etc...) and I have it take an pict file and binary and replace a specific ICON# within that binary with my pict file and set a few attributes. That's a patch on an application. That would violate their patent. What about patching a running kernel like MOL (Mac-On-Linux) can do? I'm a bit baffled by this claim. In the article they also say
"...may be also be used to update general computer readable files, which may include data files, program files, database files, graphics files, or audio files..."
So what, does that mean that CVS, rsync, and bk trample on their patent? They are applying updates to files, any file for that matter. What about VOODOO, a version control system for general documents for the average Joe. That could easily be construed as an app making changed to general computer readable files, which may include data files. I wonder if I would be breaching their patent if a buddy sends me a document to read and I send him back changes to make to it. I didn't create an app to it but I am updating general computer readable files, which may include data files. I really don't know what to say about this patent. I never knew Symantec to be like this. I'm glad they aren't enforcing it though. I know that you must enforce trademarks vigourously from day one or risk loosing them. That was spelled out in a quote from a recent discussion on/. I believe. I wonder if the same can be said about patents. Can they selectively enforce it? Can they say they won't enforce it and the next year start enforcing it?
I know this is long and I apologize for that but this article is one that I have enough past experience to give good commentary on this topic.
While I haven't done exactly this, I have had a lot of past experience which is directly applicable. I worked at reasonably good-sized University (+35k users) as The Mac Guy at our IT Helpdesk for a long time. Before that I held together a school district, while being a student. For most of that time I was a student. We were the front end for the admins in the basement that really didn't have time to answer hordes of basic questions. We did the phone, e-mail, and walk-in tech support. Myself and a few others went the extra mile and did onsite calls for free. Our supervisor was a full-timer who had been there for a long time. Our relationship with him was excellent. He's a great guy (I'm switching tenses because he's still there while I've moved on). Between our admins and the helpdesk it was sometimes another story entirely. Some treated us well and respected the work we did to keep the masses away from their doors. Others thought we were dirt beneath their feet. In fact I recently sent an e-mail too one of their rather fickle admins advising him about two of their hosts send SNMP GetRequests to the broadcast address in the building that houses one of my servers still there. I have yet to hear from him. I'm now working at a peer University not as a student but as the Network & Systems Manager. Apparently the added length to my title isn't enough to get a little respect from him. Back to the helpdesk. From the students/faculty/staff we were usually praised. Occasionally we were on the receiving end of a lot of grief. The powers that be (read: admins in the basement) would elect to do something that affected the campus at large. Did they ask our opinion since we were the ones that actually dealt with the masses and knew them best? No. Never did. That usually promoted many irate people to stop by for a friendly visit or would temporarily double our work load. Another sign that we weren't respected in the least is that we had no budget. None. They also kept cutting the allowed number of students employees on us. During the course of a day, you will probably have 6-8 different student work just to cover the office while working around their schedules. Being the type of person I am, if there wasn't enough people when it was time for me to leave for class, I'd stay. That reflected in my grades. People would forget to show up, leave early, make excuses, blah blah blah and the supervisor and I would have to cover for them. This happened almost daily. No wonder the poor man was so frustrated and in bad need of a vacation. There was also the problem of unprofessionalism among the students. I'm not talking about wearing ties, talking in a perfect proper English accent (it's a joke people), or anything that extreme. Just a general professional conduct among the students workers. Some would argue with the customers, call them names, horse around with customers in the office, stop what they're doing with a customer to AIM their buddy about going out and getting drunk later, wearing clothes with holes in the butt, etc... I'm not perfect by any means but I know when to act like a pro and when I can relax a bit. Some students were so lazy that when a someone called to see if their computer was fixed, they student that would answer the phone would field the question, say they're gonna go check, set the received down, play some Quake for a minute or two, pick up the received and inform the user that it wasn't. They wouldn't even extract their asses from the chair to walk in the back and check. Sometimes they'd answer a question with a blatantly wrong answer. Sometimes it's a question that would have required a little research but they'd never look into it. They'd just guess.
We also had some really good students work for us; students that you'd actually miss when they left and had trouble finding another student of the same caliber to fill their shoes. They might not have always been on time for their shift. Sometimes they would have their back to the door and get caught telling a dirty joke when some older female faculty member walks in the door. They were honest though. If they didn't know the answer to a question, they'd make an honest effort to find the answer. If they needed some time off for a big test coming up, they'd ask you for the time off because of it or offer to sit in the back and study and come out if you needed some help on the floor. They were knowledgeable about what they did and they learned something new each day. Maybe they took the time to learn something new on their own time. Those are the people that wrote scripts to make everyone's job a little easier; scripts that are still in use today, thank you very much. If some obscure problem cropped up with the network in such and such building, they would feel comfortable calling the campus netadmin and telling them something was wrong and possibly what was wrong. They'd also keep him on the phone for a lengthy conversations and tag along with him on trouble shooting calls (thanks Richard!). Those students could easily go on to a successful career in the IT world. Some would become netadmin such as myself. Those students of today would become tomorrow's admins.
Now, this doesn't mean that I feel students can completely take over an IT department. Someone earlier in this thread mentioned something about maturity. That's part of it. Some said they don't have the sheer knowledge required to do the job. That's part of it too. Someone else also they just don't have the ability to be profession. That can be true sometimes. If you could find enough students of the highest grade, the top caliber of IT-thinking students, you could possibly do it. The problem is, those people that are usually of the high quality that you need are all leaders. They might not work together in the best manner possible. Too many chiefs arguing over how to do tend to a horse leaves no one to watch the fire in the teepee and it all burns down. They also might not have the experience with large budgets to control such a beast. Suppose they spent $300k upgrading the labs on campus and forgot to set aside some $$ for their I1 leased line. Whoops. Privacy issues come up too. When I worked the helpdesk, to assign a person their userid/passwd we had to see a photo ID, get their birth date, get their last name, and get their SSN. Then we'd write down the userid/passwd on paper and give that to them. What would stop us from using that info maliciously? Honesty. We were employees of the State. We could only see some much info. The rest was reserved for people that actually needed to see it like our supervisor. In an all student environment, who's the supervisor? Some part time student? I hope not. A student-run IT Helpdesk would work if there was a full timer over all of them, helping to coordinate their efforts. Students running servers? Mmmmmmmmaybe. I think back to what I knew about Linux when I lived in the dorms and I shudder. I was such an easy target it isn't even funny. I was a horrible security risk for our campus. Would you want a student like that running your university's mail server? Hell I know full time people I don't trust with something like, let alone a student.
Another thing to think about is that there is a much higher turnover rate with student than full time people. A student helpdesk worker is only likely to work for the helpdesk for 1-3 years and then leave for an internship or better paying job. A full-timer may be there for years upon years. The knowledgeable staff turn over rate goes down greatly when there are more full-timers. Now this might not hurt in the helpdesk arena but in the server arena it matters a lot!
What about netadmin positions? Do you really want students having master keys to buildings? To be honest I sure don't. I don't even want them to be able to check out a master key. Temptation is Man's worst enemy. Let's talk about knowledge for a while; network knowledge. Think back to when you were in college. Pretty good with computers, right? What did you know about networking? You know much about routing? How about spanning tree? Understand what switches and hubs really do and how they do it? VLANs? Media selection? How about wiring rules, do's and don'ts? Ever do VPN for specific users within a building? Ever use ATM? I didn't think so. I was lucky. I had early exposure to networking and it made a good impression on me. I liked it and I understood it. That's more than I can say for some of the people I've worked (and work) with. Would you really want a student in that position? Sure you can train them but do you really want to shell out $4k to send them to a class for a week and then have the up and decide to leave a few months later? A position like that requires 24/7 on call availability too. Sometimes you're lucky that a student shows up for work at all. Let me ask ya'll something, how many of you have ever been drunk and done something stupid on your computer--sent and e-mail or something? How many of you have ever been root while drunk? Now would you really want a student to have access to root on your campus mail or auth server when they're drunk? What about during their hangover afterwards (unless they are like myself who's lucky enough to not get hangovers)? I'm not ragging on students. I think something like this has great potential. That former university of mine employed what they called "Student Administrators". Those were students with programming background in their 3rd year of college that had the ability to take on some of those mundane sysadmin tasks. Those student usually went on to great IT jobs or were hired in house. That's excellent. Making every IT position a student position isn't quite so excellent. I think this would be an interesting story to follow up on though.
Just how is an ISP supposed to monitor/regulate the newsgroups for something like this? Are they supposed to go through every posting and check to make sure it's not kiddie pron? What if they can't tell for certain? What if they can only see part of the body and it looks like part of a body from an off-age person and later on it's proven that it wasn't? How the hell are they supposed to know that? Are they going to be held accountable for email that traverses their MX host as well? If I use email to plan the assination of that dumbass president we have (that has actually decreased the unemployment rate for comedians because he's just to easy a target) is my ISP an accessory because I used their SMTP server? What if I didn't use their SMTP server but an SMTP server of another ISP. Is my ISP still an accessory because they carried my traffic? What if someone signs up for internet access at my ISP and they quickly post a webpage with kiddie pron and run (hit and run style like a lot of spammers use). Someone happens to surf over and sees that and calls the police. Will they ask me (the ISP) to take it down or will they instantly arrest me since I'm the ISP hosting that content? How am I supposed to know what that customer was going to post? What if he posts a page about goat sex....
If I own a business and put up a bulletin board (physical, not electronic) for my employees to use for free and somebody posts a piece of kiddie pron on it, am I liable? Should I have to put that bulletin board behind glass, lock it down, and have an approval process for new postings? What if they tape it to the glass? How the hell are we supposed to regulate the actions of someone else? Shit the police can't even regulate the speeds of someone else! What if someone posts not a picture of kiddie pron but a short story about underage sex? Am I liable? What am I liable for? The 1st Amendment covers that. Now it may offend some woman and she sues someone for sexual harrasment. Whos' she going to sue? Me? Do I have to have hire someone to stand next to that board and check the content of everything that's posted as it's posted? Does anyone else think this is royally fscked up?
This is just a Microsoft PR spin. Call it political mudslinging if you will. If it smells like M$, looks like something a marketing guy drew up while watching Opra, and tastes like shit, then it came out of M$'s PR Department.
Slashdot Mirror
--
--
--
--
--
--
--
--
--
--
--
--
No, I'm not whoring (karma whoring).
--
--
--
--
If the answer is yes, when will we be petitioning the courts for an amendment to the Consitution that protects our Freedom to Think?
--
--
--
--
--
While I haven't done exactly this, I have had a lot of past experience which is directly applicable. I worked at reasonably good-sized University (+35k users) as The Mac Guy at our IT Helpdesk for a long time. Before that I held together a school district, while being a student. For most of that time I was a student. We were the front end for the admins in the basement that really didn't have time to answer hordes of basic questions. We did the phone, e-mail, and walk-in tech support. Myself and a few others went the extra mile and did onsite calls for free. Our supervisor was a full-timer who had been there for a long time. Our relationship with him was excellent. He's a great guy (I'm switching tenses because he's still there while I've moved on). Between our admins and the helpdesk it was sometimes another story entirely. Some treated us well and respected the work we did to keep the masses away from their doors. Others thought we were dirt beneath their feet. In fact I recently sent an e-mail too one of their rather fickle admins advising him about two of their hosts send SNMP GetRequests to the broadcast address in the building that houses one of my servers still there. I have yet to hear from him. I'm now working at a peer University not as a student but as the Network & Systems Manager. Apparently the added length to my title isn't enough to get a little respect from him. Back to the helpdesk. From the students/faculty/staff we were usually praised. Occasionally we were on the receiving end of a lot of grief. The powers that be (read: admins in the basement) would elect to do something that affected the campus at large. Did they ask our opinion since we were the ones that actually dealt with the masses and knew them best? No. Never did. That usually promoted many irate people to stop by for a friendly visit or would temporarily double our work load. Another sign that we weren't respected in the least is that we had no budget. None. They also kept cutting the allowed number of students employees on us. During the course of a day, you will probably have 6-8 different student work just to cover the office while working around their schedules. Being the type of person I am, if there wasn't enough people when it was time for me to leave for class, I'd stay. That reflected in my grades. People would forget to show up, leave early, make excuses, blah blah blah and the supervisor and I would have to cover for them. This happened almost daily. No wonder the poor man was so frustrated and in bad need of a vacation. There was also the problem of unprofessionalism among the students. I'm not talking about wearing ties, talking in a perfect proper English accent (it's a joke people), or anything that extreme. Just a general professional conduct among the students workers. Some would argue with the customers, call them names, horse around with customers in the office, stop what they're doing with a customer to AIM their buddy about going out and getting drunk later, wearing clothes with holes in the butt, etc... I'm not perfect by any means but I know when to act like a pro and when I can relax a bit. Some students were so lazy that when a someone called to see if their computer was fixed, they student that would answer the phone would field the question, say they're gonna go check, set the received down, play some Quake for a minute or two, pick up the received and inform the user that it wasn't. They wouldn't even extract their asses from the chair to walk in the back and check. Sometimes they'd answer a question with a blatantly wrong answer. Sometimes it's a question that would have required a little research but they'd never look into it. They'd just guess.
We also had some really good students work for us; students that you'd actually miss when they left and had trouble finding another student of the same caliber to fill their shoes. They might not have always been on time for their shift. Sometimes they would have their back to the door and get caught telling a dirty joke when some older female faculty member walks in the door. They were honest though. If they didn't know the answer to a question, they'd make an honest effort to find the answer. If they needed some time off for a big test coming up, they'd ask you for the time off because of it or offer to sit in the back and study and come out if you needed some help on the floor. They were knowledgeable about what they did and they learned something new each day. Maybe they took the time to learn something new on their own time. Those are the people that wrote scripts to make everyone's job a little easier; scripts that are still in use today, thank you very much. If some obscure problem cropped up with the network in such and such building, they would feel comfortable calling the campus netadmin and telling them something was wrong and possibly what was wrong. They'd also keep him on the phone for a lengthy conversations and tag along with him on trouble shooting calls (thanks Richard!). Those students could easily go on to a successful career in the IT world. Some would become netadmin such as myself. Those students of today would become tomorrow's admins.
Now, this doesn't mean that I feel students can completely take over an IT department. Someone earlier in this thread mentioned something about maturity. That's part of it. Some said they don't have the sheer knowledge required to do the job. That's part of it too. Someone else also they just don't have the ability to be profession. That can be true sometimes. If you could find enough students of the highest grade, the top caliber of IT-thinking students, you could possibly do it. The problem is, those people that are usually of the high quality that you need are all leaders. They might not work together in the best manner possible. Too many chiefs arguing over how to do tend to a horse leaves no one to watch the fire in the teepee and it all burns down. They also might not have the experience with large budgets to control such a beast. Suppose they spent $300k upgrading the labs on campus and forgot to set aside some $$ for their I1 leased line. Whoops. Privacy issues come up too. When I worked the helpdesk, to assign a person their userid/passwd we had to see a photo ID, get their birth date, get their last name, and get their SSN. Then we'd write down the userid/passwd on paper and give that to them. What would stop us from using that info maliciously? Honesty. We were employees of the State. We could only see some much info. The rest was reserved for people that actually needed to see it like our supervisor. In an all student environment, who's the supervisor? Some part time student? I hope not. A student-run IT Helpdesk would work if there was a full timer over all of them, helping to coordinate their efforts. Students running servers? Mmmmmmmmaybe. I think back to what I knew about Linux when I lived in the dorms and I shudder. I was such an easy target it isn't even funny. I was a horrible security risk for our campus. Would you want a student like that running your university's mail server? Hell I know full time people I don't trust with something like, let alone a student.
Another thing to think about is that there is a much higher turnover rate with student than full time people. A student helpdesk worker is only likely to work for the helpdesk for 1-3 years and then leave for an internship or better paying job. A full-timer may be there for years upon years. The knowledgeable staff turn over rate goes down greatly when there are more full-timers. Now this might not hurt in the helpdesk arena but in the server arena it matters a lot!
What about netadmin positions? Do you really want students having master keys to buildings? To be honest I sure don't. I don't even want them to be able to check out a master key. Temptation is Man's worst enemy. Let's talk about knowledge for a while; network knowledge. Think back to when you were in college. Pretty good with computers, right? What did you know about networking? You know much about routing? How about spanning tree? Understand what switches and hubs really do and how they do it? VLANs? Media selection? How about wiring rules, do's and don'ts? Ever do VPN for specific users within a building? Ever use ATM? I didn't think so. I was lucky. I had early exposure to networking and it made a good impression on me. I liked it and I understood it. That's more than I can say for some of the people I've worked (and work) with. Would you really want a student in that position? Sure you can train them but do you really want to shell out $4k to send them to a class for a week and then have the up and decide to leave a few months later? A position like that requires 24/7 on call availability too. Sometimes you're lucky that a student shows up for work at all. Let me ask ya'll something, how many of you have ever been drunk and done something stupid on your computer--sent and e-mail or something? How many of you have ever been root while drunk? Now would you really want a student to have access to root on your campus mail or auth server when they're drunk? What about during their hangover afterwards (unless they are like myself who's lucky enough to not get hangovers)? I'm not ragging on students. I think something like this has great potential. That former university of mine employed what they called "Student Administrators". Those were students with programming background in their 3rd year of college that had the ability to take on some of those mundane sysadmin tasks. Those student usually went on to great IT jobs or were hired in house. That's excellent. Making every IT position a student position isn't quite so excellent. I think this would be an interesting story to follow up on though.
Cheers,
--
If I own a business and put up a bulletin board (physical, not electronic) for my employees to use for free and somebody posts a piece of kiddie pron on it, am I liable? Should I have to put that bulletin board behind glass, lock it down, and have an approval process for new postings? What if they tape it to the glass? How the hell are we supposed to regulate the actions of someone else? Shit the police can't even regulate the speeds of someone else! What if someone posts not a picture of kiddie pron but a short story about underage sex? Am I liable? What am I liable for? The 1st Amendment covers that. Now it may offend some woman and she sues someone for sexual harrasment. Whos' she going to sue? Me? Do I have to have hire someone to stand next to that board and check the content of everything that's posted as it's posted? Does anyone else think this is royally fscked up?
--
--
--