Penguin Cabal

User talk:Anomie

From Wikipedia, the free encyclopedia
Jump to: navigation, search


Crystal Clear app ark.png This user's talk page has archives:

2007 2008 2009 2010 2011 2012 2013 2014 2015

Basshunter[edit]

Hello. What happened with "archive.li" linking? Eurohunter (talk) 18:06, 21 June 2016 (UTC)

archive.is has been blacklisted for years, due to issues with people running unauthorized bots to spam links to the site all over Wikipedia. The mirror at archive.li was added to the blacklist last month. There's currently an RfC discussing unblocking it. Anomieโš” 13:15, 22 June 2016 (UTC)

Perpetuating vandalism[edit]

Anomie: Do you have any idea who was editing as 185.127.244.160? Someone was socking as 185.127.244.160 and IMO vandalizing that page and several others where you've followed up on that IPs edits. You followed up on their edits by removing orphaned links from numerous pages. I wonder what their motivation was, and yours. Can you please explain? Do you actually buy this "archive.is is not reliable" nonsense? Your treatment of these dead links is highly inappropriate. "Remove blacklisted orphaned ref" is not an accurate representation of your edit, IMO. What you did was remove an orphan of a complete citation that happened to use a blacklisted reference, but doing so is not in alignment with editor norms, because the citation would be enough to make the content verifiable even without the blacklisted URL within the citation. As User:Rebbing has already noted elsewhere, and I concur: It's considered bad form to remove dead links from articles without at least making a minimal effort to find a replacement. (Have a look at WP:LINKROT.) Doing it as a drive-by is pretty close to vandalism. Even if archive.is hadn't been removed from the blacklist, which it since has been, it's unconstructive, I think. At minimum, you ought to leave the original dead link so others can make an effort to replace it. Thanks. (Rebbing's note, revised by me.) You understand that archive.is et. al. has been removed from the blacklist? --Elvey(tโ€ขc) 02:14, 19 July 2016 (UTC)

No, I don't know who was using that IP, and I don't care. My motivation was "This reference cannot be re-added to the article due to the blacklist, so I'm going to remove it instead of leaving a big red error in the article". If archive.is has been removed from the blacklist, then AnomieBOT and I won't be unable to re-add the reference so it won't come up. Anomieโš” 13:24, 19 July 2016 (UTC)

Foreign relations of the Central African Republic[edit]

There are 2 bots fighting out there one is yours. just FYI --Varun โ˜Ž 17:17, 8 July 2016 (UTC)

Oauth[edit]

Can you delete my deprecated oauth consumer: meta:Special:OAuthListConsumers/view/4fc51567780d99e946537deeb115544c; it has been replaced by version 1.1. I would have thought that owner-only OAuth consumers would be able to be deleted/disabled by their owners? โ€” xaosflux Talk 23:54, 10 July 2016 (UTC)

Requests for OAuth consumer management should be posted on m:Steward requests/Miscellaneous now, the process has been handed over to them. The feature request for disabling your own consumer is phab:T65712. Anomieโš” 13:10, 11 July 2016 (UTC)
Thank you, I'll subscribe to that ticket :D โ€” xaosflux Talk 17:03, 11 July 2016 (UTC)

Just genius[edit]

This is so clever and so useful. Thank you for your brilliant contribution to this project. --Dweller (talk) Become old fashioned! 07:53, 13 July 2016 (UTC)

API Question[edit]

Hi Anomie, I had a question about the API. Is it possible to use the API to fetch the username of the first editor to a page, for multiple pages with one query? I'm currently using the revisions module to get the username of a page creator, but that only lets me set one titles= param at a time. Thanks, FASTILY 02:27, 14 July 2016 (UTC)

No, that's not possible. We can easily fetch the latest revision for multiple pages because each row in the page table points to it via page_latest, but there's no such pointer for the earliest revision. Anomieโš” 11:26, 14 July 2016 (UTC)
Thanks! -FASTILY 07:52, 20 July 2016 (UTC)

New feature requested for User:Anomie/linkclassifier[edit]

Please see Wikipedia:Village pump (idea lab)/Archive 21#Wanted: yellow links for articles that exist in Draft space - this looks like something best implemented using your linkclassifier script. ืขื•ื“ ืžื™ืฉื”ื• Od Mishehu 04:03, 15 July 2016 (UTC)

Done. Anomieโš” 19:23, 18 July 2016 (UTC)

Category:Pages automatically checked for accidental language links has been nominated for discussion[edit]

Category:Pages automatically checked for accidental language links, which you created, has been nominated for renaming to Category:Pages automatically checked for accidental category and language links. A discussion is taking place to see if it abides with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. โ€” Preceding unsigned comment added by Pppery (talk โ€ข contribs) 14:28, 20 July 2016 (UTC)

Hanging indent for lines, not paragraphs?[edit]

Hi. I recently found a clever solution of yours for creating a hanging indent: style="margin-left:.5in;text-indent:-.5in" and I tried to apply it to a template I recently created ({{Verse translation/sandbox}}). However, the result isn't right:

Line 1
Line 2
Line 3

 

Translation 1
Translation 2
Translation 3

What I'm after is that this hanging indent would be applied individually to each line, not to the whole block as a single paragraph. Thus, the effect should seldom be seen at all โ€” only if the lines were very long, or the screen very narrow. (My underlying implementation is {{#tag:poem|{{{1}}}|style="font-style:italic;margin-left:.5in;text-indent:-.5in"}} so that single uncoded line breaks are maintained in the display. I.e. I want to keep the texts intact and avoid markup like : at the beginning of a line or <br /> at the end.) This is just a nice-to-have, not a necessity, but any advice? Thanks much. Phil wink (talk) 17:08, 4 August 2016 (UTC)

Bot down?[edit]

Wanting to nominate a file for deletion, I just now found myself creating Wikipedia:Files for discussion/2016 August 5, because AnomieBOT hadn't done so. It appears to be creating FFD pages at 23:01 on the previous day, but I can't identify why it didn't create the 5 August page at 23:01 on 4 August. Could you look into it? Nyttend (talk) 02:23, 5 August 2016 (UTC)

I have no idea what might be going on. I'll try stopping and restarting the bot and see if that fixes things. Anomieโš” 13:28, 5 August 2016 (UTC)
Bag bot

Hi Anomie, Would you please check on User:AnomieBOT, BAGBot task (not sure if same issue as this other report) - appears to have stalled out. Thank you, โ€” xaosflux Talk 18:06, 5 August 2016 (UTC)

The other bots down?[edit]

AnomieBOT II and AnomieBOT III may be down too. II hasn't edited since 00:00, 4 August; III hasn't edited since 13:57, 4 August. Chickadee46 talk 17:20, 6 August 2016 (UTC)

MedComClerk bot also seems to be down. โ€” TransporterMan (TALK) 19:41, 6 August 2016 (UTC)

Fixed[edit]

I had a bug in my OAuth code: it was passing a floating-point value rather than an integer for the oauth_timestamp parameter, and gerrit:221863 had a side effect that the different backend on WMF wikis chokes if given a non-integer. Bot updated and seems to be running correctly now. Sorry for the delay in fixing it, I was without Internet access since Friday. Anomieโš” 19:51, 7 August 2016 (UTC)

Face-smile.svg Thank you! โ€” xaosflux Talk 20:46, 7 August 2016 (UTC)

Linkclassifier[edit]

Hello Anomie, I would like to have your script work at commons, I think I've asked you this before but, I'm unable to see or remember how to link back to the script here or add the script to my common.css / common.js there. Sorry to be a bother. Thanx, Mlpearc (open channel) 16:09, 8 August 2016 (UTC)

I believe it should work with something like mw.loader.load( 'https://en.wikipedia.org/w/index.php?title=User:Anomie/linkclassifier.js&action=raw&ctype=text/javascript' );. Anomieโš” 01:47, 9 August 2016 (UTC)

BAG News[edit]

BAG News August 2016
BAG laurier.svg

Greetings Bot Approvals Group member!

  • Please take a moment to review and update your status at the membership page. If you have been semi-inactive, we would love to have you back in action!
  • If you have not already, you may want to consider adding Wikipedia:BAG/Status to your watchlist, it is a bot generated list of all in progress requests.

Thank you! โ€” xaosflux Talk 23:32, 8 August 2016 (UTC)

(You can unsubscribe from future BAG Spam by removing your name from this list.)

Nomination for deletion of Template:2014[edit]

Ambox warning blue.svgTemplate:2014 has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Pppery (talk) 02:54, 25 August 2016 (UTC)

Cheers for AnomieBOT[edit]

This saves me so much fuss - David Gerard (talk) 12:52, 26 August 2016 (UTC)

User:AnomieBOT/SPERTable[edit]

Hello Anomie,

It seems that AnomieBOT is down here; the table hasn't been updated for a few hours. (Though it may be fixed by the time you read this). Just thought I'd let you know, thanks! MeowMoon (talk) 23:59, 31 August 2016 (UTC)

Looks like Labs maintenance may have accidentally killed the bot task. I recently set things up to automatically restart it daily when such things happen, which seems to have worked in this instance. Anomieโš” 13:30, 1 September 2016 (UTC)

Extended confirmed protection[edit]

Padlock-blue.svg Hello, Anomie. This message is intended to notify administrators of important changes to the protection policy.

Extended confirmed protection (also known as "30/500 protection") is a new level of page protection that only allows edits from accounts at least 30 days old and with 500 edits. The automatically assigned "extended confirmed" user right was created for this purpose. The protection level was created following this community discussion with the primary intention of enforcing various arbitration remedies that prohibited editors under the "30 days/500 edits" threshold to edit certain topic areas.

In July and August 2016, a request for comment established consensus for community use of the new protection level. Administrators are authorized to apply extended confirmed protection to combat any form of disruption (e.g. vandalism, sock puppetry, edit warring, etc.) on any topic, subject to the following conditions:

  • Extended confirmed protection may only be used in cases where semi-protection has proven ineffective. It should not be used as a first resort.
  • A bot will post a notification at Wikipedia:Administrators' noticeboard of each use. MusikBot currently does this by updating a report, which is transcluded onto the noticeboard.
Please review the protection policy carefully before using this new level of protection on pages. Thank you.
This message was sent to the administrators' mass message list. To opt-out of future messages, please remove yourself from the list. 17:47, 23 September 2016 (UTC)

Thank you! ๐Ÿ’[edit]

Your AnomieBOT just visited my sandbox. It is great! Thank you! Wanted to do this work next week an now it already is done. Wonderful. --Andrea014 (talk) 05:49, 24 September 2016 (UTC)