[Feature request] Make "ping instances" check functionality

[KaKi87]

Hi,

Lots of services have a working homepage even when opening actual content pages doesn't work.

So, it would be nice for the "ping instances" feature to actually ensure that content pages open properly.

Thanks

[IkelAtomig]

First, instances doesn't work that way. During the ping, we can only get HTTP status 200, if the instance is running or turned off and the latency to reach instance from your ip and determine faster ones.

To find a way the ones that actually work. The instances need to have a standard API that reports their status, if it were there, we could consider implementing it ping check and only enable working instances.

[KaKi87]

That's fine. What I'm asking is to check that content pages return 200 instead of checking homepages.

For example, this AnonymousOverflow instance : https://ao.vern.cc

Appears to be working when looking at the homepage, but any content page, for example : https://ao.vern.cc/questions/43743250/using-libsodium-xchacha20-poly1305-for-large-files

Returns 504 after a long loading time.

Thanks

[KaKi87]

Hello,

Any news on this, please ? 🙏

Thanks

[IkelAtomig]

Appears to be working when looking at the homepage, but any content page, for example : https://ao.vern.cc/questions/43743250/using-libsodium-xchacha20-poly1305-for-large-files

In this case, I am not sure, how to fetch this and seems technically infeasible.

[KaKi87]

How so ?

If you can fetch the base URL, why couldn't you fetch a post path ?

[IkelAtomig]

1. I need to check if this error is still visible on http header (currently on mobile)
2. If needed, what I could think of another way is A sample URL, is picked for every problematic service. Then, when pinging, I do 2 checks

No. 1 - Base domain
No. 2 - The 2nd URL (sample URL), If possible only via HTTP header.

There are some services that display error in page but not in HTTP header. We need to be mindful of that.

---

I am kind of working with another person behind the scenes to make Mv3 as permissionless as possible and less invasive.

So you can doubt this coming in Mv2 or if ManeraKai (other lead dev) works on this.

P.S. The port to Mv3 is slow, so you can't expect it sooner.

As mentioned in mastodon, you can expect a new release if it urgent bug fixes are needed. Apart from that new functionality and frontends are released when we have time, merge it and release it.