DemonGoddess

added

nukie nukie

I'm going to clarify the thing with the particular user that was the "straw that broke the camel's back" for Apollo. She signed up for the site when she was sixteen. Yes, I said sixteen. She turned 18 in 2009. Yes, I processed her for old minor content and what not in late 2011. Sometimes it takes awhile to catch 'em when they lie you know. But here's the thing. It may take, in some for instances, a couple years to catch 'em. Point is, I don't really give a shit WHEN we catch 'em, caught is caught. That means, you signed up here before you turned 18, YOU WILL LOSE THAT DATA. Don't complain. Don't ask me to restore it. I can't anyway once I delete it. Even if I could, I wouldn't, as the data was posted when you were underage. The archive is run on a database. The database record, once it's removed, is gone for good. I'll use an example of what you little brats are potentially doing to the actual adults who both run and visit the site. If you were to approach any one at a convenience store, and were under 18, wanting to buy adult materials, you would be carded. If you were not yet 18, it wouldn't be sold to you, as it's ILLEGAL. Not only that, if the clerk went ahead and did it anyway, he or she would face some stiff fines for a first offense, and offenses thereafter the fines would increase, and that person could face jail time as well. This applies to ANY AGE CONTROLLED ITEM. Whether magazines, tobacco, or alcohol. There are splash pages saying you must be 18, there are labels all over the damn site, saying it's RESTRICTED TO ADULTS. That doesn't mean when you feel you are one, but when you are actually 18 years old or older. Yes, these restrictions also apply to adult content on the internet. You entitled asshats who think it does not, are sadly mistaken. You bet I'm calling names at the moment. Understand this DOES NOT APPLY to the bulk of our users. Just the few spoiled brats who make it difficult on the rest of us, whether staff or members. Coding Issues You bet we're aware of them. You bet that with the old stuff, everything that can be done to it without breaking it, has been. There are some things I'd LOVE to do with the old code that are simply not possible. I try it, it'll break. It breaks, we have no archive. This is why we are paying for new code. Enough of you were around for the big crash in 2005, to realize that there are still many, many stories that are in need of repair. Don't try and push me to get it done faster. There's only so much I can do in a day. As a large chunk of this is being done direct in the database itself, one should be able to see why for that, I don't give access to everyone to do that. I've been working with databases for many years, and if it gets screwed up, we have no archive, so no, I won't be granting direct access to anyone either. It'll just have to take time. Mod stuff We found out about 8/20 of last year, that a utility I use to delete underage users wasn't functioning correctly. For the last 2 weeks, I've been chasing down and deleting the rest of the underage content. It's unfortunate that it's made for several thousand reviews to be deleted, but you're looking at 3 1/2 years of data I had to (and am still going through) go through, to be sure I got all the underage content OUT of the archive. The good thing is, it's a one time thing, and it won't be happening again once I have it done. My alternative to this would've been to empty the tables for all reviews, and have everyone start fresh. That would've been unfair to all of you. Much quicker and easier for me, yes; but not fair to the users, so it was never an option I would have honestly considered. There are some rules that people gripe about, like the restriction on the AN in chapter, and no AN chapters. Most of you paid attention when I said it was for database stability. You're not the ones that gripe. This database is ten years old and 8GB in size. There are things that I insist on from a database management standpoint, to keep the thing stable. If it's not stable, we have no archive, as the database will crash. I've always announced when something like this was necessary. That people won't read when something like that is announced, quite honestly, is not my issue. It's yours for not reading. Don't try to make it my issue either. Pay attention when announcements are made.

There's nothing I can say to make this any easier on you Melrick. I know how hard it was on my husband and his brothers when his dad was diagnosed with this same thing a few years back. All I can tell you is to make the most of the time you have. It does help later.

Another group this would apply to, if you think about it, are spouses of police officers, and fire fighters. Imagine the kind of stress that is. My uncle is a retired cop. His wife had to deal with daily "oh gee, my husband may never come home from work because he may die". Did she run? Nope.

When you get involved long term, that means you stick around for the bad as well as the good. Severe illness, to me, is not a reason to leave.

The other likelihood is if that you see the author's profile, but not the story, is that they posted the story here before they turned 18. Sorry, I can't leave those.

added

not until I get there for the repair part. What you're seeing there is the result of the database crash and then the addition of the rte. The db crash scrambled some of the html, and when the rte stripped that html, it just became more obvious what the issue in the record is.

The issue they had with admin was refusal to follow ToS. So rather than correct whatever the issue was for their story a few years ago, they deleted it.

You know, there are many reasons that an author will put a story on hiatus. The most common is that they simply no longer have the inspiration to continue with that particular story line. They may have to step away from their writing due to RL getting very busy. No need to get testy at 'em when things like this happen. It's certainly not like they do this to punish you... As to Weapons of Mass Destruction, the author pulled it rather than correct some new ToS violations within the story.

If it's no longer on the site, she would've pulled it for publishing. Look at her profile, she leaves notes about that sort of thing in it.

The author who published it plagiarized someone, so all of his/her other content and profile was deleted; including this story.

Old Minors By old minors, what I'm referring to, are users who were minors at time of registration, are now adults, and registered BEFORE 12/31/08. We were finding so many, that I decided to "grandfather" in those accounts, and simply delete all data pre the user's 18th birthday. I do make exception to this, in that if we find old minors who are inactive for a number of years, we delete them anyway. As well as old minors who registered underage, never posted anything, and have been inactive. 2008 process year 2003 registration year 3 accounts processed, 2 users deleted, 1 users modified, total of 3 actual users 2004 registration year 2 accounts processed, 2 users deleted, 0 users modified, total of 2 actual users 2005 registration year 1 account processed, 0 users deleted, 1 users modified, total of 1 actual user 2006 registration year 5 accounts processed, 3 users deleted, 2 users modified, total of 5 actual users 2007 registration year 2 accounts processed, 1 user deleted, 1 users modified, total of 2 actual users 2009 process year 2002 registration year 1 account processed, 0 users deleted, 1 users modified, total of 1 actual user 2004 registration year 7 accounts processed, 1 users deleted, 6 users modified, total of 7 actual users 2005 registration year 8 accounts processed, 0 users deleted, 6 users modified, total of 6 actual users 2006 registration year 12 accounts processed, 0 users deleted, 12 users modified, total of 12 actual users 2007 registration year 7 accounts processed, 0 users deleted, 7 users modified, total of 7 actual users 2008 registration year 5 accounts processed, 1 user deleted, 4 users modified, total of 5 actual users 2010 process year 2003 registration year 15 accounts processed, 4 users deleted, 8 users modified, total of 12 actual users 2004 registration year 24 accounts processed, 7 users deleted, 16 users modified, total of 23 actual users 2005 registration year 28 accounts processed, 6 users deleted, 22 users modified, total of 28 actual users 2006 registration year 34 accounts processed, 6 users deleted, 28 users modified, total of 34 actual users 2007 registration year 36 accounts processed, 9 users deleted, 25 users modified, total of 34 actual users 2008 registration year 12 accounts processed, 6 users deleted, 6 users modified, total of 12 actual users 2011 process year 2002 registration year 18 accounts processed, 9 users deleted, 9 users modified, total of 18 actual users 2003 registration year 168 accounts processed, 87 users deleted, 55 users modified, total of 142 actual users 2004 registration year 326 accounts processed, 190 users deleted, 86 users modified, total of 276 actual users 2005 registration year 604 accounts processed, 361 users deleted, 124 users modified, total of 485 actual users 2006 registration year 477 accounts processed, 290 users deleted, 73 users modified, total of 363 actual users 2007 registration year 632 accounts processed, 428 users deleted, 68 users modified, total of 496 actual users 2008 registration year 286 accounts processed, 211 users deleted, 36 users modified, total of 247 actual users

I didn't find out about this until late last night, and what it would take to MAKE AFF go dark would take a fair bit of time this end. 24 subdomains, 24 pages written to redirect to a "dark" page. Since I don't get home until the afternoon, there's really no point in doing it at that time for a few hours. Or I would've....

thankee Cal

the particular function you're talking about is an ajax function. Ajax being extended java, blocking java would indeed halt it. It'll stop other things too, aside from the shoutbox. When you see the image thing in a post, what happens is the user is given the option in the upper right corner to go to the next image, if there is one. It also displays the image in its true size, usually; not the thumbnail you see in the post.

I fixed it. The problem was, after one line break, you had a series of spaces, indicated by the html symbols for it. As they were consecutive with no break, that's what caused the stretching. I removed them, and the chapter now is displaying correctly.

All rightclick does for me is open up a menu allowing me to open something in a new tab, or inspect the element. If you're in an image heavy topic, and you want to see the images full size, you will have to right click after load. To close it, if you don't see the 'x', simply press 'esc'. Mind you, without knowing which topic you're referencing to begin with, I can't even duplicate what you're saying is happening.

Inconclusive results These are individual accounts we've previously checked, and still not made an age determination. The year listing is what is left marked this way. 2008 - 9 users 2009 - 103 users 2010 - 164 users 2011 - 196 users Confirmed as 18 or older These are individual accounts we've previously checked, where we've confirmed the user is 18 years old or older at time of registration. 2008 - 52 users 2009 - 120 users 2010 - 227 users 2011 - 158 users Minors that have been deleted and are still underage We monitor these for return. The listing will be by year deleted. The variance between number of accounts and actual users, is due to many of them creating multiple profiles. 2008 - 11 accounts, 11 actual users 2009 - 15 accounts, 13 actual users 2010 - 78 accounts, 71 actual users 2011 - 490 accounts, 412 actual users Users posting for/with minors This is how many instances handled, by year found. 2009 - 2 2010 - 11 2011 - 9

Don't even bother, I nuke 'em as fast as I can.

You edit warnings by adding it to the end of the summary field, in story properties. So you want to choose "edit story details".

All tv based fiction (except BtVS and AtS) is posted here. If you don't see your category, post to misc. To request a category, go here.

FAQ exists