In regards to not tracking users...integrating a http request to Google for JQuery, is still tracking users. I always find this ironic about these articles don't track your users , or prism is watching, let's use mailvelope , some of these pages that is promoting privacy, integrates google analytics, have a share button, or some type of off server request.
Why to use Twitter, Facebook and Google Plus share links and not buttons
21–30 of 65 posts
Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#22Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#23So using links instead of the widget codes is better for your site (performance wise), privacy wise, and it degrades gracefully when people like me use Widget Blockers.
Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#24Those networks can still track user habits by clicking the URL. In one acorn, they will know they came from your site, any user agent information, screen size (via JS on the social network site), if they are logged in they will associate them going to your site even if they decide not to share the URL. The only thing they aren't seeing is additional analytic data they're missing out by not having there JS installed o…
Isn't that kind of the point though - if I don't click the URL then FB/Twitter/G+ etc etc don't get notified of my visit to a third party site that includes their buttons. If I do, fine, I'm going there and they get the info, but usually I don't.
Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#25Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#26Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#27Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#28Re: Why to use Twitter, Facebook and Google Plus share links and not buttons
#29I don't have an opinion on the core of the article, but this bit at the end is not the best advice from a user experience standpoint. "And I am seriously thinking into serve my own copy of Twitter Bootstrap scripts instead of serving them from the Google Network." The point of using a CDN for common js/css is to serve it as close to your users as possible as well as increase the change that they already have it in th…
Sorry, you are right. it is NetDNA's From the performance point of view is better to use that public CDN. But they have control over the javascript, and they may change it at anytime. Maybe too paranoid, so just thinking about it.