All The Tropes Wiki Project, Part VII

[TvT Rivals]

@Bob: We'd appreciate that. The early time of Tv Tropes is somewhat hidden in the fog of history.

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.

 

A wiki for creators of media where creativity isn't allowed is a kind of contradiction in itself...

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

Glad to hear that. :-)

No really, Munchkin is a terrible game (with a few good jokes buried in it).

We don't comment on that. The Administration of the future troping wiki has to stay neutral.

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.

Peculiar... except for the last point, we'd call this rather a page for "What is the purpose of the wiki?", not "What are the rules of the wiki?"

We'll have to write a page about that too. Some ideas are there, but it's not finished yet. We know that we like troping very much, but if you ask us to nail it down... we disagree among us about that. We'll see.

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?

Other than Tv Tropes, we allow Potholes at the beginning of examples. Does that answer your question?

(Also, we allow strikethrough markup, colored text and bigger font size. And we want to keep it like that.)

Furthermore, other than in PmWiki, our parser can handle markup (like B, I, Strike, Spoiler, Color...) in potholes.

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.

The software doesn't put many restrictions on examples. They have to be shorter than 4 kiB, that's all. And you may add more than one example for a certain trope-work combination.

On a side note, what language are you using for the core wiki code?

Read carefully what we wrote, there's a hint hidden in it.

but on the other hand why are you writing a new app that doesn't target PostgreSQL?

We'll have to see. As long as we are the only ones using the software (we don't plan to sell it), we use our time for other stuff. Other than that, nothing against PostgreSQL. Just wasn't our first choice.

(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?)

Good thing we rarely use that function, then.

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.

The link on top doesn't work. At least right now.

Other than that, we weren't talking about trolls like you or Eris. Rather about the "YOU ALL SUCK" kind of trolls that came later.

Also, you're not really invited yet until you'll get the mail with the 64-letter-and-number code you need for registering. - j/k, you'll get it, just nitpicking.

We have a beta tester BTW who likes to argue on fora very much. Some hairy UNIX admin who likes anime. You'll get along very well.

Did you get our mail with the attachment (the custom titles for pages)?

Other than that, we're off for the weekend. Have to dig deep into the wiki. CU!