User talk:Gerard Schildberger: Difference between revisions

m
Add some nowiki formatting to keep this page from showing up in the task list. Other twiddle to cope with new site.
m (Add some nowiki formatting to keep this page from showing up in the task list. Other twiddle to cope with new site.)
 
(One intermediate revision by one other user not shown)
Line 122:
 
The text of an email sent to Gerard:
<langsyntaxhighlight emaillang="text">From: Paddy 3118 <paddy3118@xxx.net>
Date: 7 December 2010 04:40
Subject: Rosetta code.
Line 133:
Thanks.
 
- Paddy3118.</lang<syntaxhighlight>
 
I was beginning to wonder what
Line 145:
Sorry Paddy; at the point where people start sending open letters, I figure it's time I finally take a look.
 
<langsyntaxhighlight emaillang="text">On Tue, Dec 7, 2010 at 6:21 PM, Gerard Schildberger <GerardS@rrt.net> wrote:
 
Michael Mol:
Line 258:
The sequence I've observed to work the best, as far as creation of successful tasks:
 
1) Someone creates a task, and uses <nowiki>{{draft task}}</nowiki> instead of <nowiki>{{task}}</nowiki>, to invite people to critique it and add
some trial solutions.
2) As people add trial solutions, they'll hit on bugs in the spec
Line 264:
describe the task to meet the original writer's desires.
4) The task is refined, and we jump back to step 2.
5) Eventually people don't see a need to refine the task farther, and the task gets switched from <nowiki>{{draft task}}</nowiki>
to {{task}}. If I have time, I'll throw a note out to RC's Twitter and Facebook pages announcing the new task.
 
Sometimes step 1 is skipped, and the author uses <nowiki>{{task}}</nowiki> instead of <nowiki>{{draft task}}</nowiki>. When that happens, steps 2
and onward still occur; it just gets a little rougher.
 
Line 418:
 
--
:wq</langsyntaxhighlight>
 
(I got permission to post the reply.) --[[User:Short Circuit|Michael Mol]] 04:11, 8 December 2010 (UTC)
Line 918:
 
Thank you. [[User:Peak|Peak]] ([[User talk:Peak|talk]]) 19:10, 3 July 2021 (UTC)
 
: I also have the same problems. &nbsp; The '''(1)''' problem (above) is certainly annoying, &nbsp; and I just have to bear it and go through the monkey-works business of clicking on buses, fire hydrants, traffic lights, bicycles, crosswalks, chimneys, and occasionally, tractors or stairs. &nbsp; Even though I've been through all of those before, reCaptcha (Captcha) insists on presenting me with multiple screens (trials) and I have to then play that game. &nbsp; I haven't found rhyme nor reason for the superfluous trials. &nbsp; &nbsp; -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 20:06, 3 July 2021 (UTC)
 
: As for the reCaptcha system, as already mentioned above, &nbsp; I have found out that on a slow PC (the slowness most probably caused by insufficient real storage), &nbsp; that FireFox likes to use both of my engines (cores) such that on my old Windows system, the Microsoft Windows is trying to compete with FireFox's consumption of both (CPU) engines, &nbsp; such that I had to limit FireFox to a single engine (by using AFFINITY). &nbsp; One reason of the excessive use of the CPUs by a browser is the number of cookies, &nbsp; when the number of cookies is large, CPU consumption increases dramatically by a browser, making the browser to become &nbsp; ''non-responsive''. &nbsp; I usually just end up deleting a bunch of cookies and that clears things up. &nbsp; Other people have complained about reCaptcha on Rosetta Code's Village Pump (see the link below), &nbsp; but as far as I know, &nbsp; nothing has been done about it, &nbsp; or more to the point, &nbsp; I haven't read about anything being done about it. &nbsp; &nbsp; -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 20:06, 3 July 2021 (UTC)
 
: See: &nbsp; [https://rosettacode.org/wiki/Rosetta_Code:Village_Pump/CAPTCHA_problems Rosetta Code:Village Pump/CAPTCHA problems].
 
== pi &nbsp; musings ==
10,327

edits