![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Recent livejournal madness could be overcome (for some users) by deleting corrupt cookies off of their browser.
I wasn't experiencing the delays in using livejournal, and I have a good idea why. Personally, I keep my web browsers lean and mean.
I disable caching of page requests, and I minimize the allowed storage space for temporary internet files, because I'm not coming in on a low-speed connection. I have broadband, and most services are feed driven and meant to be refreshed several times in an hour. Why would you want caching in an environment like that? Most coders are setting the HTML to tell the browser to override cache in any case, so don't bother storing it in the browser, it isn't being referenced, it's just sitting there holding things up.
I don't download requested plug-ins or load extensions to the browser. If the content becomes mainstream, then the company engineering the browser will embed it in the browser. You open yourself up to the problems inherent in third-party add ons to software. It can create memory leaks, be a medium for viruses, or sabotage the resources of the app by allocating them in a foolhardy way. I live with the ads and other net annoyances.
I frequently trash cookies older than a week. I try not to let them hang out for a month or more. Most sites have rollouts that frequently, and I want to have a relatively new cookie in order to use the site properly.
If a site trashes my browser repeatedly, I tend to avoid it, or access it through another browser. As soon as possible, I will update the erroring browser. Firefox has gotten really good about updating itself.
I wasn't experiencing the delays in using livejournal, and I have a good idea why. Personally, I keep my web browsers lean and mean.
I disable caching of page requests, and I minimize the allowed storage space for temporary internet files, because I'm not coming in on a low-speed connection. I have broadband, and most services are feed driven and meant to be refreshed several times in an hour. Why would you want caching in an environment like that? Most coders are setting the HTML to tell the browser to override cache in any case, so don't bother storing it in the browser, it isn't being referenced, it's just sitting there holding things up.
I don't download requested plug-ins or load extensions to the browser. If the content becomes mainstream, then the company engineering the browser will embed it in the browser. You open yourself up to the problems inherent in third-party add ons to software. It can create memory leaks, be a medium for viruses, or sabotage the resources of the app by allocating them in a foolhardy way. I live with the ads and other net annoyances.
I frequently trash cookies older than a week. I try not to let them hang out for a month or more. Most sites have rollouts that frequently, and I want to have a relatively new cookie in order to use the site properly.
If a site trashes my browser repeatedly, I tend to avoid it, or access it through another browser. As soon as possible, I will update the erroring browser. Firefox has gotten really good about updating itself.
