16% of the code on the average site belongs to Facebook • Hacker News Board

Re: 16% of the code on the average site belongs to Facebook

#51

Post by BinaryIdiot » Mon, Sep 04, 2017, 6:59 PM UTC

exodust wrote: post #47

BinaryIdiot wrote: post #12

Earlier quoted context omitted.

Your point is not entirely accurate though. The likes get displayed and used on Facebook which can help and your post to the top of other people's feeds. I don't like them either but you'd be crazy by not integrating it on a website that you're trying to funnel organic, social traffic to.

It's not the website's job to host Facebook-exclusive functionality. By all means have the basic FB share link, as found on every Youtube video, along with other social media services. But the actual Facebook widget is not what should be installed on websites, and FB should kill it dead. Sounds like you need a browser extension to handle "liking" the current page you're on. Not all websites have the Like button, so i…

I get you but that’s just idealistic. Today you have to do it to help your social engagement. Every opportunity you can get to gain more likes you have to take to get your social postings to rank higher.

Re: 16% of the code on the average site belongs to Facebook

#52

Post by apostacy » Mon, Sep 04, 2017, 8:25 PM UTC

I noticed that when I tried ordering food off www.seamless.com, I could put together an order, but the checkout process would fail in the final step.

It turns out, it was because I had blocked *.facebook.com.

I do not like that major websites will break, if Facebook is blocked. My business with Seamless had nothing to do with Facebook. Facebook does not need to know that I am ordering food. Especially if I am not even logged in.

Why can't I simply say "no" to all interaction with Facebook?

Also, try firewalling Google Analytics, and see how much of the web breaks.

Re: 16% of the code on the average site belongs to Facebook

#53

Post by derefr » Tue, Sep 05, 2017, 3:25 AM UTC

eknkc wrote: post #38

derefr wrote: post #7

Earlier quoted context omitted.

> subscribe to an event that's triggered once the user successfully adds a Like A.K.A. the "like this page in order to enable the download link below" API. I wish they'd never made it; it has so many evil use-cases and I can't think of a single non-evil one (that wouldn't be better served by just async querying aggregate data.)

I don't think that you can easily check if the user already liked your page so that approach would not work.

Right, that was my point—if only an async+aggregate-statistical API for likes to a page was exposed, you wouldn't be able to implement [accurate] like-gating in terms of that (i.e. you wouldn't be able to be Evil), but you'd still be able to do most other things people use the like-button API for, like showing current number of likes (i.e. not Evil).

Re: 16% of the code on the average site belongs to Facebook

#54

Post by exodust » Tue, Sep 05, 2017, 5:44 AM UTC

BinaryIdiot wrote: post #51

exodust wrote: post #47

Earlier quoted context omitted.

It's not the website's job to host Facebook-exclusive functionality. By all means have the basic FB share link, as found on every Youtube video, along with other social media services. But the actual Facebook widget is not what should be installed on websites, and FB should kill it dead. Sounds like you need a browser extension to handle "liking" the current page you're on. Not all websites have the Like button, so i…

I get you but that’s just idealistic. Today you have to do it to help your social engagement. Every opportunity you can get to gain more likes you have to take to get your social postings to rank higher.

I'm sure spammers apply same logic.