User:Yair rand/Wishlist


 * Scripts should be able to store arbitrary data, private and public, both associated to a user's account and not. Gadgets should be able to store preferences that don't disappear when a user switches computers. OnlineStatusBar and Drafts should be gadgetizable. Actually, pretty much everything should be gadgetizable. Keeping things in the hands of the community is a good thing, as is eliminating the need for communities to contact the devs. Live feeding data should also be allowed. Making a edit screen chatbox gadget is not going too far with this. Nor are javascript A/V Wikinews streams gadgets, "This user is actively editing:" boxes, or "Read this page later" user lists/buttons. Though really, I'm primarily thinking about Reference Tooltips preferences, watchlist gadget settings, and Wiktionary's various show/hide (currently cookie-based) settings.
 * All javascript should be community-editable. If the community wants to add something specifically to mediawiki.special.movePage.js, they should be able to do so. If they want to actually change some core js, they should be able to do that too. Same thing with all CSS.
 * All configuration changes should be handled by the community, including namespace changes and usergroups. It frequently takes weeks for bug reports on these things to be dealt with. Involving the devs for these things is unnecessary.
 * Post-wikitext-processing serverside scripts for modifying the HTML output. There shouldn't have to be enormous amount of DOM-modification on-load with JS. The community should be able to set regular expressions to run through the HTML, as well as more complex actions. On certain wikis, heavy DOM work is currently necessary, and it shouldn't be.
 * AbuseFilter should be capable of much more complex operations (think ClueBot NG). It should also be able to do any action any admin can do: protection, editing, etc.
 * It should be possible to upload bots to a wiki. Users shouldn't have to run them on their own computers.
 * Dump analysis should be doable on-wiki. Downloading such enormous files should not be necessary. Nor should knowing whatever programming languages.
 * Real-time feeds of everything should be available. If one can find new stuff be repeatedly refreshing, they should be able to directly access a RT feed. (A few examples: RecentChanges, history pages, watchlists, contribs pages, categories, logs, whatlinkshere, TFAs and equivalents, relevant Wikidata changes...) Use Eventsource, WebSockets, etc.
 * Skins should be community editable, along with the configuration for the default skin. If not the entire skin, then as much as possible.
 * Templates should be virtually all-powerful. They should be able to access all public data (including histories), read the page the template is located on, modify their own arguments on save, perform all user actions (certain ones requiring a user with those rights to approve the template's use of those actions), store and read data, output raw HTML (again, subject to approval by those with user rights), and everything else feasible/not too dangerous. Most/all of this probably done through Lua.