News for hackers. Stuff that matters.
Re:Angie’s List Sues Amazon Local by dang on Thursday July 30, 2015 @09:12PM (#9979370)
Good idea. I've done that above (hopefully icebraining won't mind) and will add it to our list of things to fix (edit: if there's a way to do so that doesn't break normal punctuation). Thanks to both of you!
Re:Angie’s List Sues Amazon Local by aptwebapps on Thursday July 30, 2015 @11:36PM (#9979779)
Stripping periods is probably beneficial more often than not. Also commas and closing parentheses, I imagine. Ideally the script would test url before modifying.
Re:Angie’s List Sues Amazon Local by saurik on Friday July 31, 2015 @05:11AM (#9980713)
I seriously, just a few minutes before reading this thread, out a period after a URL and was concerned "will this break? who is parsing the links, and in what scenarios will the period accidentally be considered part of the URL?" and decided "engh, I bet nothing expects periods at the end of URLs and thereby it will get chopped off, and people putting periods at the ends of URLs probably learn quickly that that causes problems and avoid doing that"... and then I read this thread ;P.
Re:Angie’s List Sues Amazon Local by aptwebapps on Friday July 31, 2015 @05:36AM (#9980783)
I actually have seen urls that ended with a long row of commas, now that I think of it. Empty parameters, I guess.
Re:Angie’s List Sues Amazon Local by jacquesm on Friday July 31, 2015 @06:03AM (#9980871)
Empty parameters won't affect the url resolution (normally), they'll just be passed as empty to the same url. (Assuming the parameters were in the querystring as they should be...).
Re:Angie’s List Sues Amazon Local by aptwebapps on Friday July 31, 2015 @06:08AM (#9980891)
No, not in the querystring. I didn't mean GET parameters.