User talk:Abián
Add topicWelcome to Meta!
[edit]Hello Abián, and welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum (please read the instructions at the top of the page before posting there). Happy editing!
-- 19:47, 24 February 2011 (UTC)
Usuario:Invadinado
[edit]Hi. I deleted the page that you just created, Usuario:Invadinado, since it became an ordinary page and not your user page. You have your user page on User:Invadinado since Meta is using English, despite that it's a multi-language project. -- Tegel (Talk) 18:31, 5 January 2012 (UTC)
Invadibot ha sido autorizado
[edit]Hola Invadinado. He autorizado tu robot bajo la cláusula de aprobación automática lo que te permitirá continuar usando el flag para trabajar con las redirecciones. En el caso de que quisieras expandir el trabajo del bot deberías volver a solicitar autorización. Un saludo. -- MarcoAurelio (talk) 13:37, 4 March 2013 (UTC)
Commons links
[edit]Why doesn't this just use the "commons:" prefix? I'm confused. PiRSquared17 (talk) 11:34, 27 April 2013 (UTC)
- Because the presentation wouldn't be the same, due to there is not a defined text to show:
- [//commons.wikimedia.org/wiki/Category:Monuments_historiques_in_France_by_name] → [1]
- [[:commons:Category:Monuments_historiques_in_France_by_name]] → commons:Category:Monuments_historiques_in_France_by_name
- Regards, and thanks for your interest. --invadinado (TALK - SUL) 11:43, 27 April 2013 (UTC)
Your edits on a chapter report
[edit]Please refrain from editing in the WM NL chapter quarterly report. Ad Huikeshoven (talk) 12:54, 27 April 2013 (UTC)
Invadibot is destroying links
[edit]Hi,
Invadibot is breaking links by converting them into protocol-relative links without discretion, see e.g. [2]. Can you please make an effort to review the bot's past edits for other such problems and fix them, and adjust the bot's rules so that this doesn't happen again?
Also, what is the rationale for automatically replacing all these links by protocol-relative links? I understand the reason for doing so in case of links from one SUL wiki to another (where a protocol-relative link might have the slight security advantage of saving a logged-in user the effort to log in on the target site separately, if they prefer to view or edit it while being logged in). But this does not apply to links to other sites, e.g. https://blog.wikimedia.org/ , and for these, converting HTTPS links to protocol-relative links arguably means a decrease, not increase, in security.
Regards, HaeB (talk) 19:10, 27 April 2013 (UTC)
- Hmm. When I reviewed the bot's edits I didn't see any problematic links but clearly there were some chapter ones that were missed out in the ~200 trial edits. As far as I understand links from https:// are not being converted to protocol relative links, partly for that reason and additionally because there can be some other error messages. Thehelpfulone 20:17, 27 April 2013 (UTC)
- Is the bot's code for these conversions public? It might be safer to restrict them to sites where this is known to work, or to use the HTTPS Everywhere ruleset for Wikimedia sites, which includes a lot of exemptions for smaller domains that don't have HTTPS support, like dumps.wikimedia.org or the really obscure yongle.wikimedia.org.
- If HTTPS links are not converted (this wasn't obvious from the description, but looking at some other edits it seems you are right), that of course takes care of the second concern.
- Regards, HaeB (talk) 01:22, 28 April 2013 (UTC)
- To note that I (temporarily) blocked the bot earlier today as it was editing spam blacklist subpages, and threw COIBot into spasms in IRC and that fallout is still propagating through. Not necessarily a fault of the bot, however, I am being conservative. I reverted a couple of pages and protected them for the future. I also see that the bot is operating in archives of stewards' pages, and I am not sure that it is necessary, or in fact advisable. — billinghurst sDrewth 05:05, 28 April 2013 (UTC)
- Okay I don't know why we are editing pages from many years ago, especially in archives. How far did the bot get before I blocked it? In which namespace is the bot operating? How often is the bot going to be operating? Continuously, one-off, periodically? That information doesn't seem to be available from my quick look. I am going to extend the block so we can have some of the questions answered. — billinghurst sDrewth 06:05, 28 April 2013 (UTC)
- Apologies for blocking the IP address too, my mistake, and now corrected. — billinghurst sDrewth 06:08, 28 April 2013 (UTC)
- Okay I don't know why we are editing pages from many years ago, especially in archives. How far did the bot get before I blocked it? In which namespace is the bot operating? How often is the bot going to be operating? Continuously, one-off, periodically? That information doesn't seem to be available from my quick look. I am going to extend the block so we can have some of the questions answered. — billinghurst sDrewth 06:05, 28 April 2013 (UTC)
- To note that I (temporarily) blocked the bot earlier today as it was editing spam blacklist subpages, and threw COIBot into spasms in IRC and that fallout is still propagating through. Not necessarily a fault of the bot, however, I am being conservative. I reverted a couple of pages and protected them for the future. I also see that the bot is operating in archives of stewards' pages, and I am not sure that it is necessary, or in fact advisable. — billinghurst sDrewth 05:05, 28 April 2013 (UTC)
Minor bug
[edit]In this edit, I think the bot should have un-escaped the URLs (like oswiki and hywiki ones). Although leaving it percent-encoded doesn't break the link, it makes it harder to read. Similarly, it should replace underscores with spaces (although this is debatable). PiRSquared17 (talk) 20:23, 27 April 2013 (UTC)
- Unless there's a reason for the percent-encoding? PiRSquared17 (talk) 20:27, 27 April 2013 (UTC)
Re-run link correction
[edit]Hello, are you planning to run the bot again? (Provided that the problems above are fixed.) It would be useful given HTTPS becoming the default for registered users. --Nemo 12:50, 22 August 2013 (UTC)
Wikimedia LGBT
[edit]I am reaching out to people who have translated pages here at Meta to assist with translating pages at Wikimedia LGBT. If you are willing and able, any assistance would be appreciated. If not, I understand. Thanks for your consideration. --Another Believer (talk) 00:45, 29 October 2013 (UTC)
Upcoming IdeaLab Events: IEG Proposal Clinics
[edit]Hello, Abián! We've added Events to IdeaLab, and you're invited :)
Upcoming events focus on turning ideas into Individual Engagement Grant proposals before the March 31 deadline. Need help or have questions about IEG? Join us at a Hangout:
- Thursday, 13 March 2014, 1600 UTC
- Wednesday, 19 March 2014, 1700 UTC
- Saturday, 29 March 2014, 1700 UTC
Hope to see you there!
This message was delivered automatically to IEG and IdeaLab participants. To unsubscribe from any future IEG reminders, remove your name from this list
Please stop hitting wikimediadc websites so frequently
[edit][redacted] - - [15/Aug/2017:03:18:35 +0000] "HEAD / HTTP/1.1" 301 184 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:18:35 +0000] "HEAD / HTTP/1.1" 301 3586 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:18:49 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:19:03 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:19:19 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:19:23 +0000] "HEAD / HTTP/1.1" 301 3586 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:19:36 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:19:50 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:20:06 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:20:11 +0000] "HEAD / HTTP/1.1" 301 3586 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:20:25 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:20:39 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites" [redacted] - - [15/Aug/2017:03:20:55 +0000] "HEAD / HTTP/1.1" 301 708 "https://tools.wmflabs.org/status/" "Checking availability status of Wikimedia websites"
Is it necessary to hit Wikimedia DC websites so frequently? Please slow your script down. Thanks, Legoktm (talk) 03:24, 15 August 2017 (UTC)
- Hi Legoktm! The script isn't running very often, only four times an hour. However, it has to make multiple requests, in first place, because there is a chain of redirects until the final homepage is reached (in your case, http://www.wikimediadc.org → https://www.wikimediadc.org → https://wikimediadc.org → https://wikimediadc.org/wiki/Home); and, in second place, because it checks wikimediadc.org and www.wikimediadc.org with both HTTP and HTTPS, and this multiplies by four the requests of the chain of redirects. I can remove www.wikimediadc.org and keep wikimediadc.org, which will prevent more than half of the requests. Do you think that will suffice?
- Best regards! --abián 10:41, 15 August 2017 (UTC)
- Yep, that would be great. I should clarify that these requests are pretty cheap, I was just slightly irritated at the time since I was trying to track down what actually was overloading our server and this was continually popping up in the access log. Legoktm (talk) 02:35, 16 August 2017 (UTC)
- Great, Legoktm, done.
- And no problem! The tool should help the owners of the websites, not disturb their work, so thanks for your feedback.
- Best. --abián 12:09, 16 August 2017 (UTC)
- Yep, that would be great. I should clarify that these requests are pretty cheap, I was just slightly irritated at the time since I was trying to track down what actually was overloading our server and this was continually popping up in the access log. Legoktm (talk) 02:35, 16 August 2017 (UTC)
Bot inactivity notice
[edit]Hello Abián,
The Meta-Wiki community has approved a new bot inactivity policy which states that bots that are inactive for a continued period of 14 months should be subject to review. A bot you operate, Invadibot (talk · contribs) meets the inactivity criteria. In accordance with the bot inactivity policy, if you wish to retain the bot flag for the named account, please answer to this message no later than 6 April 2019 on Meta:Requests for help from a sysop or bureaucrat. After that date if the bureaucrats have not received any reply, the bot flag for the named account will be removed.
To reflag a bot, please create a new request at Meta:Requests for bot status.
Best regards, —MarcoAurelio (talk) 11:33, 30 March 2019 (UTC)
The 2021 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 November, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 December and 21 December.
The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!
18:25, 20 November 2020 (UTC)
We invite all registered users to vote on the 2021 Community Wishlist Survey. You can vote from now until 21 December for as many different wishes as you want.
In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones.
We, the Community Tech, are one of the Wikimedia Foundation teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams.
We are waiting for your votes. Thank you!
16:08, 11 December 2020 (UTC)
Global bot flag
[edit]Apologies for the crosspost, but leaving this message here as required per policy.
Hi, I noticed that your bot Invadibot is considered inactive under the global bot status criteria, since it has not edited during the last year - except for eswiki, which is not a global bot wiki. Do you still need the flag? --Rschen7754 07:02, 21 July 2021 (UTC)
Inactive bot
[edit]Hello. As per policy, bots which are inactive for a period of 14 months shall have their flag removed. Please reply here if you wish to keep the bot flag. --Minorax«¦talk¦» 08:14, 9 January 2022 (UTC)
- As there has been no reply or activity from User:User:Invadibot, it has been deflagged. Should you need to reactivate it in the future, please seek new approval first. — xaosflux Talk 14:49, 17 January 2022 (UTC)