Also removes bibliogram from the auto-updater
Bibliogram is discontinued, and many instances are going offline as a
result. This clears out the ones that have already been deactivated, but
the better solution would probably be to stop supporting bibliogram.
User profile pages are no longer accessible from Bibliogram. This should
be addressed by Farside at some point, but for now, we should at least
be checking if posts are accessible for a particular instance.
Closes#63
The bibliogram.privacydev.net instance has been removed, as it doesn't
actually redirect to a bibliogram instance. The site it redirects to,
imginn, does work as an instagram alternative, but has not been vetted
and should not be used by Farside as a drop-in replacement for
bibliogram yet.
Closes#61
The cloudflare filter, when performed as part of the github action
workflow, doesn't seem to work nearly as reliably when run on an actual
machine.
The farside server will instead run the un-cloudflare script whenever it
pulls in new changes to services-full.json, which should be a much more
reliable approach to filtering out cloudflare instances.
If dig returns exit code 9 (no reply from server) when checking an
instance for cloudflare records, it shouldn't fail the CI build but
rather just skip adding the instance to the non-cloudflare services
list.
This should be re-evaluated soon to see if the CI build routinely has
issues with getting a server reply. If so, a different approach needs to
be taken to check if an instance is using cloudflare.