Comment

Comment by warbiscuit

That seems really ass-backward, and not just because I use the search feature a lot.

If I'm reading that right, they're deprecating support for discoverable browser-independant markup for searches; and replacing it with the requirement that each site actively develop (and maintain!) a software plugin for every browser their users might want to use.

The whole point of a "user agent" was to go out and do things for me on the web; and the idealistic goal was that each person could choose an agent suited for them, which then had tools to programmatically discover and interact with the web in a common manner (reducing engineering load on the webdevs).

And I don't want to try and use a separate search tool (with new flashing graphics and ads!!!!) for every site I go to... I want a single search tool, like FF offers right now. (Aside: not to mention chrome's "auto-discovery of opensearch when you tab after typing a domain" is actually MORE useful than FF's manual mode!).

Taking a step back and removing support for a declarative api seems to me like the really wrong direction for an open web. Instead of sites supporting a single declarative browser-independent markup; they now have to deal with a long tail of (2-3 + who knows how many) browsers; and users with a niche browser have to spend effort convincing every site to support their browser.

Why not try to improve the opensearch markup instead?

parent warbiscuit 7 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton