Feedback or requests for help with the site.
May 8th, 2015, 2:13 am
For historical reason that have no rime or reason in this day and age, apache still bans forward slashes (yes i'm talking about properly encoded ones - like %2F) in the url calls.

Try it yourself : http://forum.mobilism.org/search.php?keywords=ohNo%2FdammIdied&submit=Search

Now this would normally be a very minor inconvenience but in the ebook sections not being able to use slash is kind of a drag. Thats because there are not all that many people that are interested in both M/M and M/F stories. Most people has a strong preference for one or the other and would consequently like to either use M/M in their search queries or use -M/M to filter out the stuff they have less interest in.

Possible solutions :
1. make seperate ghetto for M/M (way too much work - scrap that)
2. prevent postings containing / (pretty easy to do - and it make sense that if you cant use that symbol in searches, then it doesnt make much sense to allow people to use it in posts). M/M will become uniformly MM.
3. start your favorite text editor and find that httpd.conf file that has been gathering dust and add the following magical directive :
AllowEncodedSlashes NoDecode
or
AllowEncodedSlashes On

Here is the reference to the directive: http://httpd.apache.org/docs/2.2/mod/core.htmlhttp://httpd.apache.org/docs/2.2/mod/core.html#allowencodedslashes

I hope all my pervert friends and myself will soon be able to avoid seing barely clad <NameTheGengerYouArentAllThatAtractedTooHere> while searching for smut in the ebook section.
May 8th, 2015, 2:13 am