User talk:Kylu

Ideas to chuck at various developers

 * 1) Removal of an article name from logs. For instance, if a vandal creates Jimbo Wales Home Phone is 555-555-5555 and the article is deleted, at the moment we have to contact a developer to remove the entry from logs.
 * 2) Likewise, User:Brion Lives at 1234 Mockingbird Street, even renamed, is a problem. (Shows up in the bureaucrat rename log)
 * 3) An ability to blacklist names (usernames, pagenames, edit summaries) by regex could really come in handy. Perhaps there's something in the MediaWiki: space, or could be? Kylu 19:18, 3 November 2006 (UTC)

Hi Kylu, you may have a look at these ideas. Regards -- :Bdk: 10:48, 4 November 2006 (UTC)


 * I'm already familiar with this (ran across it on Brion's page) and with the current incarnation of oversight. The catch is, rev deleted and oversight only work with edit revisions, not log entries.
 * Here's an example: A vandal makes an article, Jimbo Wales Home Phone is 555-555-5555 and I, as a Wikipedia admin, delete it: The article is gone, sure, but with a title like that, the information still hangs around in the deletion log. Oversight affects revisions, not log entries, so there's no way to hide that title without annoying our overworked Developer staff. This can be done with nearly any page title, including userpages linked to in the username list. I won't mention my WP:BEANS related ideas here.
 * I'm a bit curious how Wikimedia would handle these sorts of permissions: They're more sensitive than oversight (somewhat) and yet it'd make sense to the enduser if they were combined into one function. Like many other things, it's mostly going to boil down to who you trust. Kylu 01:57, 6 November 2006 (UTC)

More ideas

 * Add checkboxes next to usernames in checkuser, plus one "master" reason and duration field, to block multiple abusive sockpuppets at once.
 * Add "checkuser lite" to allow for people to retrieve autoblock #'s instead of IPs to perform blocks without endangering IP privacy needlessly.
 * Possibly, "Antibureaucrat" (or maybe "PHB"?): a method (besides stewardship) for desysopping, but not sysopping or debureaucratting. Just a silly separation-of-powers concept, that one.

Kylu 02:43, 13 November 2006 (UTC)
 * Note that the desysop extension is already on svn. Voice of All 05:21, 17 November 2006 (UTC)
 * See how good an idea it was? So good they got right to work and implemented it! Kylu 05:37, 17 November 2006 (UTC)
 * Can you explain your autoblock thingy? It might be interesting to write a tool to show the IPs of autoblockees for checkusers at Special:Ipblocklist, perhaps links there can be added to a Special:CheckAutoblock to pull the IP of an autoblock. I'add add it checkuser directly, but users might happen to have names like #45454.Voice of All 05:52, 17 November 2006 (UTC)


 * Okay:
 * Kylu performs checkuser on VoiceOfAll
 * Instead of returning 10.20.30.40 as your IP, it returns an autoblock # (it returns #12345, for instance)
 * I can perform a checkuser on #12345 and see that VoiceOfAll is in actuality ... Willy on Wheels!
 * Voila: Checkuser evidence without needing to expose someone's IP addy.
 * I can then block #12345 if need be.
 * CON: Nearly impossible to perform rangeblocks this way.
 * CON: No way to determine if a block based on this would include collateral damage (from blocking an AOL IP, for instance)
 * IDEA: Allow checkusers to pop in an autoblock # and have it return User/IP.
 * Hope that helps! Kylu 06:01, 17 November 2006 (UTC)
 * Hrm. I don't see any need to bog down checkuser any futher, as it already slow and tedious to read. The idea of being able to pull IPs for #autoblocks is nice though. I ought to write that.Voice of All 06:06, 17 November 2006 (UTC)
 * See User:Voice_of_All/CheckUser2.0. Any suggestions are welcomed.Voice of All 18:26, 2 December 2006 (UTC)

Semirelated to CU2.0
How hard would it be to change the IP pagenotice (the one with the WHOIS links at the bottom, I'm too lazy to look up the MediaWiki: page we use) to provide a note for "This IP is static", "This IP is dynamic" or "This IP is of unknown permenancy" (or similar message)? Kylu 03:31, 29 June 2007 (UTC)

Interwiki concept
Let's say we've got an article... oh, Wikipedia. Every language version of Wikipedia has this article, either translated, untranslated, or somewhat-in-the-translation-progress.

I want to add the Sinhala article on Wikipedia (Wikipedia) to the site and interwiki it:
 * 1) Create the article,
 * 2) Go to, say, enwiki and copy the interwiki list, by hand, add the en interwiki to the list, and dump it on Siwiki's article, then,
 * 3) go to every other single copy of Wikipedia and add the interwiki links by hand

This sucks.

Now, step 2 can be mostly automated, and step 3 can be completely automated using bots.

This also sucks.

So, my idea is you have an "interwiki server" that uses linked lists: If I add Wikipedia to the siwiki article, the software sees the link, adds it to the linked list, and adds the update to the linked list to the job queue at some later time.

Later on, when the job is started, it looks at the linked list and updates the interwiki links on all the articles marked as updated.

Possible problems:
 * 1) People who don't know how to use interwiki links (say, on a sig that points to another wiki?) and end up with User_talk:Anthere linked to xx:User:Newbie
 * 2) *Possible solution: Don't let cross-namespace interwiki links exist. Either automagically fix the broken interwiki link, or, better yet, put up a giant error message box at the top of the screen, which the user must read and check the "yes I really want to do this" and possibly enter letters into a CAPTCHA to continue.

Questions:
 * 1) Will this use up more or less processing power than the currently running interwiki linking bots?

Opine. Kylu 08:49, 11 August 2007 (UTC)