Posts tagged ‘Firefox’
When you use a socks proxy with firefox (with SSH for instance) the dns lookups are done via your default gateway. Which makes the whole thing pointless if you’re trying to be private. This setting makes the dns lookups go out over the tunnel where they can’t be sniffed.
1. go to about:config
2. search for network.proxy.socks_remote_dns
3. Set to true, which will have the proxy server perform DNS lookups.
Want to speed up your text editting in web forms? Here’s a few quick keybindings:
Because of the netbook craze or just because you like seeing more of the web and less of the application it takes to view it, one might want to minimize the usage of screen space taken up by various firefox functions. Below are several tips for accomplishing this.
When you Ctrl+K to the Google search box in Firefox, type your terms and hit Enter, the results appear in your current tab – but it’s easy to make ‘em open a whole new tab so you don’t lose your current page.
Type about:config into the address bar, and then put the following into the filter box: browser.search.openintab. Double-click the value to change it to true.
You can also use Alt-Enter when you search to open a new tab optionally. Want more Firefox about:config magic?
Playing with uzbl, I recently created a flat text file of my bookmarks saved in ~/.bookmarks, a bit cumbersome right now, but the good part is uzbl isn’t the only browser who can open links given to it from a dmenu script.
Continue reading ‘dmenu script to open bookmarks in firefox tabs’ »
Anyone using both Vimperator and Tree Style Tabs (great combo) will have noticed the actual “tree” organizing of sub-tabs hasn’t worked together since the Vimperator 2.0 update. Luckily there’s a fix.
This appears, on quick inspection, to be due to a ‘clash’ with vimperator’s tab number tab bindings.
Adding the following to your ~/.vimperatorrc file is the best work around.
js styles.removeSheet(true, “tab-binding”)
This will remove the option of using tab numbers.
Firefox 3 is a significant stride forward in features, but it carries with it an equally significant stride backward in performance. The stats are much better – better memory usage both at startup and over time, faster JavaScript execution, less CPU time – but the browser just felt sluggish, even when it shouldn’t. Thought that your system with a terabyte of RAM and 256 cores could make Firefox soar? It turns out that, for most users, Firefox is actually I/O-bound, in large part because of the switch to SQLite databases.
SQLite is designed to be portable and highly reliable, and it pulls this off with amazing success. However, it does this at the cost of speed. SQLite implements its own journaling system, lock contention procedures, multi-process access, and more. Since SQLite is a portable library, the only way to pull these complex feats off is through standard file I/O. As the volume of data that Firefox stores in SQLite databases grow – and as the number of tabs concurrently trying to access those databases on your system do as well – the time spent by Firefox on secure, hardware-backed I/O grows as well. And since SQLite is so cautious about synchronization, even gobs of RAM and a fast CPU can’t help; the process becomes entirely I/O-bound, particularly at the moments where it should be the most responsive (typing a URL, opening or switching tabs, and the like).
But how attached are you to the last five minutes of your browsing history, really? SQLite’s agonizingly slow access times can destroy performance – and, because of the high volume of writes, it can also destroy sectors on SSDs, USB drives, or other flash media if your profile is on one of these devices. To me, it’s worth accepting a little volatility in the event of a crash for a noticeable and welcome increase in responsiveness.
tmpfs is a virtual, RAM-backed filesystem. It’s lightning-fast, but since it’s RAM-backed, any file written to tmpfs uses precious memory while it’s there, and the entire contents of the virtual partition are lost on shutdown or crash. The good news is that these detriments can be minimized, making tmpfs a viable choice for your profile directory. This document gives some tips on how to mount your Firefox profile in a tmpfs partition while minimizing the downsides of tmpfs.
While Vimperator offers already lots of cool features, the vimperator team cannot be expected to include every feature directly in the core. But they allow their users to enhance the Vimperator experience by adding plugins which add new commands or mappings. You can install plugins by copying them to the ~/.vimperator/plugin/ directory.
NoScript , being a separate extension in itself, doesn’t have any controls natively within vimperator. So what we can do is get the following script ; (http://vimperator.org/trac/raw-attachment/ticket/1/noscript.js ) and place it in our ~/.vimperator/plugin/ directory.
Continue reading ‘How to control NoScript via Vimperator in Firefox’ »
add the following line to your .vimperatorrc
javascript liberator.beep = function() { return false; }
For some reason Firefox’s vimperator plugin removes the RSS button that allows you to easily add a page’s rss feeds to your Google Reader or other present RSS reader. Simple enough, just edit your ~/.vimperatorrc file and place the following within :
javascript <<EOF
(function(){
var feedPanel = document.createElement("statusbarpanel");
feedPanel.setAttribute("id", "feed-panel-clone");
feedPanel.appendChild(document.getElementById("feed-button"));
feedPanel.firstChild.setAttribute("style", "padding: 0; max-height: 16px;");
document.getElementById("status-bar")
.insertBefore(feedPanel, document.getElementById("security-button"));
})();
EOF
