Wikibooks:Simple talk

This is the place to ask questions about the Simple English Wikibooks.

Ask a new question


May I know the stub policy here? Pages with over 1.5k of text are marked as stubs while one liners aren't. Surely that is not the general rule? PmlineditorTalk 14:39, 1 October 2009 (UTC)

Wikibooks:Stubs might have what you're looking for, although it doesn't specifically say how long a page needs to be to not qualify as a stub. Tempodivalse 18:59, 1 October 2009 (UTC)
Anyways, the page is not helpful. I'd say use the general 1.5k rule, so I'm being bold and adding it. PmlineditorTalk 07:55, 2 October 2009 (UTC)

Flood flag

Can we please install the flood flag here? It'll help us in blocking proxies (a thing I can't do now) and doing tedious maintenance work without flooding RC. Pmlineditor  10:00, 10 October 2009 (UTC)

  • Support A useful tool, i think it should be installed on all wikis by default. For those of you who aren't familiar with the flood flag and its functions, see m:Flood flag. Tempodivalse [talk] 13:22, 10 October 2009 (UTC)
  • Support - Would be useful. Maximillion Pegasus 14:17, 10 October 2009 (UTC)
  • Support - Yep. This would be a useful tool. Tiptoety talk 16:48, 10 October 2009 (UTC)
  • Oppose - Project is near to inactive, there is no work on any books.. No need to start blocking proxies if there are no people editthing from it.. No need to hide stuff. Huib talk 22:46, 11 October 2009 (UTC)
  • Support Good plan. GrooveDog 20:13, 12 October 2009 (UTC)
  • SupportJuliancolton | Talk 22:33, 12 October 2009 (UTC)
bugzilla:21121 filed. GrooveDog (talk) 02:17, 13 October 2009 (UTC)
Flood flag has been enabled on the wiki... Pmlineditor  16:01, 18 December 2009 (UTC)


Hiya gang! Recently, on IRC, a suggestion came up about dealing with open proxies on all Simple English WMF projects at the same time. The creation of a adminbot (proxyblocker) that'd block proxies for all sites at the same time. This came up because on simpleWQ today an open proxy vandal (the same one as simpleWP of late) begun an attack there. This proxy had already been blocked on simpleWP for some time. As such, it might be useful to get some discussion going about the need for such a tool, what it would look like, what it would do and what it would not do. Suggestions so far have ranged from a non-admin bot that dumps a list of proxies to block into AN on the projects (or another page) to a bot with the sysop flag that finds the proxies and deals with them. It was also wondered about if this should be a new bot (EhJJ expressed interest in writing it) or an existing bot (IE: en:User:Slakr's bot) Thoughts? fr33kman -s- 00:11, 13 October 2009 (UTC)

Enwp has w:en:User:ProcseeBot, which however is not open source, so we can't take it. Someone could ask it's creator if they'll run it for simplebooks, if this vandal hit SimpleWP and WQ they'll probably be at us at some point. Admins are sufficient right now, Tiptoety will be promoted soon which is a good thing. Right now what we need is bookbuilding, see WB:RB for ways you can contribute. GrooveDog (talk) 00:16, 13 October 2009 (UTC)
I like the idea of a more standardized way of dealing with open proxies. That said, I am weary of admin bots. I feel that the operator must be someone with a great deal of technical understanding, and who is easily reachable if something does wrong. I would only support a block, if the bot was well tested and cleared by the community first (plus have an active operator). Just my two cents. Tiptoety talk 15:53, 13 October 2009 (UTC)
Agree with Tiptoety. That aside, we need someone to fix the proxy blocks TDV made first, editing from registered accounts must be blocked and the blocks should be for 1 year. I can do this, but then, I'll need to flood RC. Pmlineditor  15:54, 13 October 2009 (UTC)
I think that a bot that simply compiles a list of open proxies would be better than an adminbot - i'm generally not comfortable with automated processes being granted sysop status, unless the bot was well-tested first and had a very competent owner. Also, are my open proxy blocks incorrect? Wikibooks:Blocking#Proxies encourages OPs to be blocked indefinitely, so that's what i did. Tempodivalse [talk] 15:59, 13 October 2009 (UTC)
Sorry, TDV, IPs aren't generally indefed. Someone told me about this on #wikimedia-stewards. I think we might reblock them using the sewq methods. Anyways, the guidelines of these projects are outdated. Cheers, Pmlineditor  16:01, 13 October 2009 (UTC)
Okay, I will make sure not to indefblock OPs in the future, sorry about that. I initially wasn't sure how long to block OPs, and the blocking policy said to block indef, so that's what I decided to do. Perhaps Wikibooks:Blocking#Proxies should be updated/clarified to reflect current OP blocking standards. Tempodivalse [talk] 16:20, 13 October 2009 (UTC)
I'm in the process of changing all my IP indef-blocks to one year, as that seems to be the preferred length. Sorry for screwing it up the first time. :-( I'm going to do a little at a time to avoid flooding the rc and #cvn-sw channel. Tempodivalse [talk] 17:47, 13 October 2009 (UTC)

Copying GrooveDog :P

I requested +import on Pmlineditor's talk page, but Griffin directed me here instead. I can see that GrooveDog had the same idea as me :) (or me as him, not sure which). I am working on a rugby union book right now, but would like the import perm so that I can bring en.wikibook pages here, and simplify them. I would most likely start off with basketball, then move on to other sports. I am also MacMed on enwiki. Regards, MacMedtalkstalk 21:23, 15 October 2009 (UTC)

  • Support trusted. Tempodivalse [talk] 21:34, 15 October 2009 (UTC)
  • Support Yeppers. Pmlineditor  08:25, 16 October 2009 (UTC)
  • Support I definitely said yeppers first in my summary. ;) <_> GrooveDog (talk) 12:26, 17 October 2009 (UTC)
    Requested. Pmlineditor  17:49, 21 October 2009 (UTC)
  • Oppose - I don't see the need for a extra importer - Huib talk 17:50, 21 October 2009 (UTC)
This article is issued from Wikibooks. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.