can't they just put all the quotes on wikipedia or twitter or something
It's all on archive.org
Tell HN: Bash.org is no more
341–344 of 344 posts
Re: Tell HN: Bash.org is no more
#342Earlier quoted context omitted.
Is it? It was its own private entity and now it's offline probably forever. Edit: I think it'd be far better off on Wikipedia than Twitter
https://news.ycombinator.com/item?id=38950912 Mirrors still exist (Also, Twitter already deleted old data, so these quotes wouldn't be much safer there)
Backed up on centralized gitlab and centralized archive.org, huh?
My point is that the comment was praising independent services when it doesn't make sense: bash.org, the independent service, shutting down and people want to store backups in a more trustworthy centralized service, much like the two backups you linked.
Re: Tell HN: Bash.org is no more
#343Earlier quoted context omitted.
Works for me. Do note that archive.is blocks CloudFlare DNS.
This has bitten me before; now my pihole has this line in its dnsmasq configuration server=/archive.is/archive.ph/8.8.8.8 so that even if I'm using cloudflare dns for everything else, it will query 8.8.8.8 for those two domains
Gonna go out on a limb and agree with the archive.is owner -- the reason he blocks it is bc cloudflare intentionally doesn't support edns client subnet. They cite privacy reasons, but it comes at the at the cost of performance -- most cdns use DNS based routing, so using cloudflare DNS means you connect to random server for a lot of websites. CloudFlare on the other hand uses anycast routing for their CDN, so they don't suffer at all.
I hate Google but my pihole is configured to use their DNS resolvers. Lesser of two evils.
Re: Tell HN: Bash.org is no more
#344Earlier quoted context omitted.
This has bitten me before; now my pihole has this line in its dnsmasq configuration server=/archive.is/archive.ph/8.8.8.8 so that even if I'm using cloudflare dns for everything else, it will query 8.8.8.8 for those two domains
Gonna go out on a limb and agree with the archive.is owner -- the reason he blocks it is bc cloudflare intentionally doesn't support edns client subnet. They cite privacy reasons, but it comes at the at the cost of performance -- most cdns use DNS based routing, so using cloudflare DNS means you connect to random server for a lot of websites. CloudFlare on the other hand uses anycast routing for their CDN, so they do…
It shouldn't be that bad, CloudFlare's anycast should direct you to a nearby resolver, and doing your GeoDNS on that resolver IP instead of ECS is probably not that much worse than doing it on the actual client IP. Both approaches aren't great at picking an ideal CDN node, GeoIP is notoriously unreliable, and it tells you nothing about network topology.
Breaking DNS entirely is much worse behaviour, especially because GeoDNS itself is arguably not in the spirit of DNS which is distributing a consistent database, not making it up on the fly based on the client's info. The archive.is admin is being ridiculous, the least they could do is block anyone not using a resolver supporting ECS to be consistent, but no they have something personal against Cloudflare.