0
michelous wrote...
there could still be more like pregnant, gender bender, and loliIt's a no go on that last one. Get with the times.
0
BLZebub51 wrote...
michelous wrote...
there could still be more like pregnant, gender bender, and loliIt's a no go on that last one. Get with the times.
then we still need the other 2
gender bender includes cross dressing, body swap, gender change,possession and futa
0
Late for the celebration... finally TAGS, who changed the owner's mind? Anyway, it's the most useful addition I can remember, but...
Why not allow search for multiple tags? Even if the site's back-end does not use an ORM, it trivial to implement it. And while on the subject why there is no advanced search feature?
On the tags themselves, why not implement a voting system, if nothing else it will both distribute the work-load, and give a better (as in more accurate) results. This is also trivial to implement, however chaotic the back-end currently is.
Why not allow search for multiple tags? Even if the site's back-end does not use an ORM, it trivial to implement it. And while on the subject why there is no advanced search feature?
On the tags themselves, why not implement a voting system, if nothing else it will both distribute the work-load, and give a better (as in more accurate) results. This is also trivial to implement, however chaotic the back-end currently is.
0
Malkuth wrote...
Late for the celebration... finally TAGS, who changed the owner's mind? Anyway, it's the most useful addition I can remember, but...Why not allow search for multiple tags? Even if the site's back-end does not use an ORM, it trivial to implement it. And while on the subject why there is no advanced search feature?
On the tags themselves, why not implement a voting system, if nothing else it will both distribute the work-load, and give a better (as in more accurate) results. This is also trivial to implement, however chaotic the back-end currently is.
i am for a voting system on tags as well
some of the current tags are a little stupid
like chikan
0
It is quite easy to implement voting too.
1) create two tables in the DB, tags, and tags2user
1a) tags, has the name of the tag, as PK, and a int, counting the number of votes (you can do this with SQL for speed, or PHP for simplicity/integration, hell even skip the second field altogether for a view).
1b) tags2user, references the tag table PK, and whatever you are using in your user table as PK. The point here is to disallow multiple votes per user. Of course you can skip it if you don't care.
2) On your form to edit tag, put text field (AJAX on tag names would be also easy and helpful) or if your lazy a checklist with the tags you want to allow. When typed or checked, you get the username from the session global, and the tag name typed or checked, and insert the new entry on the tags2user table (if you used SQL count, the votes will get updated automatically). If the tag is new, you grab the exception thrown (or if-else branch) insert the new tag and repeat.
Now if the DB-engine chosen does not support FK, better be extra careful, seeing the site go down for a day each time something gets updated, worries me :p
The reason for this is that first as michelous said some tags and tagging are a bit off, and second anyone can easily contribute, increasing your quality and quantity of tagging. Plus you later do cool things like index results ;)
In between, if you have any programmers they can just write a spider to query other sites, like mugi or ero-db, it's just a little tricky to bypass common failsafes for bots.
1) create two tables in the DB, tags, and tags2user
1a) tags, has the name of the tag, as PK, and a int, counting the number of votes (you can do this with SQL for speed, or PHP for simplicity/integration, hell even skip the second field altogether for a view).
1b) tags2user, references the tag table PK, and whatever you are using in your user table as PK. The point here is to disallow multiple votes per user. Of course you can skip it if you don't care.
2) On your form to edit tag, put text field (AJAX on tag names would be also easy and helpful) or if your lazy a checklist with the tags you want to allow. When typed or checked, you get the username from the session global, and the tag name typed or checked, and insert the new entry on the tags2user table (if you used SQL count, the votes will get updated automatically). If the tag is new, you grab the exception thrown (or if-else branch) insert the new tag and repeat.
Now if the DB-engine chosen does not support FK, better be extra careful, seeing the site go down for a day each time something gets updated, worries me :p
The reason for this is that first as michelous said some tags and tagging are a bit off, and second anyone can easily contribute, increasing your quality and quantity of tagging. Plus you later do cool things like index results ;)
In between, if you have any programmers they can just write a spider to query other sites, like mugi or ero-db, it's just a little tricky to bypass common failsafes for bots.
0
Xil
Norse God of Sawdust
Pretty cool something was implemented this smoothly on this scale...
We are Fakku! If we deem it beneficial to the community that is Fakku, we have the power to do so!
Never forget
We are Fakku! If we deem it beneficial to the community that is Fakku, we have the power to do so!
Never forget
0
Thanks for the manga tags. My life is now so much easier. I just have to go straight to the forced section and I'm good to go!!!!!
