Slashdot Mirror

lol.. What an idiot. Whether a woman looks like a whore or not does not give anyone the right to violate her just as it doesn't give anyone the right to kick your ass- even though we might think you deserve it. When she says bugger off creep, you need to move on.

Rape statistics have little to do with it. For one, a lot of the rapes were unreported, for two, there was a level of social justice the simply is not tolerated today so rapists don't really have to worry about being hunted down a killed by her kin, three, in the 50s and 60s we institutionalize mentally ill people a lot earlier and a lot longer on a lot less grounds, and finally, and finally, we changed the laws on what was rape in the 60's including the reporting for record keeping to include more acts and again later in the 70s and 80s to include yet more activities.

If you look at the statistics which only include what was reported, you will see a jump in all violent, property, rape, robbery, assault, burglary and, motor vehicle theft crimes too. It seems the murder and larceny rates stayed about the same. Is that all because of how a woman started dressing or could there be other issues involved?

but hey, this has nothing to do with rapes as near as I can tell. None of the articles listed mention it. It is literally as I said, professional disclosure of personal information being used for non professional uses and behavior that would get most people fired from their jobs.

This study conducted in the late 90's found that about 17.6% of American women had experienced attempted or completed rape, with 13% experience completed rape (more summary stats here), and this study from 2007 found that 18% of American women had experienced rape. I'm not sure Rei's number of 1 in 4 came from (a different country perhaps?), but a rate of 1 in 6 is shockingly high.

There are some major issues, here.

One, I'm familiar with the study you linked concerning housework distribution. Are you aware that in that study, half again as many men were employed full-time as the women? Do you agree that if one person is employed full time and the other isn't, that the one that is not should take on a greater share of housework? Also, you claim the link points out a correction for this, but I don't see one. Can you cite, please?

Two, recent studies show that lesbian couples experience domestic violence at a similar rate to heterosexual couples, and it is known that men underreport, so I wouldn't say the situation is so cut and dries as "man=criminal, woman=victim."

Three, you attack the "women want wealth" position as not being supported, but cursory searching turns up evidence. Here's a couple:
Women more attracted to men in expensive cars
Women's orgasm frequency increases with the wealth of their partner

Carrying it so far as to imply the majority of divorces are because of crimes perpetrated by men is, frankly, sensationalist. I have seen deep discourse from you on this site, so I know you are not trolling, but your claims, implications, and position here are not defensible.

It sounds from this and other comments like some form of self-administered CBT worked to treat your own depression. That's good, and it would be wonderful if that worked for everyone suffering from depression. However, that doesn't mean that your own results will work for everyone else any more than someone whose cancer went away after drinking special mineral water can claim that other cancer victims are just not taking the initiative to drink some mineral water and get on with their lives.

Now if only they could come to the realization that they don't need to launch them from a Florida swamp, at sea level with plenty of humidity.

NASA could easily come to an arrangement with a friendly country (while there are still some around) and set up launch facilities someplace like the Atacama Desert of Chile, which is closer to the equator (about 10 degrees of latitude closer), higher (about 8K ft), and drier (drier than anywhere else on the planet). I'd guess there's not much lightning either (Florida is the most lightning-prone place in the US).

But I guess that having a major federal employer located in a state is worth more as a political plum than eliminating a bunch of difficulties that cost us incredible amounts annually and make launches much more challenging than they really need to be.

We don't have a problem with having military bases all over the planet, and we even have a prison in Cuba. I'm sure that all sorts of government (state as well as federal) work is being offshored to various places around the globe. So why can't we contract with Chile to set up launch facilities there? The Europeans had no problem seeing the value in setting up observatories there.

The important thing is not where we launch from, it's where we launch to.

I do not know what to make of this. I just thought it needed to be shared. 16872638 incest father encourage touch penis 2006-03-26 20:04:02 http://muse.jhu.edu/ 16872638 incest father encourage touch penis 2006-03-26 20:04:02 http://nasw.org/ 16872638 incest father encourage touch penis 2006-03-26 20:04:02 http://www.fhi.org/ 16872638 list drugs interact with each other 2006-03-29 01:02:06 http://www.centerfordrugsafety.org/ 16872638 list drugs interact with each other 2006-03-29 01:02:06 http://www.fda.gov/ 16872638 list drugs interact with each other 2006-03-29 01:41:37 http://www.personalmd.com/ 16872638 ohio senate bill 17 2006-03-29 01:45:09 http://www.hslda.org/ 16872638 ohio senate bill 17 2006-03-29 01:45:09 http://www.ohiosenatebill17.org/ 16872638 ohio victim counseling service prosecute 2006-03-29 01:46:34 http://www.usdoj.gov/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.sexualassaultresources.org/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://odmrdd.state.oh.us/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.drc.state.oh.us/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.odvn.org/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.ag.state.oh.us/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.drc.state.oh.us/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.drc.state.oh.us/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.drc.state.oh.us/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.usdoj.gov/ 16872638 victim witness coordinator in columbus ohio 2006-03-29 01:50:26 http://www.usdoj.gov/ 16872638 multiple drug interactions paroxetine 2006-03-30 12:57:21 16872638 multiple drug interactions safety 2006-03-30 12:57:56 16872638 drug interaction checker safety 2006-03-30 12:58:47 16872638 dictionary words that start with 2006-03-30 14:05:03 http://dictionary.reference.com/ 16872638 dictionary words that start chu 2006-03-30 14:06:58 http://www.hyperdic.net/ 16872638 case history woman abuse childhood rape 2006-03-30 17:58:32 http://www.womanabuseprevention.com/ 16872638 case history woman abuse childhood rape 2006-03-30 17:58:32 http://www.survivorinfo.org/ 16872638 case history woman abuse childhood rape 2006-03-30 17:58:32 http://www.musc.edu/ 16872638 case history woman abuse childhood rape 2006-03-30 17:58:32 http://www.thedoctorwillseeyounow.com/ 16872638 case history woman abuse childhood rape 2006-03-30 17:58:32 http://escapinghades.pandys.org/

Could THIS be what you seek? Or maybe you'd prefer it in BOOKMARKLET form?

billy - no,no...think nothing of it...I know I do

http://www.unicat-communications.de/zentral/bildar /darlmcbride.jpg

http://www.fda.gov/oc/whiteoak/whiteoakdedication/ orrinhatch.jpg

http://hcc.musc.edu/images/hollings.jpe

FYI, there's another option besides ECT. There's a new technology called Repetitive Transcranial Magnetic Stimulation (rTMS). brief intro here

rTMS seems to have cured the depression that I had going on for the last 10 years (I'm 22). I'd tried nearly every kind of antidepressant, with no good/lasting results, and was ready to off myself, as I didn't consider ECT an option due to the risk of memory loss and/or brain damage. I was the one to mention rTMS to my last shrink (learned about it online, Wired might have had the first mention I saw), and somehow got a referral. I had an initial appointment, a brain scan the next day, and the day after that I was told & shown that parts of my brain were abnormal hyperactive and drawing resources away from the other parts. I had my first rTMS treatment that day and started a low dose anti-epilepsy drug and, tho I barely believe it myself, haven't been depressed since. The only side effects I've had are excedrin-treatable headaches here and there, and increased mileage on my car due to driving to chicago for maintenance treatments.

When I say I haven't been depressed, I mean the following:
Sad thoughts will happen, but my brain doesn't grab them and run off into despair anymore. Sometimes I'll come across thoughts that just a month and a half ago would have sent me into hours of crying or inertia, but now I'm able to be mindful, to go "oh, that's sad. hmm. that's sad because xyxyxy. I might as well think about something else." And then I do so and the parts of my brain that were white (overactive) in the scans don't dominate and I can just be myself and go about my day. I feel like my full brain capability is back. I'm more attentive, more creative. I actually feel like getting out of bed and doing things.

AND I can use my laptop, read, or even play gameboy during the treatments! in a comfy chair!
Plus now I have cool pictures of my brain!!!! I'm psyched to get scanned again and see what my normal brain activity looks like.

Seriously, go see a neurologist and definitely get a brain scan before getting ECT. IMHO, ECT is too broad a disruption to the brain when it's quite possible that it's more of a localized problem. rTMS is precise, requires no anesthesia or muscle relaxants (all you have to do is keep your head still), and far, far less neurological side effects like memory loss. (I haven't forgotten a single thing).

aie, what a first post. had to say something, tho.

as to the initial article, the implants would be a fantabulous idea for people who respond to stuff like rTMS but need it very frequently to keep sane. where I am now, I'd rather go to the doctor's periodically than have something stuck in my head, unless it gave me superpowers or something.

Last time the goverment allowed us to hire or replace someone, we tried something new.

First, there were horrible resumes sent in and the only thing that stopped us from deleting them was if they sent a word document. We read most of them no matter what.

Second, we only cared what the persons experience was, an opensource project was a definite PLUS!
A resume was only crappy if they had nothing real
to show. We then selected about half for the interview process.

Third, we had two interview levels. The first was IRC, we would send an email telling the person to meet us on irc and then have a chat with them. This let us know if the person was for real or not. Whether they wrote a bad resume or not. It was great to do this, everyone on the team was involved in the interview and it was logged. Also, it was completly unbiased with relation to sex or race. Then after we had about 3 canidates we interviewed them in "real life". It was a quick and fun experience. And we hired someone that kicks ass!!

We use sluice to handle various IT requests. Firewall rules for example. People submit requests, it goes to the certain person via a sluice or jabber message and then the request gets acted upon.

http://radinfo.musc.edu/images/photos/MRIvsChair01 .jpg

http://radinfo.musc.edu/images/photos/MRIvsChair02 .jpg

http://radinfo.musc.edu/images/photos/MRIvsChair01 .jpg

http://radinfo.musc.edu/images/photos/MRIvsChair02 .jpg

I seem to recall Eric Wasserman giving a paper on this in 1996 or thereabouts.

There is actually a lot of stuff on this floating around the 'net, as you would expect of a technology that is that old.

Some discussions in more depth can be found here, written for a general audience, and herehere for those who want more meat.

I seem to recall Eric Wasserman giving a paper on this in 1996 or thereabouts.

There is actually a lot of stuff on this floating around the 'net, as you would expect of a technology that is that old.

Some discussions in more depth can be found here, written for a general audience, and herehere for those who want more meat.

Well, where I work we have the dress code of "clothes required" and that is it. Some guys wear business casual and some where t-shirts and tennis shoes. You can check us out here. Anyway, my thought it is this, most computer guys (programmers,scientists, etc.) are problem solvers.That is their job. To solve problems with the tools they are given or to give users the appropriate tools to solve their problems.I think it does not matter what they are wearing. As long as they solve those problems. And if you are all jazzed up in a suit then you (in my opinion) give the impression you are trying to sell something and not solve my problems. So, until they give me a cool 'computer scientist lab coat' I am going to wear what I am comfortable in and be the problem solver I am supposed to be. :)

Well, where I work we have the dress code of "clothes required" and that is it. Some guys wear business casual and some where t-shirts and tennis shoes. You can check us out here. Anyway, my thought it is this, most computer guys (programmers,scientists, etc.) are problem solvers.That is their job. To solve problems with the tools they are given or to give users the appropriate tools to solve their problems.I think it does not matter what they are wearing. As long as they solve those problems. And if you are all jazzed up in a suit then you (in my opinion) give the impression you are trying to sell something and not solve my problems. So, until they give me a cool 'computer scientist lab coat' I am going to wear what I am comfortable in and be the problem solver I am supposed to be. :)

Security is only one issue that needs to be considered in implementing wireless networking. We identified three key issues in developing a wireless strategy: (1) security that was "good enough", (2) end-user simplicity, and (3) technical staff set-up and management.

1. For us, security that was "good enough" meant having by-user authentication, putting the access points behind a router, and being vigilant to evidence of inappropriate use. There's not much point in putting bars on the windows when you never lock the door anyway.
2. For end-user simplicity, we wanted to support a diverse client userbase while minimizing the amount of configuration and additional software required by client machines.
3. For set-up and management, we wanted to depend on open-source and free software packages that we were already familiar with and not have the administration become a burden.

We eventually decided to use Nathan Zorn's Authentication Gateway. Wireless connections are blocked at the gateway until users connect via ssh. Clients need to have ssh and know the name of the gateway: everything else gets configured automatically. The system uses iptables, PAM, and ssh and the only admininstration required is to build accounts. The system might not scale well, but works well for an entity our size (one department).

I gave a presentation about our conclusions.

The ITLAB rocks! :)

"The power of UNIX is in connecting small, fleet-footed tools. What we need now is to create an environment, where users can easily create customized tools for the way they work, and developers can easily add new functionality."

Here at MUSC, the IT Lab is trying to do exactly that. We are trying to use the web as a way to string together tools and make it as easy as possible for the user. Check out the toolbox for some of the attempts. We are just a small group and any ideas to better our tools would be great!

"The power of UNIX is in connecting small, fleet-footed tools. What we need now is to create an environment, where users can easily create customized tools for the way they work, and developers can easily add new functionality."

Here at MUSC, the IT Lab is trying to do exactly that. We are trying to use the web as a way to string together tools and make it as easy as possible for the user. Check out the toolbox for some of the attempts. We are just a small group and any ideas to better our tools would be great!

I work at the IT Lab at the medical university in Charleston, South Carolina. My work schedule is very sporadic. One week I may work 50 hours and then next I may work 30. It just depends on what I am doing. My boss is great becuase all he cares about is if we get the job done and if we are happy. I am sure lots of you have similar bosses. Or I hope so. I have not read most of the comments yet. :) Anyway, I say on average I probably work 40 hours a week.

I tend to agree that a lower budget helps popularity in free software. Where I work we have
had plenty of budget cuts and other money problems. Because of these money problems people have looked to open source alternatives. We have come up with many open source solutions to problems for the Univeristy. Without the money problems, and other reasons, people would not have considered using our lab or the solutions we came up with. Departments and people are now using open source software and now realize that free software is just as good, if not better, than other closed source software. They now are armed with cheap solutions to their problems. They also have more options. If an open source solution does not work they can either adapt the code or use closed software. And before they just had to settle for the closed software that they purchased. Anyway, the point is alot more people were I work have opened up to open source solutions/software because of money problems and now realize that not only is it cheap, but open source software, most of the time, is really good software.

I tend to agree that a lower budget helps popularity in free software. Where I work we have
had plenty of budget cuts and other money problems. Because of these money problems people have looked to open source alternatives. We have come up with many open source solutions to problems for the Univeristy. Without the money problems, and other reasons, people would not have considered using our lab or the solutions we came up with. Departments and people are now using open source software and now realize that free software is just as good, if not better, than other closed source software. They now are armed with cheap solutions to their problems. They also have more options. If an open source solution does not work they can either adapt the code or use closed software. And before they just had to settle for the closed software that they purchased. Anyway, the point is alot more people were I work have opened up to open source solutions/software because of money problems and now realize that not only is it cheap, but open source software, most of the time, is really good software.

I tend to agree that a lower budget helps popularity in free software. Where I work we have
had plenty of budget cuts and other money problems. Because of these money problems people have looked to open source alternatives. We have come up with many open source solutions to problems for the Univeristy. Without the money problems, and other reasons, people would not have considered using our lab or the solutions we came up with. Departments and people are now using open source software and now realize that free software is just as good, if not better, than other closed source software. They now are armed with cheap solutions to their problems. They also have more options. If an open source solution does not work they can either adapt the code or use closed software. And before they just had to settle for the closed software that they purchased. Anyway, the point is alot more people were I work have opened up to open source solutions/software because of money problems and now realize that not only is it cheap, but open source software, most of the time, is really good software.

I tend to agree that a lower budget helps popularity in free software. Where I work we have
had plenty of budget cuts and other money problems. Because of these money problems people have looked to open source alternatives. We have come up with many open source solutions to problems for the Univeristy. Without the money problems, and other reasons, people would not have considered using our lab or the solutions we came up with. Departments and people are now using open source software and now realize that free software is just as good, if not better, than other closed source software. They now are armed with cheap solutions to their problems. They also have more options. If an open source solution does not work they can either adapt the code or use closed software. And before they just had to settle for the closed software that they purchased. Anyway, the point is alot more people were I work have opened up to open source solutions/software because of money problems and now realize that not only is it cheap, but open source software, most of the time, is really good software.

Check this cam to find the Iron City. :)

"It must be created by talented software engineers that understand what the customer's needs are."

I disagree. Here at the ITLAB at MUSC we follow a very similar engineering process to XP. You can check it out on our web site. We also produce quality code with a small amount of people and who are not the most talented programmers. Now we are talented, just not the most. :) Anyway, XP programming talks about simple design and short releases. Along with that and following the tools based way that UNIX is built on, we are able to create tools that solve one problem and combining these tools we can solve a big problem or come up with a solution to many problems. Also, the problem about knowing what the user wants is solved with rapid prototyping. I think XP does something similar. Check out Our about page.

"It must be created by talented software engineers that understand what the customer's needs are."

I disagree. Here at the ITLAB at MUSC we follow a very similar engineering process to XP. You can check it out on our web site. We also produce quality code with a small amount of people and who are not the most talented programmers. Now we are talented, just not the most. :) Anyway, XP programming talks about simple design and short releases. Along with that and following the tools based way that UNIX is built on, we are able to create tools that solve one problem and combining these tools we can solve a big problem or come up with a solution to many problems. Also, the problem about knowing what the user wants is solved with rapid prototyping. I think XP does something similar. Check out Our about page.

"It must be created by talented software engineers that understand what the customer's needs are."

I disagree. Here at the ITLAB at MUSC we follow a very similar engineering process to XP. You can check it out on our web site. We also produce quality code with a small amount of people and who are not the most talented programmers. Now we are talented, just not the most. :) Anyway, XP programming talks about simple design and short releases. Along with that and following the tools based way that UNIX is built on, we are able to create tools that solve one problem and combining these tools we can solve a big problem or come up with a solution to many problems. Also, the problem about knowing what the user wants is solved with rapid prototyping. I think XP does something similar. Check out Our about page.

Anything I have to say is allready said here.

this is well beyond the first step.