jamendo.com surrogate [FOR ALL "FaceBook Connect"]

[rlx]

jamendo.com - a creative commons music site - fouled up their site with a edesign recently. When blocking scripts from facebook domains nothing works.

A surrogate that works for me:

Code: Select all

noscript.surrogate.jamendo.sources;@*.jamendo.com
noscript.surrogate.jamendo.replacement;fb_sharepro_render=function(){}

[Tom T.]

Please review the Forum Rules, and refrain from offensive language, thank you.

[Thrawn]

jamendo.com - a creative commons music site - fouled up their site with a edesign recently. When blocking scripts from facebook domains nothing works.

A surrogate that works for me:

Code: Select all

noscript.surrogate.jamendo.sources;@*.jamendo.com
noscript.surrogate.jamendo.replacement;fb_sharepro_render=function(){}

Thanks for posting that . Even if someone uses & allows Facebook (more specifically, fbcdn.net), the surrogate is handy if they also run RequestPolicy

[Giorgio Maone]

jamendo.com - a creative commons music site - fouled up their site with a edesign recently. When blocking scripts from facebook domains nothing works.

A surrogate that works for me:

Code: Select all

noscript.surrogate.jamendo.sources;@*.jamendo.com
noscript.surrogate.jamendo.replacement;fb_sharepro_render=function(){}

Thanks for posting that . Even if someone uses & allows Facebook (more specifically, fbcdn.net), the surrogate is handy if they also run RequestPolicy

Notice that the surrogate could be generalized to any site which attempts to use the same Facebook Connect feature:

Code: Select all

noscript.surrogate.fbconnect.sources;.fbcdn.net/connect.php/js/FB.Share
noscript.surrogate.fbconnect.replacement;fb_sharepro_render=function(){}

... but it likely wouldn't work with RequesPolicy because NoScript runs later.

[Tom T.]

... [Notice that the surrogate could be generalized to any site which attempts to use the same Facebook Connect feature:

Code: Select all

noscript.surrogate.fbconnect.sources;.fbcdn.net/connect.php/js/FB.Share
noscript.surrogate.fbconnect.replacement;fb_sharepro_render=function(){}

@ Giorgio:

Disregarding RP for the moment (and OP's original impolite language), is that something that you would be adding to the existing NS surrogate?

Code: Select all

noscript.surrogate.facebook_connect.sources;connect.facebook.net/en_US/all.js
noscript.surrogate.facebook_connect.replacement;FB=function(){if(typeof Proxy==='undefined'){var f=arguments.callee;return f.__noSuchMethod__=f.Event=f;}var p=Proxy.createFunction({get:function(proxy, name){return name in Object.prototype?Object.prototype[name]:p;}},function(){return p;});return p;}();

I avoid Facebook completely (which is why I had no comment before), but if many sites are indeed using this "feature", should this surrogate be added as a default?

[Giorgio Maone]

Disregarding RP for the moment (and OP's original impolite language), is that something that you would be adding to the existing NS surrogate?

Code: Select all

noscript.surrogate.facebook_connect.sources;connect.facebook.net/en_US/all.js
noscript.surrogate.facebook_connect.replacement;FB=function(){if(typeof Proxy==='undefined'){var f=arguments.callee;return f.__noSuchMethod__=f.Event=f;}var p=Proxy.createFunction({get:function(proxy, name){return name in Object.prototype?Object.prototype[name]:p;}},function(){return p;});return p;}();

I avoid Facebook completely (which is why I had no comment before), but if many sites are indeed using this "feature", should this surrogate be added as a default?

If those site break without it and it's tested to "fix" this issue, then yes it should.

[Tom T.]

Disregarding RP for the moment (and OP's original impolite language), is that something that you would be adding to the existing NS surrogate?

Code: Select all

noscript.surrogate.facebook_connect.sources;connect.facebook.net/en_US/all.js
noscript.surrogate.facebook_connect.replacement;FB=function(){if(typeof Proxy==='undefined'){var f=arguments.callee;return f.__noSuchMethod__=f.Event=f;}var p=Proxy.createFunction({get:function(proxy, name){return name in Object.prototype?Object.prototype[name]:p;}},function(){return p;});return p;}();

I avoid Facebook completely (which is why I had no comment before), but if many sites are indeed using this "feature", should this surrogate be added as a default?

If those site break without it and it's tested to "fix" this issue, then yes it should.

Very well, then. I've edited the topic title to attract more user feedback.

ANYONE WHO CAN REPRODUCE A PAGE BREAKING WHEN THIS SCRIPT IS BLOCKED:

Please list the site addresses, and please test the surrogate as follows:

1) Navigate away from the site, and open about:config
2) Right-click in the window, and select "New > String"
3) In the pop-up box for "Preference Name", copy/paste

Code: Select all

noscript.surrogate.fbconnect.sources

and click OK.

4) In the pop-up box for "Enter String Value", copy/paste

Code: Select all

.fbcdn.net/connect.php/js/FB.Share

and click OK.

5) Right-click in the window, and select "New > String"
6) In the pop-up box for "Preference Name", copy/paste

Code: Select all

noscript.surrogate.fbconnect.replacement

and click OK.

7) In the pop-up box for "Enter String Value", copy/paste

Code: Select all

fb_sharepro_render=function(){}

and click OK.

Then please close about:config.
Go back to the site(s) that broke with the Facebook script either default-denied or marked as Untrusted.

Does the site now work correctly? Or not?

Your feedback may result in an enhancement for many users. Thank you.