Live data from Hacker News

Blocklist of all Facebook domains

github.com

101–110 of 152 posts

Re: Blocklist of all Facebook domains

#101
post #52

Honest question because I seriously don't know: Is facebook really worse than google when it comes to privacy? I kind of wonder who exactly are the people telling everyone to block facebook everywhere while everyone seems to collectively ignore google. Google and facebook seem to both purposely ignore the known implications of their data collection programs. They likely have handed over data to the NSA, and we know t…

> we know they sell the data

Sounds a lot like "we know global warming is fake" and "we know vaccines are evil" to me.

Re: Blocklist of all Facebook domains

#102
post #39

Will there be a point where the government will step in or is all of this tracking within fair use of non-logged in Facebook users visiting a website?

If they regulate it, they will probably do it like in the EU where you have to click on some super-annoying "I agree to cookies bla bla bla" thing entering any website, which just trains people to automatically agree.

Re: Blocklist of all Facebook domains

#103

Earlier quoted context omitted.

Microsoft was an investor in Facebook, http://whoownsfacebook.com and they are planning an undersea cable between the US and Europe that will only be used by the two companies.

What for? I can see Trading companies doing that but why would Microsoft/Facebook need that?

they are trading data

Re: Blocklist of all Facebook domains

#106

It's inefficient to specify a large number of hosts in the facebook.com domain instead of blocking the whole domain. For this, you can run dnsmasq and use the "--address" option or "address" command in dnsmasq.conf: $ man dnsmasq [...] -A, --address=/ /[domain/] Specify an IP address to return for any host in the given domains. Queries in the domains are never forwarded and always replied to with the specified IP add…

[deleted]

Re: Blocklist of all Facebook domains

#107
post #98

Earlier quoted context omitted.

Because most people don't block outbound and certainly not in a stateful way which means it's a poor place or a blacklist. To get this to work outbound, you need to allow all other traffic out (fine that's probably what you are doing already) or have a curated whitelist of other traffic allowed out. I assume this package doesn't want to make that assumption so the safe thing to do is to make an inbound blacklist.

That doesn't make any sense. You can block outbound just fine by having your block rules followed by a default allow. You don't need anything to be stateful when you are blocking whole IP addresses.

So this has to assume that it's not a whitelisting setup and put a default allow. Which if you do outbound whitelisting, kinda fucks things up.

Re: Blocklist of all Facebook domains

#108

I'm wondering ... what's the best approach to automatically collect all domains of a company?

there is no consistent way of defining the meaning of "all domains of a company". Who pays for the registration? Which email is listed as technical contact? Who has the authority to change DNS-records? Which email listed in the DNS SOA-record?

Re: Blocklist of all Facebook domains

#110
post #15

Not the way I'd do it, since you can easily miss on some new domain that belongs to facebook (or perhaps some server that does not look like it belongs to facebook in the first place, but it is sitting in their assigned subnets). If you really want to block all traffic from/to facebook, lookup the IP prefixes associated with their AS number(AS32934), and setup your firewall to block those. If you are using PF, tables…

I'm surprised that AS-based blocking tools aren't already more prevalent and readily available.

AS information isn't trivially available, though you can do a pretty good job through tools like the CIDR Report and ASN Routeviews.

There are quite substantial portions of the Internet to which I'd generally provide very little or very limited access if I had my druthers.

Post reply on HN