Page MenuHomePhabricator

Create a structured talkpage handler extension consistent with extant user talkpage expectations
Open, Needs TriagePublic


Some sort of content-model structured voting and discussion system.

Threads storing things in json, parsed mostly into wikitext. Custom editpage for dealing with it, plus js for replies and all the fancy crap we're currently missing.

The real problem is how we manage those threads, and how do we do the votes?

Related Objects

Mentioned In

Event Timeline

Isarra created this task.Apr 11 2019, 8:51 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 11 2019, 8:51 PM
Isarra updated the task description. (Show Details)Apr 11 2019, 8:53 PM
Isarra updated the task description. (Show Details)Apr 12 2019, 10:45 PM

And we should call it 'TalkpageHandler'. Because ContentHandler. Duh.

Or 'Unstructured Discussions'. And have it do absolutely nothing but display talkpages totally as usual, but with some extra handling so users don't need to muck up all their threading themselves.

And then when the users yell at us for doing this instead of, say, fixing all the actually broken stuff, well, who cares? It's not like they're paying us. >.>

Isarra added a comment.May 9 2019, 8:20 PM

The main feature is probably voting support. How many kinds of votes do uncyclopedians even do?

Main ones that come to mind:

  • Tables with separate sections, tied to a gadget for actually submitting the vote (VFH, VFP, VFD)
  • Ordered lists with separate for/against sections and a {{s}} 'score' item at the top (VFS, some forum votes)
  • Unstructured/unordered lists with {{for}} and {{against}} together, and a {{s}} 'score' item at the top (other forum votes)

Four things users can do with it:

  • Normal reply
  • Initial comment
  • non-comment section (which can still be replied to or even signed, but isn't inherently treated as a comment, and is also probably not a vote)
  • vote section (also repliable, but with buttons or something for VOTING DUH)

Votes, general threads, and an entire thread block should all be embeddable objects (though maybe that last one just is the content model and we just use MCR to make that fly, I dunno).
Votes and discussion threads need to both be embeddable, inside each other or other votes/threads. Potentially indefinitely. Let's not limit people, here.

Isarra added a project: Epic.

Okay, we are going to do this using slots. It is decided.

Isarra updated the task description. (Show Details)May 17 2019, 3:14 PM


Because you can only have one slot of a type per page!

Isarra updated the task description. (Show Details)May 19 2019, 9:00 AM

Is this primarily for the English Uncyclopedia? It sounds like it (or something like it) could be useful for the proposed Wikimedia talk page improvements, although obviously that project is still in the planning phases.

Note that storing all threads, or all messages of a thread, on a single slot, will make conflict resolution harder, depending on how the edit is handled (2 or more users adding or editing comments of the same thread)