I suggested this as "Request #93543" at...
...and was asked by support rep "Anthony Honciano" to submit it here. Fine. Here you go...
It sure would be nice if you had, in the Chrome Web Store, an OpenDNS extension. I saw the thread where someone asked for a plugin for Chrome, here...
...and while that's interesting, and needed, the *REAL* need is being able to make one's Chrome (by which, in this case, I mean Google Chrome, as well as any Chromium-based Chrome-look-alike; including Chromium, itself: so that would include Comodo Dragon, SR Ware's IRON browser, and now even Opera, among many others) browser use OpenDNS whether or not the rest of the machine also so does for other purposes.
In other words, even if the machine, itself, within Windows, is configured to use the ISP's default DNS, there should be a way to have just the Chrome browser (using an OpenDNS extension -- not a plugin, but, rather, extension, from the Chrome Web Store -- which, of course, doesn't exsit yet; or at least I couldn't find one, hence the reason I'm making this suggestion) use nothing but OpenDNS.
The reason this is important is for users of portable versions of software -- on others' machines using thumb/flash drives on, for example, one's keychain -- like me. I work on others' machines; and when I sit down at another's machine, I insert the flash drive on my keychain and it auto-launches a menu system, and from it I use my own copy of the Chromium-portable browser so that no matter where I go, or whose machine I'm using, I have my own browser with all its own settings and is auto-logged-in to everything; and doesn't leave a trace on the machine after I'm gone.
Whenever I do such a thing, I'd like to be able to use OpenDNS while in my Chromium-portable browser, even if the machine at which I'm temporarily sitting is using its ISP's default DNS, as configured in Windows.
Yes, I realize that by simply also including, on my flash drive, the portable version of something like "NetSetMan," or "Net Profiles," or "Quick Config"...
...I can simply launch, from my flash drive, a tool that will temporarily reset the entire machine's DNS to use OpenDNS; and that when I'm done I can just set it back just before I remove my flash drive and then reboot the machine...
...and that's how I've been doing it; and if that's my only choice, then fine. However, it sure would be nice if there were a simple OpenDNS extension in the Chrome Web Store which allowed a person (after installing it into Chrome) to have all DNS used by at least the browser happen through OpenDNS, regardless how DNS on the machine on which said browser is running is configured.
Making the OpenDNS "IP Updater" software so that it may be run portably would help, too. But back to the extension idea...
Said extension would have, at minimum, these features on its "Options" page:
1) A basic "on/off" switch to turn on/off the extension's ability to force OpenDNS use in the browser; and,
2) a place to key-in and save one's OpenDNS login credentials, with options to allow (or not) the machine one's using to be included among one's networks; and also so that one's guide and block pages will contain one's logo, etc.; and, which would remember said credentials (if a checkbox is checked wherein one specifies to remember them) from browser session to browser session, even if the extension is either turned-off using the switch in item "1)" or even completely disabled on the Chrome "Extensions" page (though said credentials would not survive the complete uninstallation of the extension); and,
3) the ability to configure whatever basic things from one's dashboard and account settings, and for the specific network, that it would make sense to include in such an extension so that one needn't even go to one's dashboard and settings on the OpenDNS website; however, if one *DID* need to so go, then because one had already given one's login credentials in the extension, one could just be taken straight to one's dashboard and settings on the OpenDNS site without having to also login there; and,
4) of course, the "tagging" capability asked for in the request for both a Firefox and Chrome plugin, to wit (from the Firefox request): where one "can use to sign in and submit site's they find or get sent too which should be flagged. a plugin with right click options to submit the url which pop's up a window to select the category it be should placed in etc."; and, finally,
5) the extension would, if possible, adequately address what's described here:
Overall, this extension would, in a way, sort of do what the tray IP updater does, but only for whatever happens only in the Chrome browser... but with much, much more!
The reason I propose that this should be the first extension of its type developed is because by doing it for Chrome and Chromium (the differences are sufficient that you'd really need to test it on both), it would automatically be useful on all other Chromium-based browsers out there; and so with just the one extension, you'd be coving a huge range of browsers.
Thereafter, a Firefox plugin, and then IE BHO could be developed; and at that point you'd have something like 90% or more of all browsers covered in just three pieces of software.
There would, of course, need to be Mac and Linux versions, too; but, of course, do the Windows ones first.
Also, remember that Google announced just this week that...
a) it is now, immediately, finally making good on its October 2013 promise to not allow any extensions to be installed into Chrome (not Chromium, or browsers based on it, mind you... only Chrome) which do not come from the Chrome Web Store; so you would definitely have to put it there, once you develop it; and,
b) it is, very soon, going to stop allowing anything using the NP API to be installed into, and run in, Chrome (again, not Chromium or browsers based on it... only Chrome); and it will allow only PP API (Pepper) based plugins and extensions; so you'll need to avoid NP API code and technique entirely. Yes, NP API stuff will continue to run in Chromium (and all, except Chrome, based on it), but developing both an NP API and PP API version would be silly. Just do the PP API one, which will, of course, run in both Chrome and Chromium and Chromium-based browsers).
The need for this is HUGE; so I hope you'll strongly consider it.
Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com
Honciano also said he would be "marking this ticket as a feature request so it can be reviewed."
Hope that helps.
Please sign in to leave a comment.