!mdn <search query>
and get the MDN search results page.You can also do the same for stuff like
!gweek <search query>
And get google results limited to the last week (or StartPage ones if you swap the g for and s).It's amazing.
I've used these a lot in the past, but switched to DDG's bangs largely because it was such a pain to change browsers/devices, and none of them ever worked for me on mobile. DDG's bangs are still a little unwieldy (! isn't a very convenient character to type, especially on mobile), so an alternative would be nice. For now though, the consistency everywhere far outweighs any other advantages of the in-built browser feature.
Opera, yes.
Unfortunately the UI isn't too great -- on desktop, the suggestions between the awesomebar show you that a keyword search will happen (just like when you type something matching an open tab it tells you that it will switch to tab unless you hit the down arrow to choose something else). On mobile there is no such indication, but hitting enter after typing the keyword followed by the query still works fine and does the keyword search thing.
I might try to fix that.
Let's search for "rfc 1855". The first item is indeed the original plain text source, unfortunately without links or anything:
- https://www.ietf.org/rfc/rfc1855.txt
But the second hit is a third-party source, that doesn't provide much over the plain text version. It doesn't even contain the RFC contents directly. I can't imagine anyone seriously linked to that page, let alone that so many are doing it to push it to the second place:
- https://www.rfc-editor.org/info/rfc1855 ... wtf?!
Moreover, the RFC authors group itself, the IETF, already provides a beautiful HTML representation, with links and everything:
- https://tools.ietf.org/html/rfc1855
But you won't find that in the first 10 hits. Not even in the first 50 hits, for that matter. You will find it, however, if you click at the third item, which is the corresponding Wikipedia entry:
- https://en.wikipedia.org/wiki/Etiquette_in_technology
The very first item in the "External links" section points to tools.ietf.org.
Given the prominent low-quality links to w3schools, rfc-editor and so on, I'm asking myself if Google is actively harming Mozilla and IETF. Maybe not harming, but being ignorant. These issues are known for years. If they want to be the best possible search engine, why don't they do anything about these widely known issues? I understand that they'd rather fix their algorithms than adding special rules for IETF, but then, they should have analyzed their algorithms how they can be tricked by low-quality sites. And fix that. Meanwhile, years have passed and nothing changed.
Maybe we should introduce a new search engine:
"Second-Order Wikipedia"
It would work like this:
1. Look up the search terms in Wikipedia articles
2. For each hit, show the Links of all articles' "External Links" sections.
- https://tools.ietf.org/html/rfc1855 (html version)
- ietf.org/rfc/rfc1855.txt (text version)
- rfc1855.net (another html version which is more readable than the ietf's)
- datatracker.ietf.org/doc/rfc1855/ (information about the history of the rfc)
- https://www.rfc-editor.org/info/rfc1855 (useless)
This is one of the clearest examples yet of why I prefer duckduckgo these days. Even if it might partially be just because less SEO is targeted at them.
https://developers.google.com/speed/pagespeed/insights/?url=...
I think it's likely someone will go through old RFCs and convert them too.
- ietf.org/rfc/ <- this is a static version that IETF has
- rfc-editor.org <- this is the RFC Editor's official site - I think you used to be able to download stuff through FTP, and the site looked like an FTP site until recently; in some sense this is really the canonical URL for RFCs which the RFC Editor publishes
- tools.ietf.org/html/ <- this is mostly Henrik Levkowitz' work - he's working directly on datatracker.ietf.org and has for many years, I think there was a plan to have datatracker.ietf.org contain HTML versions but I don't know the status
- datatracker.ietf.org <- this is the dynamic (Django-based) site that tracks lots of stuff about the working groups and meeting and documents - the source is open so you can look at it if you like - honestly I think this is the best place to link as it gives an increasing amount of context, although tools.ietf.org/html/ is definitely the nicest way to read the contents
https://www.searchenginejournal.com/all-wikipedia-links-are-...
They're looking for "how to do <something>", not for the docs.