User talk:Hasteur

Request edit process

I used your name a couple time recently, and want to get you up to speed. I think the request Edit process needs to be done more professionally. I'm working with User:CorporateM on some ideas; they are still in the formative stages, but as you can see at User:CorporateM/request_edit, the format is a blatant ripoff of the AfC format. I know you have been active at AfC, am concerned that you are over-burdened, but trust that you will beg off if this is too much. However, given the parallels to AfC, I hope you can at least share some experiences if you see us headed over the cliff.--S Philbrick(Talk) 19:35, 25 May 2014 (UTC)

This is going to take a little longer than I thought. I just received an article I've been anticipating for weeks, and want to use it to make some article edits. I will get back to the Request edit issue when I can.--S Philbrick(Talk) 19:49, 26 May 2014 (UTC)

Hasteurbot batching

Hello Hasteur; hitting the same page 80 times[1] in under 10 minutes is a little crazy. Could we possible have the bot back-off for 10 minutes, think before acting, and then make a single edit with all 80 notifications in the same edit? —Sladen (talk) 09:30, 26 May 2014 (UTC)

Sladen In short no. The bot evaluates the By Date categories (Category:AfC submissions by date) and then evaluates the individual submissions that are eligible. The reason why there were 80 at the same time is because I accidentally toasted my records of who has been notified so I need to rebuild the database of which editors had been given fair warning that their submission was under consideration. I would also note that users like DGG explicitly opt in to the notifications at User:HasteurBot/G13 OptIn Notifications. I could do some re-structuring so that the bot collects all the notifications for a single run and drops them at the same time, but that runs the risk of some notifications not going out. Hasteur (talk) 13:22, 26 May 2014 (UTC)

Hasteur: Thank you for the reply. Could you help me understand why "some re-structuring so that the bot collects all the notifications for a single run and drops them at the same time" potentially "runs the risk of some notifications not going out". Perhaps we can come up with a solution? —Sladen (talk) 20:33, 26 May 2014 (UTC)

Sladen The re-structuring I would do is move all the notifications to interested editors to the end of the run. If the run terminates abnormally,then the "FYI this became eligible for G13" notifications will be lost.Hasteur (talk) 23:03, 26 May 2014 (UTC)

Hasteur; Yes, re-structuring … move all the notifications to interested editors to the end of the run sounds a good solution. Would the following work for you? For the detection part:

1. Work through each rule/test-case
2. For any notification situation detected, append a notification to the database

Then, at the end of the run, move on to the consolidated notification part:

1. Work through each addressee, attempting to deliver all of the (consolidated notification) for that user
2. Atomically update the flag on each of the delivered notifications once the page containing that notification has been delivered, with the timestamp and when, and the revision ID.

In the case of unhandled exception at any point, the list of awaiting notifications will all still be there in the database. It sounds from the earlier my records of who has been notified … rebuild the database of which editors had been given fair warning that this nearly already exists; just perhaps needs tweaking so that in some manner. (If not, please could you help me to understand how (precisely) an exception is leading to loss of delivery-status information, which would prevent batching). —Sladen (talk) 23:27, 26 May 2014 (UTC)

Hasteur *poke*. This is still going on. —Sladen (talk) 03:12, 30 May 2014 (UTC)

@Sladen: I thought it was clear that based on DGG's response below (on whose behalf you were complaining) that this is more of an annoyance rather than a real need to change. I note that I have 3 other high priority projects (Monthlong AFC backlog drive, DRN noticeboard clerkbot, and Cleanup after a certain editor's mess making at AFC/MFD) that are higher prioritiy. If you can round up a consensus that the bot needs to change then I'll be happy to change, otherwise I'm disinclined to acquiesce to your request. I would also suggest you see if Martijn Hoekstra has problems with the way the notifications are delivered. Hasteur (talk) 12:32, 30 May 2014 (UTC)

It would be nice to have, but I don't really care much, I have rarely more than one delivery a day. As a software developer I say yes, one delivery per recipient per run is nicer. As a software team lead I would say it's probably fairly low on the priority queue depending on other open issues, especially since it needs to be robust enough to withstand a crash without delivery loss. Long story short, my personal preference for batched delivery is small enough that it can be safely ignored. Martijn Hoekstra (talk) 14:00, 30 May 2014 (UTC)

@Hasteur: I happened to spot a bot acting in sub-optimal manner within the User_talk: namespace. I followed the bot's User talk:HasteurBot page (a soft-redirect to this talk page) in order to notify the bot's operator[2] and to provide an example. The purpose of reporting the sub-optimal behaviour (ie. bug) to the bot operator was to enable it to be reviewed, analysed, and fixed. I'm keen to see this issue remedied, and would appreciate if you could share what I can do to assist you in that regard. I've already documented above how the database and delivery mechanisms can be designed in a resilient, atomic and reliable manner. —Sladen (talk) 07:01, 31 May 2014 (UTC) I'm unsure where the mention of DGG and "on whose behalf you were complaining" might have come from; I can't see it in any of my posts above.

@Hasteur: *poke* (again). Please could I highlight WP:BOTREQUIRE a bot … does not consume resources unnecessarily and WP:BOTCOMM Bot operators … will be able to meet any inquiries resulting from the bot's operation cordially, promptly, and appropriately. This is a condition of operation of bots in general. —Sladen (talk) 13:35, 4 June 2014 (UTC)

What part of that requires Hasteur to make changes exactly as you what? It's a design choice, that's it and others have commented that your proposal may be nice, but not needed. Ravensfire (talk) 13:49, 4 June 2014 (UTC)

@Ravensfire:, the last time sub-optimal behaviour (a bug) with HasteurBot was reported, and it was being ignored (including the bot's operator swearing at the bug reporter), an editor using your signature[3] noted: "you've got … users that don't like how it works. Some might, but … sometimes you gotta bit [sic] the bullet, roll your eyes at them and make the change anyway. I hope it won't be too difficult". —Sladen (talk) 15:14, 4 June 2014 (UTC)

(edit conflict)Sladen Please demonstrate how sending the multiple revisions is consuming resources unnecessarily. I observe that it is far better to have atomic changes for the individual pages that were notified on. Please demonstrate how I have failed to respond to inquiries resulting from the bot operation cordially, promptly, and appropriately. Please review my previous statement regarding what other high priority projects are currently on my plate. Please review how I said that I was not going to add your request because I think it's a less than good idea. Please review how the two editors who are affected by the "bug" don't consider this a sufficent annoyance to get it changed currently. Please review how I suggested that if you really think this is a problem to establish a consensus that this needs to happen as opposed to "it would be nice". I prioritize "it would be nice" changes to after I've crossed out a great many other things (like a clean AFC backlog, no backlogged DYK nominations, the entirety of the AFC project in the Draft namespace, the DRN clerkbot activities being finished, and admins going idle) before working on this. Hasteur (talk) 15:36, 4 June 2014 (UTC)

Sladen In that case there was policy on the side and multiple editors came together in a consensus (which I still disagree with). What we have here is a single editor who is wanting a change. I reiterate my assertion, I'm disinclined to acquiesce to your request. Means "no". If you can round up a wide consensus that the bot needs to change, then I'll consider it, but not for the time being. Hasteur (talk) 15:36, 4 June 2014 (UTC)

Personally, I find the current batching sufficient. As long as they are all together in one group at about the same time, I can go through the group and deal with them, and then delete all the notices. I would find it much more annoying to get them in driblets throughout the day. I am, btw, extremely grateful indeed for these notices. Most of mine are for items I previously postponed for 6 months. I find that I continue 1/2 for another 6 months,usually after making a start at improvements, and of the others, accept (or fix and accept) a few, and let the rest get deleted. As usual, the more I work with these, my tolerance for inadequate work decreases. What we need now is to systematically refer postponed G13s to the workgroups. DGG ( talk ) 20:03, 27 May 2014 (UTC)

Template:Did you know nominations/2001 Pepsi 400

You told me to correct an error in 2001 Pepsi 400 to appease Template:Did you know nominations/2001 Pepsi 400, and I had replied; that was 20 days ago. Can you go check it out? NFLisAwesome 15:26, 26 May 2014 (UTC)

Hello Hasteur

First of all Thank you so much, for reviewing my article. Ya that has been decline by you. But next time i'll manage my best efforts to complete that article in appropriate manner.........

Thanking You, Wikipedia User.

Go ahead and delete that page.

The article has already been approved. Delete the page not the article. Please and thank you.Michaelgossett (talk) 02:42, 28 May 2014 (UTC)

Wikipedia:Teahouse/Questions#Mixed Reviews, but same result - Article Rejected!

Heads up... —Anne Delong (talk) 09:49, 28 May 2014 (UTC)

Supersingular Isogeny Key Exchange

Hi Hasteur, Thank you for your comments on the draft AfC. It is my first Wikipedia article and your comments are helping to get the level of the article correct. Do you have the time to look at the article now. I rewrote the introductory material to be much more explicit. The article is meant to expand on information found in the Post Quantum Cryptography wikipedia article. Thank you. Carvalho1988 (talk) 12:50, 28 May 2014 (UTC)

DYK for Prime Prep Academy

 — Crisco 1492 (talk) 14:35, 28 May 2014 (UTC)

Bathwater

Egad, "troublesome"! Thanks for your comment, but the description of us is disturbing. So, here are some rough numbers to consider: Since the ANI was opened Binksternet has made about 500-550 WP edits, the vast majority of which are article/non-ANI related. He created or added 6 new images or articles. Steeletrap has made over 100 edits, the vast majority of which are ANI related. Thomas Piketty is the one article page on which she edited; she also contributed to the Piketty talk page and on some non-ANI pages (I think about 10 non-ANI edits in total). Specifico has made about 75 edits, largely concentrating on Stefan Molyneux and Fractional reserve banking; I think ≈ 30 are ANI-related. ‎ I've done about 240 edits, most of which are gnomish article improvements. I made 15 comments on the ANI, and "earned" this bit of commentary from an uninvolved editor. So it's unfair to lump us 4 together as troublesome. The second aspect is what does "that is judged to be not helpful" mean? I agree that it has gone on too long. For better or worse my suggestions were dismissed as "shifting". I really think Steeletrap has a simple solution available – stay away from Binksternet. Admin Adjwilley was about to close the ANI with a warning to that effect, but got thwarted when Steeletrap made remarks about bias. Alas. – S. Rich (talk) 19:05, 29 May 2014 (UTC)19:41, 29 May 2014 (UTC) PS: my total for ANI-related edits is 44. These involve the ANI directly, indirectly (such as on this page), and minor edits. Egad, more than I thought!!19:51, 29 May 2014 (UTC)

Wikipedia_talk:DRAFT#Process_for_deleting_drafts

Thanks for the note, I collapsed the discussion on WT:MFD, directing anyone to Wikipedia_talk:DRAFT#Process_for_deleting_drafts. — xaosflux ^Talk 22:56, 29 May 2014 (UTC)

Regarding Mockingbird Lane (road)

Hello, Hasteur. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can at any time by removing the {{You've got mail}} or {{ygm}} template.

davidwr/(talk)/(contribs) 19:58, 3 June 2014 (UTC)

Thanks

Hello Hasteur, I would like to say thank you for helping out on the Mockingbird Lane (road) article! Brmedia 23:46, 4 June 2014 (UTC)

Wikipedia talk:Articles for creation/Bangalore Tamils

I've just gone through this & noted that virtually everything that isn't copyvio from the web (which I removed) is copied without attribution from other articles, and found that the editor had gone ahead and created Tamils in Bangalore. What should be done about the AfC version? I'll try to remove the web copyvio from the new article. Please ping me if you reply. Thanks. Dougweller (talk) 12:58, 8 June 2014 (UTC)

Odd, he's still editing it.[4] Dougweller (talk) 13:12, 8 June 2014 (UTC)

Dougweller I'd redirect the AFC version tothe created article... Hasteur (talk) 14:28, 8 June 2014 (UTC)

Thanks. Didn't know that was kosher. Done. Dougweller (talk) 14:32, 8 June 2014 (UTC)

Question re your editing

Thanks for comments on https://en.wikipedia.org/wiki/Wikipedia_talk:Articles_for_creation/Josh_Mahinay. I have changed Further Reading both in format and in moving some to External Links.

I need clarification on this comment, "Most of the focus of the article is about the charitable organization. If we are going to keep this as a biography, the BAG943 content will need to be trimmed down to at most 1 paragraph." BAG943 is the name of Mahinay's business and product, and his business exists primarily to serve the disadvantaged (mostly children) in his country. He does this by partnering with NGOs throughout the Philippines and other parts of the world that also have a commitment to serve the needs of the disadvantaged. Every time someone purchases a BAG943, the company gives one bag free, working with NGOs. Without a strong business, there would be no community service, no collaboration with other nonprofits. Thanks for taking time to help me hash this out!

And thanks for letting me know about the TeaHouse. Judy Vorfeld 18:34, 9 June 2014 (UTC) — Preceding unsigned comment added by Judy Vorfeld (talk • contribs)

Judy Vorfeld Either the submission can be about the biography of Josh Mahinay or it can be about the charitable orginzation. One or the other with a singular paragraph on the other. Hasteur (talk) 18:57, 9 June 2014 (UTC)

Ah, I see. This will be tricky. But I can do this. He is the key. Thanks for the clarification. Much appreciated!Judy Vorfeld 00:08, 10 June 2014 (UTC) — Preceding unsigned comment added by Judy Vorfeld (talk • contribs)

Thanks for the welcome

Hi Hasteur, thanks for your May 18 note of encouragement. I have made major revisions on my page, following the feedback as to why it was rejected. Any tips on how to get it looked at again and considered for approval? Slsw9 (talk) 16:10, 16 June 2014 (UTC)Slsw9

Article on Kash Gauni =

Hi Hasteur , this article meets guidelines. No one is challenging it at this point. Its has gone through edits after edits and is 100% notable and genuine DanVanKant (talk) 16:00, 24 June 2014 (UTC)DanVanKantDanVanKant (talk) 16:00, 24 June 2014 (UTC)

No, I'm challanging it. At this point you can debate it's merits at AFD. Hasteur (talk) 16:01, 24 June 2014 (UTC)

(tps) DanVanKant, the best thing you could try now, is to add references to the article that mentions Gauni. But please, do not try to add more dupes of the same press releases. Sam Sailor ^Sing 16:09, 24 June 2014 (UTC)

Noted; so the requested is to keep building. Will do; Thank you and Kind regardsDanVanKant (talk) 16:52, 24 June 2014 (UTC)DanVanKantDanVanKant (talk) 16:52, 24 June 2014 (UTC)

Why not be bold and let him blow it up?

This whole thing is equine necrophilia now. Fiddle Faddle 16:34, 26 June 2014 (UTC)

Timtrent Because I want the properly conducted MFD (not closed early because a CSD happened) on the books because I've seen editors who DB-self to avoid the MFD only to come back 2 weeks later and start pushing the content again. If we get a admin to officially close the MFD as SNOW delete and deletes the draft (thereby arming the CSD:G4 switch) I have no objections. Hasteur (talk) 16:52, 26 June 2014 (UTC)

I imagined fondly that you were an admin but I suppose you are also involved. Some days our processes do make us look very silly, do they not? Fiddle Faddle 16:54, 26 June 2014 (UTC)

Timtrent I thank you for the vote of confidence (which I'm adding to my Admin Hope chest) but I'm not an admin and I was already hopelessly involved at the point that I commented on the codification of the rules. Hasteur (talk) 17:01, 26 June 2014 (UTC)

By contrast, my new friend, I never wish to be an admin. There is too much mopping and brushing and too little fun in that role. Might you ping a passing admin and ask for a speedy close? Fiddle Faddle 17:03, 26 June 2014 (UTC)

My hands are already fully soiled. I'm sure there are plenty of admins that troll MFD and this nomination is already in the 99% category for length and contention. Hasteur (talk) 17:09, 26 June 2014 (UTC)

Enough with the attacks, please

I've said multiple times that if I believed it were possible for a bot to automatically replace archival links, I would do so. Your proposed pseudocode only works for the very trivial case of a link to content that has never changed. It's incapable of detecting whether the cited information is still present in the current version of a webpage, whether the cited information is present in any archived version of a webpage, or whether the archived version at a Wayback or any other archive matches the archived article at archive.is. Until you can demonstrate an algorithm that can accomplish those tasks, it isn't even pseudocode.—Kww(talk) 23:16, 27 June 2014 (UTC)

Kww In the space of 4 hours (and way past the Ballmer Peak in terms of sleep) I've slapped together a script that can go after instances of the string http://archive.is, look for them in reference blocks, try asking both web-cite and archive.org if they have a replacement, do a page text replacement, and save the page back out. I call BULLSHIT on your "It's too hard to undo the archive.is" assertion. This diff shows a straight copy I took from the mainspace article of the same name and ran a test over it. Hasteur (talk) 04:05, 28 June 2014 (UTC)

There is one more issue I got to work out with that CNN/Elen line where the regex grabbed too much content. Hasteur (talk) 04:06, 28 June 2014 (UTC)

Actually, you proved my point: compare http://archive.is/0dnX with http://www.webcitation.org/6611tUXn0. Completely different pages with the same URL. All you did with your archive action was corrupt the article.~Your code does not verify that the archive you are inserting has any relationship to the page you are removing beyond having the same URL.—Kww(talk) 04:26, 28 June 2014 (UTC)

Additionally, this edit summary was completely out of line.—Kww(talk) 04:38, 28 June 2014 (UTC)

Kww So you're going to be a lazy admin/editor/bot-operator and throw rocks at the suggestion rather than work to improve it? "Herp Derp, I'm a big man because I can send people to the infinite hell of block. Oh look, someone's trying to undermine my pogrom to supress archive.is. Look at how their first test didn't work 100% correctly. Look how they admitted a specific class of faults, Oh my, there's a fault that is covered by the class of faults that they didn't self point out. Let's throw more rocks at them and say that the process, while partially right, will never work". I've proved that it can be done, and that all it takes is for you to not be lazy and for time to develop the replacement when not sleep deprived. Hasteur (talk) 11:18, 28 June 2014 (UTC)

No, you haven't. The "specific class of faults" you can't handle is what is logically impossible to address, and is exactly what I said you couldn't do when you started. There is no way to write an automatic bot that:

1. Compares the current contents of the page to the archive to see if they are the same (note that they are both in different formats and include advertising and other variable content that varies from visit to visit.
2. Parses the content of the article to figure out what fact the citation is supposed to back up.
3. Compares the archived content at archive.is to other archives (again, different formats and they both contain variable content that varies from visit to visit).
4. Looks at the current version of the page to see if the fact that the citation is supposed to back up is still supported by the page.
5. Looks at a currently archived page and see if it supports the fact that the citation is supposed to back up.

You seem eager to paint me as some kind of evil lazy guy. I'm not, and I have no idea why you've developed such an intense distaste for me. The bot you are proposing is an insurmountable obstacle. The code that you've got is just a tweak to chartbot: I could do the URL replacement work and rearchiving in under a day of work. What I could never do is automatically determine when archiving is the correct thing to do: that requires human judgment. I'm not saying this can't be done because I'm lazy, I'm saying it because I've been coding for forty years and know an impossible problem when I see it.—Kww(talk) 13:30, 28 June 2014 (UTC)

Requested move

{{subst:requested move|The Longford Trust |reason=There is a page called The Longford Trust which just redirects users to the page Lord Longford.

This was to help people who did a search for the trust, as there was no special page for it.

Please can you cancel the redirect and replace my content and history and everything under the article titled The Longford Trust. Many thanks.

All the content and history is currently at https://en.wikipedia.org/wiki/Draft:The_Longford_Trust

Wikipedia:Administrators' noticeboard/Incidents

There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. Thank you. G S Palmer (talk • contribs) 22:08, 30 June 2014 (UTC)

Swan House

My understanding is that my contribution on Swan House (Chelsea Embankment) has been combined with earlier material; it's already up at the site. I don't know how deleting the Wikipedia talk:Articles for creation/Swan House (Chelsea Embankment would affect the actual article, but I doubt it would have any effect. But you know best.  :-)

Username

How do I go about changing my username?