In T161939#3223566, @Petrb wrote:

btw running telnet to bot and executing "send PRIVMSG chanserv: whatever command you wanted to execute" would probably work in this case

Wait, what? When did "we" decide that?

This shouldn't be dependent on VE. I've been mostly away and out of the loop. I'd still be interested in working on this.

I'm very interested in making a list from [[Special:WantedCategories]] right now... Any chance of this being worked on? @Reguyla -- Can you forward me any research / work you have done on this so we can make it happen sooner than later? Thanks.

In T139453#2436366, @Petrb wrote:

Quite a stupid issue with space:

"@part ##unavailable "

vs

"@part ##unavailable"

Note the extra space on end of string ;)

I will try to fix it in bot code so that it ignores the spaces in names

Yeah, need to restart the bouncers then connect the bot.

Did you restart the bouncers as well as the bot?

Why not just use https://meta.wikimedia.org/wiki/Wm-bot#.40part instead of https://meta.wikimedia.org/wiki/Wm-bot#.40drop ?

In T136198#2345929, @chasemp wrote:

@Technical13 are you actively involved in this project?

Using Phabricator would still mean that xTools developers need to be in two places at once since all the source code is on GitHub. That's why reports are allowed at either. If the goal is to centralize everything to one place, GitHub makes the most sense to me since the code is there.

I'm confused, if the page is only getting assets, why would any data (IP or otherwise) be sent? I guess I just have never learned about this before.

In T87730#2119736, @scfc wrote:

This task has been idling for about a year now, with the RfC going nowhere, and I don't remember any other requests apart from T127494. Is a formal process with lots of criteria and instructions to be followed to the letter still needed? If so, there needs to be someone who drives the discussion and distills it into a draft policy.

Would it be too different or odd to put the collapse for the outer box in the lower left instead of the upper right?  What other options are there to make it not look so odd or at least be distinctive? Change the inner to show/hide instead of (un)collapse?  T13

*sigh* I had completely stopped the webservice because this tool wasn't working. There is no reason to start it back up until it is fixed. If you leave it stopped until then, it won't fill any error logs...

I looked at this when I was first added and it appeared to just be a little lag between DBs. The results I got were much closer to on-wiki result only off by a very small amount I attributed to deleted edits.

Yep. That's why I killed the webservice for it the other day. It's not something that is going to happen soon based on our current levels of free time. I got midterms in a week, so cramming for that.

The webservice was stopped a couple days ago until it can be worked on by someone.

Sorry @EoRdE6, still trying to wrap my head around the consensus. It looks like the consensus is to just completely remove the ability to make text bigger. The alternative might be to add support for big tags as an xml object. Not sure if I want to do that either. Have to think about it a little more.

If it's Yandex's problem, then lets close it.

@Glaisher we haven't been too worried about fixing the redirects yet because we're in the process of migrating all of the tools to xtools.wmflabs.org/tool and will be going through updating them when done.

@Mlaffs You would have assumed very wrong... From my understanding, the job queue is not a linear, easy to follow thing. Changing a template with 50K transclusions does not mean 50K jobs will be added in any specific order. It actually creates a job, that creates jobs based on a bunch of different factors and variables and then runs through those jobs to decide what jobs need jobs and what order to do them in. Then, once it finishes one of the jobs that decides what jobs to run, it creates more jobs to see if the jobs are actually done or if they need to be run again and it makes more jobs based on that including a job that reorders all the jobs... Or, something like that...

@ArielGlenn how are you coming up with 78 jobs? I haven't seen it go below 1.15 million. I still consider it done, but it's still a little higher than normal according to the graphs.

[09:53] <T13|needsCoffee> !tfoo is $1 is awesome
[09:53] <+wm-bot> Key was added
[09:53] <T13|needsCoffee> !tfoo T13|needsCoffee
[09:53] <+wm-bot> needsCoffee: T13 is awesome

In T33919#1274939, @MZMcBride wrote:

Another possible approach might be having a __POSTBELOWHERE__ magic word or similar that could be placed in an arbitrary position on the page.

I'm not sure how I feel about creating new magic words these days.

The only question/concern about this is how is "top" defined for this patch? For AfC drafts, I can see top as defined as section 0; but for the WP:THQ, which is supposed to be top posting, top would be defined as the first section after the header which is section 1 on the page (don't think there are any header sections in templates).

@TheDJ does that ticket now block this one?

Question: I saw someone on one of the help boards asking about the changes to the history pages and am wondering if anyone can add/remove tags or if there are required permission sets?

In T87730#1249301, @yuvipanda wrote:

I don't know if just closing the rfc on meta is enough - this needs some
consensus from the tech community / toollabs admins / wikimedia foundation
ops.

In T87730#1248601, @Qgil wrote:

Is someone planning to work on this task during the month of May? If so, please take it. If not, maybe it is better to lower its priority?

bump per http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Email_is_not_working

Could it be implemented in a way that when the user presses "preview" it'll show up under the edit box "This edit will send notifications to User:AAA, User:BBB, ... like the edit summary does? That way people don't have to guess if it will work and don't have to hit send to see if they actually sent. They'll know before save is pressed (assuming they press preview which I'm guessing they would do if it would help them ensure important notifications are sent out). Also, it could send them a notification too so they know if they got one, everyone else probably did too.

I'll happily troubleshoot this specific situation once we are moved into our own xtools.wmflabs.org instance. I'll have it email me everything when 0 results happen until I can find the cause.

I'd personally object to changing the color from red for talk page edits and mentions. I'd support using a more neutral color for reversions and a different color for things like page links. I'm also concerned about accessibility, (as I mentioned in https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29#Colo.28u.29r_nominations where @Quiddity was so kind to point me here).

In T88954#1214400, @tstarling wrote:

Flow has something to do with Moodbar because Flow is presented as an alternative to Moodbar in the comments above by Quiddity and Eloquence

RfC development started on http://en.wikipedia.org/wiki/User_talk:Sunrise#MoodBar

Now that it looks like Flow may have just been another experiment that may or may not take a great deal more time to complete if it gets completed at all, I'm re-opening this ticket in a stalled state pending a new RfC on enwp as to whether or not this is wanted.

Oh my. This is quit a mess. I wasn't aware of this ticket when I created XTools and started adding tickets to it. Please let me know if there is anything I need to do to clean up after myself, and I will happily do so.

I have a couple questions before I state my thoughts:

• Before this became an extension, how many people had the default on gadget disabled per wiki?
• How many people had it disabled so they could use a custom userscript instead of the gadget (such as http://enwp.org/User:Technical_13/SandBox/Gadget-mySandbox.js) to allow for preferences such as non-standard sandbox page names or custom preloads?
• Will such preferences as non-standard /SandBox page names or preload templates for new sandboxes be allowed with the extension (I'll happily file a separate ticket if so)?

Bump... What is the status on this? I'm assuming this is the reason that when I SSH into labs I'm 'technical-13@labs-bastion-01~' instead of 'technical-13@tools-login' (or whatever it was) and the reason that xTools is refusing to stay up and running. Thanks.

In T86458#1147395, @chasemp wrote:

What is stalled about this?

In T18691#1140407, @Ricordisamoa wrote:

What about something like Bookmark icon.svg?

I saw the section link, had no idea what it was. Didn't think much of it, wasn't a big deal to me. Then, I came across http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Link_to_this_section_snake and subsections and I still had no clue what it was for. I followed one of the links in the discussion to http://en.wikipedia.org/wiki/Help:Section#Direct_section_links and now I know what it does. It updates the URL to a be a link to that section for copy and paste reference.

No other complaints other than "it's down" that I'm aware of. I'd still like to be added as a maintainer if even it means that I must wait for a conclusion to that RfC so that I can restart it in the future (like when there is labs maint or an outage). I have no immediate plans for any specific changes to the tool at this time, but I haven't really looked into the code yet either.

I've had people hunt me down to ask me if I could write a userscript for this and I've had people say it's a great idea when I talk about it. I've never had anyone express any concerns (except for a doubter that thought it was technically impossible but thought the idea was good) or say they didn't like the idea. After all, who wants to type the same content twice or fix the same thing twice? Also, I can only imagine how many decent new editors got discouraged by not having their contributions added correctly and just gave up/walked away since "it's only Wikipedia" and "someone will eventually fix it or create it"

https://en.wikipedia.org/wiki/Wikipedia:T89538 is an example of it working cross namespace. Protection doesn't seem to go (or does it, I wouldn't be able to tell unless I checked with alt account or logged out which is too much work from mobile) but content model follows which is what this ticket is about.

https://en.wikipedia.org/wiki/Wikipedia:T89538 is an example of it working cross namespace. Protection doesn't seem to go (or does it, I wouldn't be able to tell unless I checked with alt account or logged out which is too much work from mobile) but content model follows which is what this ticket is about.

I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.

Any progress on this? Having to go back and clean up things like http://en.wikipedia.org/w/index.php?title=Talk:Will.i.am&diff=646794855&oldid=646794596 is getting old...

@coren http://meta.wikimedia.org/wiki/Requests_for_comment/Abandoned_Labs_tools and I've pinged everyone in this ticket on the page on Meta.

@coren that's what I thought. Is there any process for this or discussion about setting up a process I can watch and if so where might I find links to those things, I'm assuming on Meta or Wikitech someplace?

In T87730#1031051, @coren wrote:

No; since the software in Labs is all Open Source you can just Do It.

@coren @LuisV_WMF @yuvipanda would this same ticket apply if someone just wanted to be added to a tool project but not actually usurp the tool? I ask because @Atethnekos's https://tools.wmflabs.org/bibleversefinder/ tool is offline and the user hasn't been active on any project in months according to https://tools.wmflabs.org/guc/?user=Atethnekos&blocks=true and https://tools.wmflabs.org/xtools-ec/?user=Atethnekos&project=en.wikipedia.org