zlacker

>>stargr+(OP)
I'm with some of the people on Twitter: It seems weird (to put it mildly) to just blackhole your own site with no explanation whatsoever to the end-user. For everyone on 1.1.1.1 archive.is will now be "down" and they're none the wiser.

Maybe there's a big backstory here, but without context that seems passive-aggressive and quite random?

>>darkla+r3
Indeed. This is the first I'd heard of this situation. I'd previously just assumed archive.is was a shonky service that didn't work properly. Hadn't connected it with my use of 1.1.1.1