162 reputation
18
bio website 127.0.0.217
location
age
visits member for 1 year, 8 months
seen Nov 24 '13 at 1:03

f(N)=44051628437193_38eb3e126b8ad922b196f9e7fd61abcf


Jan
5
comment Why do websites require retyping the password upon user error in a registration form?
@BrandtSolovij: got your point, since in your case you would do anything to help a user who forgot/misspelled the pwd you could drop the 2nd password field in the reg form, but still you shouldn't store the password in any way in case the user missed some other required field, and you can achieve this via AJAX anyway
Jan
4
comment Why do websites require retyping the password upon user error in a registration form?
So what's your take @BrandtSolovij ? You'd make a reg form with only one password field and risk being emailed or called by users to recover their password (you'd get those kind of people regardless of your avenues of recovery) OR you'd just prefill the form again on error with password also set while not taking into account the pointless security issues?
Jan
4
comment Google Site Search ReIndexing
HTML5 just got to "recommended" status and is not mature yet; "broken tags are often parseable" true; forgetting to close tags has bad consequences for bots in understanding/following the content; using JS to modify real content is also a very bad an ugly practice; so in conclusion a badly written website (in terms of markup) should not get taken so seriously and also it doesn't get all the points from SE's ("little difference" as you say, but we shouldn't be lazy here)
Jan
3
comment Google Site Search ReIndexing
@w3d: as you say "And then wait" is the key here. What you're suggesting is a kind of a poke to google, and they might or might not take it into account, but it can still help (you'd better wish you have some good changes to your site by the time the bot crawls). nice answer btw
Jan
3
comment Google Site Search ReIndexing
@DisgruntledGoat: try using multiple H1 tags, broken tags, lot's of javascript an flash, etc... as bad examples