Archive.is and its domain variants are actively blocking many VPN services and have been for some time. I'm assuming it's because they're under a never ending DDoS, which would also explain the need for Cloudflare. I would love it if people supplied screenshots of things alongside archive links as well. Sadly 8ch also uses Cloudflare. Several issues regarding Cloudflare:
* Wouldn't two sites using Cloudflare make it possible to track a session ID across otherwise unrelated sites regardless of whether a link was clicked?
* Wouldn't Cloudflare be able to seamlessly serve you modified or filtered content without you even noticing? You do have to set the DNS entries on your domain to Cloudflare's servers so they can cache for you.
* If they're caching content, doesn't that mean that humans are telling them what content is worth looking at? I can imagine a system where they prioritize cached content for OCR and datamining based upon how many UUIDs request it, as well as some other factors. Who needs spiders when you've got humans?
* Would this not render most link breaking somewhat futile? While yes, the place you're going to won't directly know you're sending them traffic, couldn't they still obtain that information from Cloudflare or whatever organizations they're selling it to?
However let's assume that both the sender and receiver don't have Cloudflare in their butt and the user is taking steps to prevent Google, Facebook, etc. from arbitrarily stalking them. Is there any way to reinvent the wheel with regards to tags so that you can more or less link someone to another site without that site getting the HTTP Referrer and Origin? Say by abusing other tags, or maybe with Javascript?
It dawned on me earlier that Google's abuse of links inherently discourages the use of a search engine's primary competitor, indexes. The reason being that being listed in certain indexes, or too many indexes, can negatively impact your search rankings. Nobody wants "bad juice." Therefore people are disincentivized from listing with them. Even breaking the HTTP Referrer and Origin wouldn't necessarily stop Jewgle from attributing "juice" via spidering though, right? If the site encoded the URLs in a custom encoding format, would this would be sufficient to avoid detection by most spiders? I suspect that any alternate encoding which gained too widespread a use would likely result in search engines catching wind of the shenanigans and adapting accordingly.
Those specifications were dead on arrival. It's as idiotic as the "do not track me" option that most browsers have these days. Who the hell thinks of these things?
The same reason that doesn't work for sophisticated email harvesters.
Because I have empathy and also because this is very relevant to the deep web. I'm uncertain whether or not local or deep web content that links to the clearnet would necessarily send the information in question as part of the header given that it would be sourced from localhost, considering the obvious security breach that would pose. Then again, I wouldn't put it past popular browser vendors to be that retarded and/or intentionally malicious.
Remember when it was common for small website owners to share traffic with websites they actually liked instead of just websites that offered referral link shekels?