And Anthropic (Claude) and PublicAI

...and helping those script developers who now suddenly have a bunch of scripts that no longer work.

@Aklapper Those who make and use scripts on Wikipedia that load external resources.

@EMill-WMF But that creates a giant barrier for user script developers. And this is only one userscript, quite a few of mine are broken. For example my AI proofreader scripts, my Apertus scripts, my AI editsummary script, my AI source verification script et cetera.

https://gerrit.wikimedia.org/g/operations/puppet/+/e14a8dba5cc577ffc528276adad9161944c83d1f Seems to suggest this is a temporary measure, if I am parsing it correctly. Is that true, and if so when will these changes be reverted? @sbassett

@ShakespeareFan00 I have, but on T419234. Probably a bad idea to duplicate my reasoning here.

Toolforge is not usable, that is a giant barrier to entry.

@Jdforrester-WMF Do you happen to know who I should contact?

@Jdforrester-WMF That is not a workable solution for script developers. Waiting on whitelisting means that it would be no longer possible to have a good idea and test and iterate quickly.

This is not what we want, see T419234. @ShakespeareFan00 please close this ticket.

Unfortunately using WMCS/Toolforge won't work. WMCS policy 4.5 explicitly forbids using it to proxy traffic to other servers. Hosting it there would be a policy violation (DVRTed recently asked for permission and was denied).

@Samwilson It would be really cool if I could add an accesskey to a particular button in JS. Do you happen to know how I would achieve that?

But that is not what I want. I also create pages in other namespaces, and I do not want to autowatchlist them. I do want to autowatchlist anything I create in userspace tho.

@Samwilson T399293 and T399295 may also be of interest to you, which may or may not be applicable to the upcoming category browsing feature.

@Samwilson My suggestion would be to parse the dump and make a count how often each template is used in each namespace. I wouldn't depend on categorization, because categories have grown organically, which is a polite way of saying that they are a mess.

@ppelberg See https://www.mediawiki.org/wiki/User_talk:PPelberg_(WMF)#T360489_-_Offer_people_edit_suggestions_within_VE thanks

@Aklapper Yeah I was intentionally recreating the error reported by Yann. I know what these errors mean and how to avoid getting them, but most people don't so the error message should:
*tell people to use fewer search terms, either by using doublequotes or removing words
*tell people to search in a smaller scope
*maybe even tell people not to bother reporting this error

@Aklapper Thanks, you should now be able to see the screenshots. It may be a good idea to have the error page mention that users should use more specific search terms or a more contained search scope.

@Aklapper Currently, when you search for "meta description" in the Phabricator search box in the top right of this page you get:

@ssastry Thanks, that fixed the problem with https://en.wikipedia.org/wiki/Wikipedia:Arbitration_Committee_Elections_December_2018/Coordination/Mass_message

@Aklapper That also applies when you allow only the default images, because you can add whatever functionality to whichever of them you like. If you want to use the Wiktionary logo for a button that increases the font size, that is possible.

@Esanders Agreed. I am not a Javascript coder and I do not work for the WMF. I have made a working proof of concept; the WMF should step in and turn it into a gadget that everyone can use.

This is a important feature for mental health and should be prioritized.

Via WINE the combobox with the sources is difficult to read, but the feature I am asking for exists so I'll change status to "Invalid".

In T382073#10401707, @Nardog wrote:

Couldn't this be an abuse filter?