Improved debugging facilities

Some common issues include:
Determining a node’s reachability (both from fully-featured nodes and browser nodes)
Determining if content has been advertised

Most of the work here will likely come from with kubo/boxo, but surfacing to users via WebUI (bundled with kubo) or IPFS Desktop (where users are likely even less equipped to deal with errors) seems valuable in reducing bounce-rate and unactionable bug reports.

Deliverable:

• Linking to https://check.ipfs.network/?cid= from https://explore.ipld.io/ and https://cid.ipfs.tech/
• Adding Diagnostic Screen to Web UI / IPFS Desktop
  • Two sections:
    • Logs Screen: leverage Kubo RPC /api/v0/log/tail + improve it to allow for real-time changes of log level per system and globally
    • Connectivity Check Screen: embed https://check.ipfs.network UI (use our backend, allow user to adjust if they want)

ETA

Q2-Q3 (depends on ordering with providing system)

Expected impact

Making debugging easier and more self-service reduces strain on maintainers by helping users solve their own issues and/or make more informed bug reports. If done well, it also helps people learn more about the stack and makes it easier for people to contribute within the ecosystem.