[91325] in North American Network Operators' Group
Re: Web typo-correction (Re: Sitefinder II, the sequel...)
daemon@ATHENA.MIT.EDU (Edward B. DREGER)
Fri Jul 14 23:30:30 2006
Date: Sat, 15 Jul 2006 03:29:45 +0000 (GMT)
From: "Edward B. DREGER" <eddy+public+spam@noc.everquick.net>
To: North American Noise and Off-topic Gripes <nanog@merit.edu>
In-Reply-To: <027e01c6a774$b492ead0$363816ac@ssprunk>
Errors-To: owner-nanog@merit.edu
SS> Date: Fri, 14 Jul 2006 13:38:31 -0500
SS> From: Stephen Sprunk
SS> Ever used Word or Outlook? They annoyingly "fix" words as you type without
SS> offering multiple choices or even alerting the user that they're doing it.
Yes. One of the first "features" that I shut off.
SS> OpenDNS's typo-fixing service can supposedly be turned off, but I don't see
SS> how that would work when you have multiple users behind a NAT or a recursive
SS> server. There also may be hidden problems if an ISP pushes all of their
SS> users onto this service and the users have no clue they've been "opted in"
SS> or how to opt back out (and we all know how well "opt out" systems work for
SS> email in general).
*nod*
SS> And that solves most of my objections, at least for HTTP. It still breaks a
SS> lot of other protocols.
...which still poses problems that should not be ignored. I forked a
subset of the main discussion in hopes of better idea organization.
Other protocols should indeed be considered.
It's a question of protocol-specific proxying when [at least for now]
DNS returns protocol-agnostic answers.
As a side note, I wonder how many users would notice a typo-intercepted
HTTPS side and associated invalid/bogus certificate. I'm afraid the
number would be rather low.
SS> If web browsers consulted SRV records instead of blindly connecting to the
SS> A, that would appear to solve everything: NXDOMAIN for the A but the HTTP
SS> SRV could point to the typo-correction server. I'd not be inclined to argue
SS> with such a setup, but it requires a refresh of every browser out there, so
SS> it's not realistic.
Agreed re the short term. However, SRV records have other uses -- why
should MXes get all the special treatment? -- so I'm trying to put
another tally in the "[potential] reasons to use SRV" column. Perhaps
if the ball began rolling...
Eddy
--
Everquick Internet - http://www.everquick.net/
A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 785 865 5885 Lawrence and [inter]national
Phone: +1 316 794 8922 Wichita
________________________________________________________________________
DO NOT send mail to the following addresses:
davidc@brics.com -*- jfconmaapaq@intc.net -*- sam@everquick.net
Sending mail to spambait addresses is a great way to get blocked.
Ditto for broken OOO autoresponders and foolish AV software backscatter.
