OSHA Launching Porn HIV Investigation
Jun 11, 2009 Gay Porn News
Earlier today I reported about a possible HIV problem in porn valley.
Now, through XBIZ, the California Division of Occupational Safety and Health has announced that they are launching an investigation into the positive HIV test.
California OSHA also said that they will be aided by the Los Angeles County Health Department.
Although the article did not go into detail as to why an investigation is being launched, I would imagine that it has to do with the handling of the HIV positive result by AIM, a non-profit organization that provides HIV testing for the porn industry.
AIM has not announced who the model was that tested positive. They do say that a handful of porn models have been quarantined. As one may imagine, this action by AIM has caused a lot of controversy. Porn producers and models alike really have no idea what is going on.
As I understand it, while the average person has privacy afforded to them when testing positive, the porn industry works a little differently.
The release that is signed before testing pretty much says that the model gives up their right to privacy if they test positive. That way, their name can be announced and producers and models alike will be able to ascertain if they are possibly at risk.
There is a very good reason for this — porn stars sleep with A LOT of people as part of their job. Some sleep with a dozen or more people a week. It would be very easy for them to forget someone when they have to name who were exposed.
It should be noted that so far nothing points to a possible problem in gay porn. The rumor is that a 42 year old MILF was the person to test positive. Then again these days there are so many straight porn stars crossing into gay and vice versa that there may very well be a risk. Nobody knows, which is why there is so much outrage directed towards AIM.
New Porn Industry HIV Breakout?
Jun 11, 2009 Gay Porn Gossip, Gay Porn News
(Note: So far, this appears to be limited to straight porn)
There was an interesting thread on GoFuckYourself.com (GFY) yesterday that immediately got my attention:
Warning Porn Valley is About to Have Another HIV Outbreak
A lot of people, including porn producers, tried to dismiss the claims made by the original poster.
The original poster refused to back down from their comments and asked to be banned for life from GFY if they were indeed wrong.
One of the people challenging this person statements said that they had called AIM (the organization that tests porn models) and were told that nobody had tested positive for HIV.
Fast forward to later in the day and a news release appears on AVN. This release says that indeed, a female actor tested positive. The release went on to say that there was no threat to the industry. There have not been any requests to shut down porn sets like there was in 2004.
There has been speculation about whether AIM is trying to cover their tracks by not being more forthcoming. That speculation can be seen in the original porn HIV thread (also the first link in this tread).
Right now there are a few other threads on GFY about this subject:
Handful of Performers Quarantined After Positive HIV Test
New Industry HIV Case Already Under AIM’s Control
So what do you think? Is this going to end up being a big deal (and possibly a game changer) for the porn industry, or is it just an isolated incident that is being well managed?
Tags: BlogDesk
Technical Problems Have Been Resolved
Jun 2, 2009 PoppinGossip News
Yesterday, the two most popular sites in our network, QueerLust.com and PoppinGossip.com, began experiencing technical problems.
We originally messed around with some settings, broke something, thought we fixed it and only today realized it wasn’t fully fixed.
The issues have been fully resolved and we apologize for any inconvenience it may have caused you.
What happened:
We modified the .htaccess files, which are security files that tells browsers and bots what they can and cannot do, and it broke permalinks, which are the long page names you see in your URL box. Both sites continued to load at all times. However, if a visitor clicked anything and tried to go deeper into the site, they received a 404 page not found error. Another modification to .htaccess, which was done a little earlier today, corrected this error.
