lemmy-meter.info just checks the landing page and the API responses for a community, post and comment, and just logs them over time. These are all things, irrc, Piefed’s API supports so I don’t know why the API needs to be expanded to log server stability? What does Mlem do to show instance stability?
Thank you for the explanation. Though I haven’t learned enough Swift to be working on the app’s code myself, I mostly just do testing after reading the commits and issues.
As you correctly observe below, we get uptime from lemmy-status.org, which doesn’t currently support Piefed. We do plan to expand this feature to Piefed, but it will require finding a new data provider and updating our code to process it, so our priority right now is adding support for features closer to the core interaction loop of the app.
lemmy-meter.info just checks the landing page and the API responses for a community, post and comment, and just logs them over time. These are all things, irrc, Piefed’s API supports so I don’t know why the API needs to be expanded to log server stability? What does Mlem do to show instance stability?
Thank you for the explanation. Though I haven’t learned enough Swift to be working on the app’s code myself, I mostly just do testing after reading the commits and issues.
@sjmarf@sh.itjust.works & @ericbandrews@lemmy.ml may be able to explain more in detail.
The Mlem details tab shows this page:
I did some digging through the repo and found they query https://lemmy-status.org/ for this info.
The Piefed instance settings are currently missing from the api.
As you correctly observe below, we get uptime from lemmy-status.org, which doesn’t currently support Piefed. We do plan to expand this feature to Piefed, but it will require finding a new data provider and updating our code to process it, so our priority right now is adding support for features closer to the core interaction loop of the app.