Well, that's good news, since it would make fixing the problem a lot easier. Here is my output from "ping lilypond.org", which definitely is trying to get something from Google: PING lilypond.org (35.206.114.173) 56(84) bytes of data. 64 bytes from 173.114.206.35.bc.googleusercontent.com (35.206.114.173): icmp_seq=1 ttl=99 time=312 ms 64 bytes from 173.114.206.35.bc.googleusercontent.com (35.206.114.173): icmp_seq=2 ttl=96 time=279 ms 64 bytes from 173.114.206.35.bc.googleusercontent.com (35.206.114.173): icmp_seq=3 ttl=99 time=339 ms 64 bytes from 173.114.206.35.bc.googleusercontent.com (35.206.114.173): icmp_seq=4 ttl=96 time=310 ms 64 bytes from 173.114.206.35.bc.googleusercontent.com (35.206.114.173): icmp_seq=5 ttl=96 time=311 ms
On Tue, Nov 2, 2021 at 5:13 PM Phil Holmes <[email protected]> wrote: > On 02/11/2021 12:53, Kevin Cole wrote: > > > > On Tue, Nov 2, 2021 at 6:42 AM Omid Mo'menzadeh <[email protected]> > wrote: > >> Hello all. >> I'm not sure if this is the right list to post this, but I'll give it a >> shot here, and see where I should report this. >> The problem seems to be the website's hosting, which appears to be >> provided by Google, which blocks access from certain countries in >> accordance with US law (with the error message "403. That’s an error. Your >> client does not have permission to get URL / from this server. That’s all >> we know."). This would not surprise me if LilyPond was not a GNU project, >> but it's a bit off at the moment, to say the least. >> What I would want to know if this is something the team cares about, and >> where I should discuss this. >> Thanks, >> Omid Momenzadeh >> > I could be mistaken -- I often am -- but... > > I suspect it's merely that the site is designed to construct search > queries using Google as the default search engine -- along with Google's > option to limit the search to a particular site. This saves the maintainers > from having to install a search engine and keep it updated. > > (One other negative consequence of this setup is that it randomly chooses > the version of documentation -- e.g. If I am on a .../doc/v2.20/... page > and search for a term, it will happily offer up a match from > .../doc/v2.22/..., .../doc/2.18/... or whatever else it finds.) > > No - it's hosted on Google currently. > > -- > > Phil Holmes >
