Thu, Jun 22
Wed, Jun 21
Fixed in v1.1beta4
Unable to replicate #3, seems to be fixed with number 2.
#2 fixed in v1.1beta4. The two URLs were seen as the same and treated this as a null edit and ignored it.
I have deleted that unused URL.
The URL ID sanitized on the interface is 24655054 while yours is 7065467. Based on the ID sequence, the unsanitized version is clearly an old remnant of the old bot code.
When you load via the interface, it sanitizes the URL and retrieves the correct URL ID. But when you provide the URL ID to modify, it goes straight to the target. The target already has the archive URL added to it. When nothing is being changed, it just comes back with failed.
For number one, there are duplicate entries in the DB, one sanitized and the other that isn't. :/
Looking into these now.
Number 2 fixed in v1.4beta3.
Tue, Jun 20
Fixed number one in v1.1beta4.
Cleaning this out. The latest code has a sanity check against this. So I've run the bot on all pages this was reportedly found on, an it cleaned out all but two articles. Investigating why.
As for number 2, it should be respecting existing formatting. Not sure what happened here.
@Shizhao What's wrong with the format in number 1? It appears to show the month in Chinese. That date format on the interface is not that same as the format used on Wikipedia. Plus it understands different date formats as well.
Mon, Jun 19
API is live, new documentation will be up by the end of tomorrow.
Number 4 is now ready to go. These will be available in the beta3 release.
I think Number 3 is finally ready to go. I'll do some more benchmarking tomorrow, but it seems to be stable.
Sun, Jun 18
Cyberbot is getting the data from the API. It probably got a null response at some point and just defaulted to unix epoch 0. I haven't seen it happen since.
Fri, Jun 16
Number 3 is something I've been struggling with for a while. There are serious performance issues adding in this particular filter.
I've been playing around with number 2 for a bit, but I think I got a good solution. I'm tying the results into the logs, to get you your information. You can access the hidden reviewed parameter by setting the filter reviewed to either 0 or 1. This is will be in the beta3 release.
Thu, Jun 15
No further response.
You can also see more details at https://tools.wmflabs.org/iabot/index.php?page=metainfo
On the graphical interface, you can see the deployed versions of IABot and the CID library, on the footer of the site.
Wed, Jun 14
Number 2 has a reviewed field in the column, but it's a hidden field. It doesn't identify who did it and when, but it's only set when changed via the API or the interface. However, this can be tied into the logs that have the URL ID associated with it. Everything is heavily logged after all.
Number 1 implemented in beta3.
Tue, Jun 13
Very stale edit. This predated version 1.0
In regards to the first diff, it's because the wrong archive is associated with the URL. I have now fixed it in the DB. The other issues are are because of inconsistent archive URLs associated with URLs.
Fixed in 1.4beta2
Fixed in the v1.1beta3 release.
IABot can handle them if they redirect to the new URL. Otherwise, it can't know what the new URL is.
Not a bug.
Mon, Jun 12
Sun, Jun 11
I reject everything on your wishlist, because I choose to be mean. :p
If it's not recognized as a valid archiving service, it will overwrite the URL with one that is recognized, or just ignore it if it doesn't think it has anything better. That URL in the archive-url field doesn't look like a web service that hosts snapshots.
That last sentence was supposed to refer to the FaQ in the previous sentence.
Not really. The reported reason is because the bot is receiving a response from the server. So it means the bot may have been blacklisted on labs.
I think you got your links mixed up. I see no such link being changed on that article.
Thu, Jun 8
BTW, I need willing translators for translating the IABot interface.
Implementing this wiki now. I should hopefully have it ready in 48 hours.
Well, Wikipedia forces HTTPS. So all protocol relative URLs go to HTTPS. So the link needs to be fixed on wiki.
Wed, Jun 7
Perfect. I'll start the bot up.
Honestly templates should not be embedded into URLs. That is the worst thing ever and no bot will ever consider a template embedded into a URL when looking for them.
Tue, Jun 6
Bot needs the bot flag. It cannot run when being blocked by the captchas.
I found the archives.
Approved and functional.
BTW, I need willing volunteers to translate the interface to the simplified and traditional variants of Chinese. It can be done at TranslateWiki.
Mon, Jun 5
I'm surprised none of these templates have Chinese names. The idea is to have IABot integrate with all url/archive url citation templates.
Sun, Jun 4
In the meantime, I'll work on getting IABot deployed on the Chinese Wikipedia.
Bot appears to be approved, but a trial run should be run first, and of course a trial will be done first but, before the bot can be deployed, @Danmichaelo I need some translations done.
This awaiting final approval.
@Sjoerddebruin if I can direct your attention to https://nl.wikipedia.org/wiki/Wikipedia:Aanmelding_botgebruikers#InternetArchiveBot. Any help would be appreciated.