DemonGoddess

uhhhh no, I believe it's back visible again.

It seems that many of you don't understand the need for not having those posts within the archive right now. It's simple, really. Understand that the scripted programs which run the archive are archaic and out of date. That being the case, they do not handle data inserts in an efficient manner. For example, a forum post has a file size in the database that is very small, in bytes. Whereas a chapter insert within the archive STARTS at 300k, and grows exponentially depending upon how many words, spaces and etc that there are in the one page. So that's reason number one, database load. As the forum is better suited for handling posting data, the forum is where they were all shifted to. I made it so it was easy, in that there are subforums set up to correspond with the 21 subdomains across the site. No login is required to read, post, or whatever in those forums. Aside from that, there's also the advantage of if one has an answer to a search question, the links work. Second would be the search engine that doesn't like to work in the first place, as it's not meant to work for a database the size of this one. We are working on that, most likely for the software being written, not the current. All those non fics then impact bringing up stories in the search even more than already happens. We HAVE a search engine which is capable of handling the data load, however, the archive itself really cannot support much more in the way of script changes, including porting in that engine. We do too much more tinkering, and the thing will crash. Now, to address that, we've been reorganizing the entire site, to make it easier to see what you're looking for at a glance. Unfortunately, there are only 3 levels of categories to work within currently, and only TWO are able to be posted to. So, there are some other things that can be done in the single fandom subdomains, which will be done, to try and make it easier to locate stories visually. Can't do those things that will be done in the multiple fandom subdomains though, because of the three levels available to me. This is another of those things which will be addressed in the software in development. Some of the changes you will see will be- A robust search engine, which will allow more than 100 returns on a search, as well as being able to search the tables for data requested without causing a "too many open connections" error. (Something that would happen with the current software were we to port in the engine now). UNLIMITED sublevel ability This is where the sorting and cataloguing comes in. Because we will have that ability, one will be able to have several levels of category placement, and choices for it. Ultimately, this will make it an easier archive to search. Mail reply to reviews (posted by logged in users), using the phpmail function, which will mask the sender's and the reciever's address. Very similar to how the forum handles email between users. Selectable user skins, and portal skins with a much smaller footprint. RTF editor built in. This will eliminate the need for uploading files, and hard coding in formattting. One will be able to format text on the fly, within the text editor window. Faster code execution, as the program scripts will be written in the newest version of php, and compatible to the newest version mySQL, backwards compatible to versions 4.x of each program. Spambot protection Drop down disclaimer option, as well as a default autofill (the autofill would very likely only be in single fandom subdomains, as well as in originals) There are many more improvements as well as just overall changes that will be done with the new software. I've been asked many, many times why we don't use some of the pre-exisiting fiction software that's available for download. Quite simply, we experimented a bit with a few (offsite), but the database is too BIG for them. In order to KEEP our current database, that makes it so this is not a viable option. After all, why use a program that the database itself, due to its size, will end up crashing? Not to mention the data loss that would follow such a crash. To us, that simply was not an acceptable option. We're also considering possibly making a queue for the users, for their review boards, where the user can select what reviews will show up. Don't know for sure on that one, was just an idea I threw out there. Reason being, that should a user get flamed, the flame can be deleted before it's ever seen. Anyway, thanks again for bearing with us as we prep the archive for the new software.

The three most common page draw errors we encounter are stretched and squished (it only draws on about 1/2 the text area) chapters. Last one would be no chapter data past a certain point. Stretched pages What causes this- The user opts to use characters as a line break. i.e. *****, or ~*~, etc. What happens then, is that the script sees those lines as a single character, so DRAWS it that way. How to correct it- LIMIT the number of characters to no more than 72 on a line. Squished pages What causes this- Improper html formatting when uploading an html file. This is most common when using a Word generated html file. Word adds many, many unnecessary tags, which the archive DOES NOT allow. How to correct it- Open the file in a plain text editor, and remove all the illegal html tags. Copy/paste the correction over the old chapter data. Missing chapter data What causes this- Improper html formatting when uploading an html file. This is most common when using a Word generated html file. Word adds many, many unnecessary tags, which the archive DOES NOT allow. How to correct it- Open the file in a plain text editor, and remove all the illegal html tags. Copy/paste the correction over the old chapter data. For more information on allowable HTML tags, please see this FAQ.

Due to the age of the script, and the fact that spambots can crawl the archive in its current state and GET the email addresses displayed in profile, it's not an option. If one decides to display their email address in a different part of their profile, that is the only way to do it currently. However, it's not something we recommend that you do.

I don't handle the sponsor/adverts stuff, so I can't say that I've honestly looked at the site in depth. Again, one of those things that me, I wouldn't necessarily encourage rape fic in fandom. Not my cup of tea. Having said that, my personal feelings and opinions on certain subjects are not what dictates what is allowable as far as specific content. That is as it should be. Were the archive to be set up according to my own personal tastes and likes/dislikes, I'd say more than half of what's here wouldn't be. But that would be based on my own personal opinions on subject matter. Which wouldn't be in keeping with what is actually allowable. I'd say it's a good thing then I'm just a mod and forum geek

Okay, what I'm going to do about the fairy tales is the following.... Create a top level in books called "Fairy Tales, Legends, and Folklore" As second levels, I will have Fairy Tales, then Legends, then Folklore third level will be the specific sub categories, i.e. Little Red Riding Hood, The Little Mermaid, and etc. I really, really will be very happy when we are no longer limited to 3 levels ONLY of categories. It really cramps what can be done, especially in the multiple fandom sub domains.

this is a good thing, yes?

They're actually a sponsor, and it's a worthy cause. Has not a THING to do with fan fiction. Other than that, personally, I think you all should be able to write about whatever, because the point is to encourage creativity. Not squelch it.

You're welcome. That was me. One of the writers I'd reviewed had pointed out that my review to explain what was needed was a bit confusing (just goes to show ya I am SO not a writer). So I adjusted it and made it simpler. Hopefully that will cut down on future confusion where I leave that message to users.

Did you try friending her on her LJ community? I believe she went "friends only" there. That's the only place I know of where the fic IS.

in misc anime, belongs in bleach

We are STILL getting caught up from when I was sick for over a week. There are only a few of us who actually actively moderate the archive, and even less who have the ability to delete and other such things. So, please be patient, all of this will be handled as soon as is humanly possible. Again, very sorry for the delays in addressing these problems.

*sighs* Well, one would THINK after deleting challenge after challenge from the same people, they might just get the idea that those don't belong in the archive, yes?

uhhhh no, haven't touched your story. Just leaving a review isn't going to make it get all wonky. This is a list of stories that have to BE fixed yet.

Ran into a bit more of a snag than I anticipated . There are files I need to change, in order to do the upgrade in the first place so we don't end up with the "white screen of death". Unfortunately, the hosting company has the files inaccessible to me, so I have to get with one of their techs to do what I need, so I can do this upgrade. Which is, though minor, rather an important one, as it has a whole new schema for handling spambots, which is much better than what was there. The good thing about the inaccessibility I've mentioned, is that it's a strong protection for the domain. After all, if I can't get into it with direct domain wide file access, it makes it that much harder for a hacker to as well.

I would expect it was likely hidden for improper format of the disclaimer, and/or the disclaimer itself not meeting site requirement. The other thing it could be is that the author him or herself deleted it rather than correct the problem. Or, the author just flat out deleted it.

ALL searches and challenges are deleted from the archive. PERIOD. If you ever read site news, and/or TOS, you would know this. There are forums set up here specifically FOR search and challenge stuff. So, you can either continue to post challenges, have them deleted, and ultimately yourself tagged as a spammer and deleted, or abide by what we require

I need to see the links to 'em pls..

Can't say that I don't agree with you, because I do. While we figure out a way to rework the current software to allow us to have more control of things (without it crashing from the modification), like who can and cannot access the thing in the first place, we gotta put up with this, unfortunately.

I'd say under normal circumstances, no the vidcard wouldn't fry from a virus. What kind of vidcard are you talking about? It may need a cooling fan on it.

Okay, should get this all caught up tomorrow or the next day, as I'm off work those two days. @branewurms- I'm actually going to do a reworking of the books archive (again) as there are already fairy tale subcategories, so I'll put them all in one place. That'll take a bit of time, but I will get to it. Hopefully this week. @Lixi-Des- your add will be easy, I'll get to it probably tomorrow @Kleptomaniac Can Opener- There is already an entire Yugioh subdomain @Palmbi- The requirement for adding any subcategories, is that one has stories ready for it, for uploading. @LemonDrop- Naruto HAS a het subcategory. If you're asking for a pair specific sub sub, the requirement for that is 10 or more stories for the pair, in order for it to be added. @Kristina Dalton- The anime subdomain has Hellsing as a top level category.

in anime link the first.... link the second..

in tv- belongs in ne-German http://tv.adult-fanfiction.org/story.php?no=600094102

You getting any kind of weird illegal function memory calls, where it calls to a program you don't recognize? That's what I was seeing, as well as general hardware performance problems. It took about 30 hours, but the scan finally finished yesterday on my machine . 30 hours to do over 260GB of data isn't too awful bad, but jeez.... In the process, the program I linked to found 3 trojans resident in the RAM, 1 that found its way into the vidRAM, and 15 on my drive itself (plus lotta adware and malware that wasn't quite viruses). My other program was just not finding those nasties. At least my machine is no longer lagging, and doing weird things with the vid anymore , now that the scan is finished.

We're actually trying to port in a better solution for all of us, pre software rewrite/upgrade. The problem we've been encountering is the age of the script itself, so we have to be very very careful so that whatever new tools we make for this old software, doesn't make the rest of it not work right.