On 7/24/17, David Spencer <baildon.resea...@googlemail.com> wrote:

> Fixed upstream just now
> Woo & YaY :D

Hurrah! Well played, sir!

Now all we need is a way for repology to check connectivity more
reliably. It thinks sites are down that just aren't, possibly due to
spotty routing in .ru, or evil firewall admins that block whole netblocks
when they get spam or exploit attempts from one IP in that block.

Whatever it's currently doing also seems to choke on https links if
the certificate's invalid. It'd be nice if repology actually reported
"bad SSL cert" instead of "can't connect".
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to