• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

fire fox and "about:config"

BriGy86

Diamond Member
1st off for people that don't know

type "about:config" into the address bar and it will bring up a page of options you can change for your fire fox browser

its got A LOT of things and i was wondering if some one knew more info on them or had a site that they could point me too
 
here's a tweak to make fire fox go faster by using about:config
------------------------------------------------------------------------------------
"Speeding up Firefox!

For those using firefox there is a way to speed it up....and here's how:

1. Open a firefox web browser
2. Type: "about:config" in the address bar, without the parentheses
3. Scroll down and find: network.http.pipeling
4. Double click on it to make it a "True" statement
5. Find network.http.pipelining.maxrequests
6. Double click on it and change the value you "30"
7. Find network.http.proxy.pipelining
8. Change it to a "True" statement
9. Right click anywhere within that browser
10. Select New
11. Select Integer
12. Type in: nglayout.initialpaint.delay as the new statement
13. Select the integer value as "0"

What this does is instead of sending 1 request to a website, it now sends 30...and then the nglayout integer means that instead of waiting for every single bit of information that the site is sending you, it biggiety bams it to you...

It should noticeably speed up your firefox, i noticed a significant speed up on both my laptop and my desktop!"
---------------------------------------------------------------------------------------------------------------------------------------------------
my value for network.http.pipelining.maxrequests is 100, i was told that some sites may not let you access them because you are making too many connections, if this is the case try dropping the value of network.http.pipelining.maxrequests to 20 or so
 
How many times does this hack have to be posted? 😕

Making a lot of connections to a webserver at one time is kind of rude too. 😛
 
Back
Top