Hello!! I am Cyberpower678. I am your typical run of the mill user here on Wikipedia.
I specialize in bot work and tools, but I lurk around RfPP, AfD, AIV, and AN/I, as well as RfA. If you have any questions in those areas, please feel free to ask. :-)
I also serve as a mailing list moderator and account creator over at the Account Creation Center. If you have any questions regarding an account I created for you, or the process itself, feel free to email the WP:ACC team or me personally.
At current I have helped to create accounts for 2435 different users.
Disputes or discussions that appear to have ended or is disputed will be archived.
Actually I am interested in participating and help out with Requests for account creation. So I accessed the interface and I was unable to register myself and the error was that the username was already registered. But I don't remember registering myself. So I tried forgot password option. I was unable to reset as the username and password didn't match. So I tried the same with my past email id. And I got the response that instructions were sent to my email. But I have deleted the email long back, and I am no longer using. As you are the manager of the interface, I've come here for a solution. Regards, Krishna Chaitanya Velaga (talk • mail) 07:37, 28 August 2016 (UTC)
I don't manage the interface, but what was the account name you tried registering as?—cyberpowerChat:Online 14:57, 28 August 2016 (UTC)
Any particular reason you impersonated me on IRC?—cyberpowerChat:Online 17:39, 28 August 2016 (UTC)
I tried registering as "Krishna Chaitanya Velaga". I apologize for my mistake on IRC, actually I wanted to talk to you on IRC, so in that intention I typed you username in the block and later understood that it was a mistake. OK, that you don't maintain, but please suggest me a solution. Regards, Krishna Chaitanya Velaga (talk • mail) 14:09, 30 August 2016 (UTC)
So this is you on ACC. Your account exists. A dev can forcibly change the email to what you need it to be. Also you need to appeal your account decline. I suggest you send an email to our mailing list requesting a change of email address for you account, so you can then send yourself a password reset. While you're at it, you can also appeal your decline, but I don't know why you're declined.—cyberpowerChat:Online 15:03, 30 August 2016 (UTC)
That's done via mail as well.—cyberpowerChat:Online 16:17, 30 August 2016 (UTC)
I have successfully reset my password, but after I login I am getting a response that my account was declined and the reason field was blank. Regards, Krishna Chaitanya Velaga (talk • mail) 13:55, 31 August 2016 (UTC)
Like I said you need to appeal that decline by sending an email as well.—cyberpowerChat:Online 14:15, 31 August 2016 (UTC)
Responses are inline.—cyberpowerChat:Offline 03:50, 29 August 2016 (UTC)
Ok date doesn't make sense to me but will check with TtM. Re the last one I forgot about that. One other thing is the IA API returns URL with port 80 in the URL, it isn't needed so WM strips it out but preserves if non-80. Any chance IAB could remove the ":80" from incoming API results? -- GreenC 04:05, 29 August 2016 (UTC)
I really don't think that is needed. As long as the URL works and the original URL and snapshot time can be extrapolated from them.—cyberpowerChat:Online 16:45, 29 August 2016 (UTC)
I fixed the $ problem.—cyberpowerChat:Online 17:13, 29 August 2016 (UTC)
It just adds a lot of unnecessary ":80" into articles and its simple to strip at the level of incoming IA API JSON. -- GreenC 13:47, 30 August 2016 (UTC)
Regarding dates and User talk:Cyberpower678/Archive 36#date format.. I see the idea there and agree with it when the situation arises. However that's different from converting every cite template (with an archive) to ISO format which probably exceeds the bots mandate, actually a major change. At least use |df=dmy-all / |df=mdy-all (when mdy/dmy are set at article level) so that access-date displays as intended for the article, otherwise the bot will be modifying existing display formats and will likely run into user trouble. -- GreenC 13:47, 30 August 2016 (UTC)
It's not converting every cite template with an archive. It's regenerating the template internally when it changes an archive URL. And I think you misunderstand the df parameter. Attaching "-all" changes all the date formats instead of just the access and archive dates.—cyberpowerChat:Online 13:51, 30 August 2016 (UTC)
Ok that's good it's not a universal change doesn't exceed bot mandate. I guess your right that setting -all might be disruptive in other ways. What about just preserving the existing format, if access-date is mdy continue to use that (unless dmy/mdy is set at global level) and lacking other guidance use ISO. -- GreenC 14:02, 30 August 2016 (UTC)
This stirs up the whole debacle about date formats again. There is no reliable way, that I can see, to accurately detect date formats. It defines the df parameter when there is a global tag in place, otherwise it defaults to ISO per the MOS. That's the best I can do with the bot.—cyberpowerChat:Online 14:05, 30 August 2016 (UTC)
If the bot is able to extract the existing date value from a citation argument such as accessdate, it should be trivial to determine its dmy/mdy/ymd format. For example, WM does this and if it has trouble it defaults but that is rare. And if the bot is able to change date formatting on a per-argument basis then it would be possible, but I don't know enough details of IABot design. See WP:CITEVAR for info on citations and dates. There is no MOS style for dates in citations, however it does say not to arbitrarily change styles (the indented block quote). If it's a technical issues with the bot that's different. -- GreenC 14:42, 30 August 2016 (UTC)
It's more of technical limitation of the bot at the moment.—cyberpowerChat:Online 14:51, 30 August 2016 (UTC)
I think I came up with an idea on how to implement date format detection. I will use the access date parameters and detect whether they follow mdy, dmy, ymd.—cyberpowerChat:Offline 23:07, 30 August 2016 (UTC)
And implemented.—cyberpowerChat:Offline 01:25, 31 August 2016 (UTC)
Great! That's what WM is doing also, but keying on archivedate (WM only works on cites where an archive already exists). If it can't determine it uses the global setting, and if still nothing defaults to ISO. -- GreenC 17:32, 31 August 2016 (UTC)
It looks for all 4 keys.—cyberpowerChat:Online 17:33, 31 August 2016 (UTC)
Hello Cyberpower. I've just read your signature key subpage. If you don't mind me asking, do you use a script to change it, or do you do it manually? I would like to display my online/offline status in superscript within my signature. Thanks in advance, Zerotalk 16:00, 29 August 2016 (UTC)
Note the double-backslash. This creates problems with internal language libraries which either interpret it as an escape sequence, or the URL is seen as having literally two backslashes, which breaks it. Anyway, might be worth testing out on the bot to see how it responds. Same problem with any URL containing a backslash not just \x## sequences. -- GreenC 14:15, 30 August 2016 (UTC)
My best guess is the double backslash will be interpreted as an escaped backslash (single backslash) when PHP decodes the JSON.—cyberpowerChat:Online 14:18, 30 August 2016 (UTC)
Ok. I checked the RFC which says "characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F)". So the IA API is correct to escape the backslash, and PHP is probably handling it correctly. Looking more closely it may be in the way I'm using the Nim JSON parser. Probably still worth checking out PHP in case it turns \x20 into a <space> character somewhere along the way. -- GreenC 15:08, 30 August 2016 (UTC)