Forum feedback forum: Script, script, script, script, script, script, script . . .

Sadly I see this all the time now, on nearly all professionally created web sites.

I'm fortunate in that I have a fast internet connection and so they whiz through, but for those with dial-up or slow broadband it can be a real problem.

You mention older machines. I remember the first car I brought over 40 years ago had drum brakes and cross-ply tires. Remember those? Things move on and such vehicles wouldn't be allowed on the roads here in the UK nowadays.

No such restriction on the internet of course, but 'things move on'. That's my 'real' answer, for what it is worth.

Mark

They will be working on speeding up the pages... but these days as Mark pointed pages are loaded with scripts--they are no longer just the flat HTML pages as they once were.

-Lee

I disabled the Facebook, Twitter, etc scripts as soon as CNET started rolling them out some time ago. CNET is pretty fast when all those other hands aren't in the cookie jar.

John

via AdBlockPlus.

Trial and error with me adding and removing filters for various components until I got it right.

But I suspect John used a custom CSS file.

Mark

For months I couldn't come to CNET already signed in. Finally got some advice on how to defeat it and not have to sign in again each time.

I don't understand what so many like about Facebook anyway. It seems to me a way to end up reading a lot of stuff on each person's "Wall" you'd rather not anyway.

well, relatively so anyway,

We're old. We don't understand this need to plaster ourselves all over the internet with photos and comments and "Like".

Someone recently said, Facebook is Mordor! I couldn't have described it better myself.

Mark

I had great success with using the hosts file to disable
- fonts.cnet.com
- connect.facebook.net

and to lesser extent
- cdn.gigya.com
- secure-us.imrworldwide.com
- b.scorecardresearch.com

No magic involved. Just looking at the "waiting for ..." and "ready with ..." messages on the status line in Firefox suffices to find the timeconsuming links. An occasional look in the html source helps also.

Kees

It seems, today at least, these are four sites that need to be allowed for basic functionality in CNET.

cbsistatic.com (login seems to be dependent on it, at least since Tuesday afternoon)
com.com ('reply' links do not function without it)
cnet.com,
cnetstatic.com (comments to articles will not appear without both of these allowed)

Gigya can be blocked again after the cookie gets set (usually after navigating to an article or something).
As far as I can guess, gigya.com only needs to be allowed long enough for purs_1 to appear in the cnet.com cookies.