Marcin Rataj

I am not aware of anyone using `Pin.meta` field yet, (go-ipfs does not use it), so appreciate you looking at this :+1: Quick pointers if someone has time to investigate...

@sanderpick I don't think we need to change anything in the YAML used for generating the client (we are already use [suggested YAML for JSON object in query params](https://swagger.io/docs/specification/describing-parameters/#schema-vs-content)), but...

@willscott there should be `routing_http_client_length` – 0 means IPNI returned no results: https://github.com/ipfs/boxo/blob/abced78b8563adbe04631889d1eddfe7890a4088/routing/http/client/measures.go#L20 Is this broken / not enough?

I believe this can be closed: https://github.com/ipfs/go-ipfs-blockstore/pull/38 shipped and depending on context, we switched to multihash (datastore keys) or CIDv1 with `raw` codec (`refs local` output)

Hm.. need to decide on the resolution we want to operate at. Something like https://libp2p.io/implementations/ with discrete features such as - "Block" "CAR" "libp2p" "DCUtR" "Public DHT Client/Server aka kad...

I believe this will become much more relevant when "pinning API changes" land in WebUI. People will be able to easily pin website data to remote nodes to keep them...

Another engine for automated Web UI testing: https://github.com/dequelabs/axe-core#axe-core

ipfs-webui getting a11y treatment and automated checks in https://github.com/ipfs-shipyard/ipfs-webui/pull/1512 :rocket:

Here's an idea: how about making "Cluster UI" a proof-of-concept of the "WebUI Add-on Apps" Juan mentioned in recent conversations?

Ok, so it seems we agree the minimal set for front page is more or less (1,4,7) presented in text form: - Peer ID - Agent Version - Node state...