• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • The reason I’m saying use a VPN is because you’re presumably visiting the site anyway, so leaking your full IP to them anyway. You can route your DNS lookups through what server you like, obviously. (Again, the privacy issue would be not that you’re leaking part of your IP to archive.is, but to everyone in the chain of recursive DNS resolvers). You could use TOR too, I think even in this thread someone posted a TOR url for it.

    Cloudflare do make the DNS queries from 1 of their 180 locations, so there is some information being passed through about where the request is coming from in terms of load balancing.

    I’m not arguing that Cloudflare are doing the wrong thing by omitting ECS data in general. Just that site owners have a right to do as they like WRT people using their website and if that includes blocking Cloudflare, so be it. What he is doing is not legal (or at least grey area) in many countries so anything that makes his life easier is understandable IMO.

    Also, ECS leaking does not seem like a real concern for the vast majority of people surfing the net.

    Lastly I don’t think Google own 4.4.4.4, did you mean 8.8.4.4?




  • It’s way faster for one. It actively scrapes articles from behind paywalls, using a bank of credentials it has. Archive.org respects robots.txt and will take down copyrighted material on request. Archive.is doesn’t do any of that.

    I would view it as complementary to archive.org. it’s more like sci-hub to me. A useful tool, run by one person who likes the idea of providing such a service.

    What exactly do you think is being tracked by your ECS being sent along with DNS requests? All it means is that archive.is can’t load balance properly because they don’t know what their nearest server to your location is. If you’re so privacy conscious that leaking a portion of your IP to a DNS provider, then hardcode archive.is IPs into your hosts file or use a VPN. Not that your problem can really be with archive.is, because you’re visiting the site anyway, giving them your full IP.

    It just seems like such a non issue to me.





  • Speed of development. It could take months for a PR to get into Lemmy core and then a new release.

    Things that get into Lemmy core have to be well thought out and the core Devs have to want them in there.

    Running custom code is a way to make changes without having to get their approval, and if it proves popular enough, then maybe they’ll implement it upstream.