Talk:Flow/Architecture/API/Archive 2014

enwiki bots that edit talk pages
I did a database query to find all bots that edited a talk page on enwiki in the last 30 days. I excluded archive bots, signature bots, and anything else that would be unnecessary with or unaffected by Flow.


 * Notifications (adding new sections)
 * BracketBot, Legobot, HasteurBot, Theo's Little Bot, ImageTaggingBot, DYKUpdateBot, RMCD bot, DPL bot, SuggestBot, Cyberbot II (also comments on the sections it creates), Cyberbot I, HostBot, DYKHousekeepingBot, EarwigBot, UcuchaBot, LaraBot, ReferenceBot, MadmanBot, Commons fair use upload bot


 * Cleanup (editing comments):
 * AnomieBOT, OgreBot


 * Editing page header (Wikiproject banners, etc)
 * ProteinBoxBot, DYKUpdateBot, VoxelBot, DumbBOT, Cyberbot I, Lowercase sigmabot, MenoBot II, AnkitAWB, SporkBot, MenoBot


 * Other:
 * JL-Bot

So except for a handful, the vast majority of bots fall into 2 categories. This also shows that there are some limited use cases to allowing bots to edit other peoples' posts. Mr.Z-man (talk) 02:19, 5 February 2014 (UTC)

Notes from Zurich Hackathon
From the Flow API session:


 * Mobile apps will in future talk to Flow over the API!
 * We need HTML of posts, but without UI cruft -- we need pure data for that stuff. This should be coming as I understand.
 * Fancy wiki features in posts -- extensions, videos, etc?
 * Currently there are two problems:
 * Parsoid doesn't handle all extensions
 * we don't know which JS modules are needed to trigger things
 * Possible ways around this: add a lightweight JS or server-side DOM postprocess that detects semantic HTML5 patterns for extensions and feeds back the JS modules you need
 * Note that the page header is not a plain wiki page like in LQT, it's another Flow object.
 * (maybe ContentHandler could make it act like that though, if that's useful for people)