While over on the CraftComputing Discord there was a posting about a 12ft.io clone but that is locally hosted, it's called 13ft.
I personally use PiHole to block loads of ads not only on my local network/computers, but also on my remote devices using my local vpn.
I was thinking it'd be a great idea to add support for this 13ft option into PiHole instead of having multiple layers of forwarding to block unwanted stuff while normal browsing.
It's not promoting another site. It's another project that would work great integrated into Pihole.
Also, it's not a name change. 12ft.io is a cloud based service that removes the "Subscribe to finish reading this article" from sites like Newyork Times and other sites that limit information and hide it behind a paywall.
The 13ft project is a predecessor that wasi-master made for use in a homelab local hosting service. It uses reverse proxy as part of its base.
I figured that instead of having 2 different DNS services, or more, it would be nice to have these two kinds of projects incorporated.
Considering the link provided is obviously a github repot, and the name of the project is clearly visible, it's not that difficult to know that the project is safe for viewing.
To me this is very interesting, it is conceivable that running this service on a pihole and then using this to strip paywalls from content (as determined by a DNS lookup list) could be hugely beneficial to most users,
12ft is a well known way of removing paywalls from sites. 13ft is an open source effort to do the same.
Coupled with some lookup redirect logic and built into pihole; this would enable pi-hole users to access sites that have paywalls such as, NYT, WSJ, in a seamless manner
Great suggestion korishan
Also what is the benefit of cross promotion on a git request site, the dozen or so maintainers would be impressed and subscribe to that lol.
In my opinion, this is well outside the scope of Pi-hole (a DNS server) that works with domains only.
How does it work?
It pretends to be GoogleBot (Google's web crawler) and gets the same content that google will get. Google gets the whole page so that the content of the article can be indexed properly and this takes advantage of that.
This stopped working for most of the mentioned sites. You have to match 2 conditions. Sending GoogleBot as engine (can be done with a browser plugin etc.) plus and this is the important condition that connot be faked: The request needs to originate for within the googlebot ip-range: