Surprisingly, having the two sets of titles would be theoretically possible. Since the software will support multiple different sets of composers and decomposers between wikicode and HTML, it could just theoretically convert to a x-wiki/tropes-forks to x-wiki/tropes-knives format on the fly (or whatever the heck those groups called themselves). And alternate names could be saved in page metadata. However, I don't think it would actually solve anything, other than institutionalize divisions between people.
I'm used to software where deleted pages show up with a big red indicator next to them on Recent Changes. But if people aren't watching, there are circumstances where pages could fall through unnoticed. Huh. Let me think about that some more.
I was wondering when someone would bug me about the markup. There's a reason I said it's a draft. I wasn't going for a "fuck you" to users of the old wiki. It was more of a "Hey, I just freed up curly brackets. Should I use them for anything?" moment.
Spoiler coding is actually a fairly hard thing to do right, because it has three competing interests: It's common so it should be short; it should be easy to remember, because it's common; and it should be easy to identify, because people don't always want to read the contents while editing. In the last, [[spoiler:] wins hands down, because it's so big and obviously says spoiler. But it's cumbersome for something that is so common. Evan suggested ((double parenthesis)), because it's like a parenthetical comment that's less important to see, but I think that fails the "obviously a spoiler" test. So I proposed with double curly brackets. Would you feel better with {{{triple curly brackets}}}? Is there another alternative that feels better to you?
-- ∇×V
I'm used to software where deleted pages show up with a big red indicator next to them on Recent Changes. But if people aren't watching, there are circumstances where pages could fall through unnoticed. Huh. Let me think about that some more.
I was wondering when someone would bug me about the markup. There's a reason I said it's a draft. I wasn't going for a "fuck you" to users of the old wiki. It was more of a "Hey, I just freed up curly brackets. Should I use them for anything?" moment.
Spoiler coding is actually a fairly hard thing to do right, because it has three competing interests: It's common so it should be short; it should be easy to remember, because it's common; and it should be easy to identify, because people don't always want to read the contents while editing. In the last, [[spoiler:] wins hands down, because it's so big and obviously says spoiler. But it's cumbersome for something that is so common. Evan suggested ((double parenthesis)), because it's like a parenthetical comment that's less important to see, but I think that fails the "obviously a spoiler" test. So I proposed with double curly brackets. Would you feel better with {{{triple curly brackets}}}? Is there another alternative that feels better to you?
-- ∇×V