Re:Chrome will Soon Let You Share Links to a Specific Word o...
by sokoloff on Friday February 15, 2019 @10:22AM
(#19171574)
I think that's more risky in that most browsers and many intermediate proxies or other traffic inspectors are likely to have special casing around http: (at least) and https: and for most traffic to be over http(s): and a tiny sliver over web+text: seems fraught with more peril than a (fairly small and intention-aligned) abuse of #fragments. Even mail agents, markdown processors, and other text-display applications often have special casing to turn http(s) URLs into touchable/clickable links.
Page authors are unlikely to use web+text: if it means cutting off old browsers from access.
Re:Chrome will Soon Let You Share Links to a Specific Word o...
by croddin on Friday February 15, 2019 @10:18AM
(#19171534)
Googles’s fragment solution should gracefully degrade to behaving like the normal link in other browsers (as long as there isn’t some fragment conflict) but creating a new pseudo protocol would have to be supported by each browser to even get to the site.
Re:Chrome will Soon Let You Share Links to a Specific Word o...
by Robin_Message on Saturday February 16, 2019 @03:01AM
(#19177630)
You could use two hashes like that and stick with http. I reckon browsers would cope, and you could strip the second one.
To double check, does this means things like,
Can become The only part I don't get about the likelihood and this extension is how it interacts with these kind of hash routes.I haven't thought that much about the next part, but how do people feel about the following?
or something. Rather than extending URLs vertically, extend horizontally into a different protocol the URI of which can encode the syntax elegantly.