Hmm, that is really strange since it means that the call is happening and correctly returning. Does anything interesting show up in the console when you visit that page?

I wondered if maybe there was a problem with IPFS Desktop or some rendering difference in Chromium but testing both of those here, they still work.

If the feature is unreliable, it could be removed, but I am really confused by what is going on and I wonder if there is _some_ issue which is just manifesting this way. I could provide a special testing build so you could get more information, on your side, if you felt like helping me dig into this. I know that is a labour-intensive imposition, so I suspect that is a bridge too far.

It is too bad that their API server for some reason requires all methods to use "POST", meaning you can't easily just get your browser to ask IPFS, directly. If it were a Linux box, it could be checked with "curl -XPOST http://127.0.0.1:5001/api/v0/diag/sys?stream-channels=true", since that is all Cacophony is doing.

Hmm, looking into it, I see conflicting information about whether or not curl is a default part of Windows, starting with Windows 10, so maybe that command would work, just in a standalone command prompt.