The cloudflare filter has been added back into the nightly build. Now
that the filtering method uses direct querying of the instance IP(s), it
should be more reliable than the namespace lookup (and more accurate).
services.json has been updated with the latest filtered results from
services-full.json as well.
The previous approach to filtering cloudflare instances was checking if
cloudflare nameservers were assigned to that domain. I believe this was
too harsh of a filter, as quite a few instances were removed even though
they were not using cloudflare's proxying feature.
To solve this, the filtering script has been updated to manually fetch
each IP associated with a domain and see if it returns the 1003 error
that cloudflare proxied sites return when queried directly.
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.
