I’m working on lemmy-meter which is a simple observability solution for Lemmy end-users like me, to be able to check the health of a few endpoints of their favourite instance in a visually pleasing way.
👉 You can check out a screenshot of the pre-release landing page.
💡 Currently, lemmy-meter sends 33 HTTP GET requests per minute to a given instance.
For a few reasons, I don’t wish lemmy-meter to cause any unwanted extra load on Lemmy instances.
As such I’d like it be an opt-in solution, ie a given instance’s admin(s) should decide whether they want their instance to be included in lemmy-meter’s reports.
❓ Now, assuming I’ve got a list of instances to begin w/, what’s the best way to reach out to the admins wrt lemmy-meter?
PS: The idea occurred to me after a discussion RE momentary outages.
Each server would have its own acceptable use policy. Also consider the social detriment of Cloudflare nodes. We could even say @[email protected] has a moral /duty/ to overwork the Cloudflare nodes :)
@[email protected]: thanks for pointing out lestat. That’s one of the very few services of this kind to be responsible enough to red-flag the Cloudflare nodes. I hope @[email protected] follows that example; though it could still be improved on.
It’s misleading for any tor-blocking Cloudflare node to have a 100% availability stat just because by design it deliberately breaks availability to a number of users in an arbitrarily discriminatory fashion. https://lemmy-status.org/ and https://lemmy.fediverse.observer/stats do a bit of a disservice by not omitting or flagging #Cloudflare nodes.