All The Tropes Wiki Project, Part VII

[Labster]

Content Creation WikiContent Classification Wiki
You need to read the classics to understand culture, and wikis are no different.  The key here is whether or not there's space to experiment or create.

PTerry

Shibboleth accepted. Your status is now "one of us".

Once had some [ fanfic ] published on the internet, but rather consider them Old Shame now.

To those of you who haven't written (or programmed): this is what creation is like.  Even God had to flood the whole place and start over.

Also have experience with ... Munchkin

I'm so sorry.  Accept my condolences.  No really, Munchkin is a terrible game (with a few good jokes buried in it).

Our sexes: Male (No girls on the internet? Yeah, sometimes it is true.).
Sometimes feeling a little that being a lesbian might be cool.

...

No replies at all? Ok, we guess you're still busy pondering about what we wrote yesterday.

...

Leaving that aside, we were quite happy with the old Troping Code.

I was actually going to ask your opinion on this yesterday, but how do you feel about my version of The Tropers' Code?  Note that it is actually policy on ATT, and a recognition that things are a really matter of degrees.  And admins have been known to reverse other admins decisions, and we all get along.  It's quite lovely.

We understand the point of FoRKS and would like to bring to old
experience back. Maybe something like "FoRKS Friday"? Each Friday, the
titles of some renamed pages are changed back to their old names for a
day. A cron job on the server should suffice for this.

Heh amusing.  More to the point, how would you handle the distinction between pages like "The Hero" and "The Heroine" where one doesn't necessarily mean the other?  Would it be possible to use "Nakama" on an Anime page and "True Companions" on a Literature page?

You don't like e.g. Radio series? Switch the filter for Radio to "No",
and the software won't display any pages or examples from radio series
anymore.

I hope you're not using radio buttons to do this   I think this is a good demonstration of the type of power that comes with a well structured system.  I truly see a lot of advantages to doing so.  The problem is that you will lose expressiveness in exchange for this power.  Questions like the one in the block above are really trying to get at the heart of how much you have done to preserve expressiveness while increasing clarity and power.  This question is one I think about a lot as Perl programmer.
On a side note, what language are you using for the core wiki code?  I assume you're using MariaDB on the backend because you mentioned Monty, but on the other hand why are you writing a new app that doesn't target PostgreSQL?  I say this as someone who uses MariaDB and Percona daily for hysterical raisins historical reasons.  (Fun fact: did you know that MySQL REGEXP only knows about byte-sized characters, despite the fact that people have been complaining about lack of Unicode support here since 2004?)

This also means: If some new troper really creates havoc, we can also
tell which troper is responsible for inviting such a
tool/troll/spammer/whatever.

You can only blame yourselves for inviting me.  I am a troll par excellence.  Here is me trolling philosophers about the nature of trolling and still being the top-ranked reply.
-- ∇×V