@resist1984 Hackers! There's a company out there that asks to be tought a lesson.
@resist1984 One reason more to use Cloudflare.The wayback machine keeps data from all websites forever.Maybe it's interesting history for some public information but they also save social media,forums,everyone you ever wrote with no way to delete it.That's pure evil.
I think it was later clarified, that it meant retrospect deletion.
Before the change the wayback machine had the problem that when someone new bought the domain and restricted the access via robots.txt, the whole archive of the site of the previous owner was deleted.
This was not only bad because of accidental deletion, but people could even intentionally destroy parts of the archive by buying old domains.
For just denying access to the archive bot have a look at the "noarchive" flag.
@nedelne_rano @resist1984 @frommMoritz There's a big difference in making content searchable or cloning it completely forever.If it's in the search and the author decides to delete it,search links will return Error 404 after clicking it.Yes,there may be some other cache but I'm talking about pure search results.This isn't problematic.If you delete it and there's an exact copy of the page which isnt removed,this is a problem in some cases.
wayback machine respects robots.
And claiming that it is "one more reason to use cloudflare" is kinda wierd.
And yes, you can get your site removed from wayback machine.
If you don't want your information public, don't make it public. Facebook already disallows crawling, so does Twitter, by the way. So your point is mostly moot anyway.
CloudFlare unilaterally deciding to screw over one of the main projects keeping Internet history is not that balance.
@Mr_Teatime @nipos the Firefox plugin that redirects CF sites is called "Block Cloudflare MITM Attack" and is posted here: https://addons.mozilla.org/en-US/firefox/user/14218621/. Description is in cyrillic but don't let that scare you off. This plugin will outright block CF sites: https://gitlab.com/gkrishnaks/cloud-firewall
@g at a high level, #CloudFlare is very similar to #SpamHaus. In both cases you have a vigilante extremist org so fixated on attacking their enemy that they have no regard for collateral damage to harmless users. Ppl cannot protect their own #privacy by running their own mail server b/c of SpamHaus, & ppl cannot protect their own identity b/c CF DoS's *all* #Tor users.
@g this article covers it in detail: http://cryto.net/~joepie91/blog/2016/07/14/cloudflare-we-have-a-problem/
@g np. And note there may or may not be a 2nd tunnel between the originating server & CF, but in either case the end user sees a padlock
So if I have a SSL certificate from Let's Encrypt setup, but still sit behind Cloudflare, is my data still compromised?
@resist1984 oh well, I guess it's time to fry all electronics and start over.
One of these days someone truly malicious is going to just blow up all the computers, don't you think?
@resist1984 I know why I never liked them...
@resist1984 Works here without. Seems it's triggered under certain conditions.. https://support.cloudflare.com/hc/en-us/articles/200170136-Understanding-Cloudflare-Captcha
I recently read an article about how those #CAPTCHA things that ask you to do stuff like, "Click all the boxes that have cars" actually have much less to do with proving you're human than with training various AI products to better recognize things in photos. Basically they're outsourcing their AI training to the public and falsely framing it as a security mechanism. It might have been Edward Snowden's book, I'm not sure.
@gerowen indeed, #Google is using #CAPTCHA to exploit labor, which in some situations in the US amounts to a 13th amendment issue (involuntary servitude). Google's CAPTCHA also gives preferential treatment to logged in Google users, which adds to the tracking of those users by associating them to the site where the captcha is presented.