PredictionBook is now read-only ( read more ).

PredictionBook will be modified sometime before January 10, 2012 months to have some form of moderation.

Created by JoshuaZ on 2011-11-17; known on 2012-01-10

  • JoshuaZ estimated 72% on 2011-11-17
  • Jayson Virissimo estimated 60% and said “I really hope so.” on 2011-11-17
  • RobertLumley estimated 75% and said “Me too Jayson. But trolls are a good problem to have, I guess, relative to where things were.” on 2011-11-17
  • Anubhav estimated 60% and said “A few filtering algorithms would work equally well. So would a way to flag posts and block the trolls post-facto. Are we really so short on technical manpower that we have to go with moderation?” on 2011-11-17
  • Anubhav said “Come to think of it, will we have enough moderators to keep up with the traffic? It wouldn’t be a lasting solution. ” on 2011-11-17
  • JoshuaZ said “Well, one obvious mod power would be to be able to fix deadlines. It seems new users often include deadlines in the prediction text but aren’t applying it correctly in the date box. ” on 2011-11-17
  • gwern said “erm, you guys know that I do have mod status right? I can edit prediction titles, due dates, and set public predictions to private” on 2011-11-17
  • JoshuaZ said “Huh. I did not know that. I was considering making a prediction about you getting mod status after such an implementation. In any event, if no one objects I’m going to withdraw this prediction since it is based on bad premises. ” on 2011-11-17
  • RobertLumley said “Yeah, no objection. Personally though, I would like to see some kind of self moderation, like LW has with Karma. Perhaps predictions could be voted up and down…” on 2011-11-17
  • JoshuaZ withdrew the prediction on 2011-11-17
  • shokwave said ““set public predictions to private” and “set public to private, not reversible” seem like enough power to moderate PB” on 2011-11-18
  • Anubhav said “Oh BTW, about the deadlines… it’s PredictionBook’s fault. If I type in, say, 2035, there is absolutely no good reason to interpret that as 20:35. ” on 2011-11-18
  • JoshuaZ said “Is that’s what is causing it? That makes a lot of sense. ” on 2011-11-18
  • shokwave said “the date parser for pbook is ‘Chronic’, http://www.rubyinside.com/chronic-natural-date-parsing-for-ruby-229.html I think it was not designed with 40 years ahead in mind” on 2011-11-18
  • Anubhav said “It’s not the timeframe; even 2012 gets parsed as 20:12. It’s just a stupid design oversight. ” on 2011-11-18