protocol
Add table of all advertised stream handlers and how many peerid advertised thoses stream handlers.
I would like data like this:
| Stream Handler | Seen |
|---|---|
/ipfs/bitswap/1.0.0 |
123456 |
/ipfs/id/1.0.0 |
234567 |
Crawl from 2023-03-24 07:50:52 UTC:
| Stream Handler | Seen |
|---|---|
/ipfs/id/1.0.0 |
23491 |
/ipfs/id/push/1.0.0 |
23491 |
/ipfs/ping/1.0.0 |
23491 |
/ipfs/kad/1.0.0 |
23451 |
/libp2p/circuit/relay/0.1.0 |
23199 |
/p2p/id/delta/1.0.0 |
23110 |
/libp2p/autonat/1.0.0 |
22868 |
/libp2p/circuit/relay/0.2.0/stop |
21900 |
/ipfs/bitswap/1.1.0 |
21083 |
/ipfs/bitswap/1.0.0 |
21083 |
/ipfs/bitswap |
21083 |
/x/ |
21057 |
/ipfs/bitswap/1.2.0 |
20996 |
/ipfs/lan/kad/1.0.0 |
20969 |
/libp2p/circuit/relay/0.2.0/hop |
19853 |
/libp2p/dcutr |
19329 |
/floodsub/1.0.0 |
536 |
/meshsub/1.0.0 |
531 |
/meshsub/1.1.0 |
527 |
/sbptp/1.0.0 |
381 |
/libp2p/fetch/0.0.1 |
322 |
/sfst/1.0.0 |
79 |
/sfst/2.0.0 |
40 |
/ipfs/graphsync/2.0.0 |
18 |
/ipfs/graphsync/1.0.0 |
12 |
/fil/datatransfer/1.2.0 |
11 |
/fluence/particle/2.0.0 |
11 |
/fil/storage/transfer/1.0.0 |
10 |
/fil/kad/testnetnet/kad/1.0.0 |
8 |
/nunet/dms/chat/0.0.1 |
5 |
/nunet/dms/dht/0.0.1 |
5 |
/nunet/dms/depreq/0.0.1 |
5 |
/telemetry/telemetry/0.3.0 |
3 |
/telemetry/telemetry/0.5.0 |
3 |
/thread/0.0.1 |
3 |
/telemetry/download/0.3.0 |
2 |
/telemetry/upload/0.3.0 |
2 |
/btfs/lan/kad/1.0.0 |
2 |
/btfs/kad/1.0.0 |
2 |
/metap2p/messagereq/0.0.1 |
1 |
/planetr-func-run/1.0.0 |
1 |
/raft/1.0.0/rpc |
1 |
/textile/threads/2.0.0 |
1 |
/textile/cafe/1.0.0 |
1 |
/metap2p/handshakereq/0.0.1 |
1 |
/planetr-socks5-proxy/1.0.0 |
1 |
/metap2p/messageresp/0.0.1 |
1 |
/shsk/1.0.0 |
1 |
| ff86804e95810819a8c1eac23d1a0c303ae47afc07d89d12c684c28ff5fd68a7 | 1 |
/planetr-tcp-proxy/1.0.0 |
1 |
/sbst/1.0.0 |
1 |
/metap2p/handshakeresp/0.0.1 |
1 |
| wesign | 1 |
/strelayp/1.0.0 |
1 |
/metap2p/pingresp/0.0.1 |
1 |
/asmb/maons/1.0.0 |
1 |
/edgevpn/0.1 |
1 |
/metap2p/pingreq/0.0.1 |
1 |
/planetr-pod-get-info/1.0.0 |
1 |
crawled_peers |
dialable_peers |
undialable_peers |
|---|---|---|
| 26712 | 24096 | 2616 |
I guess this issue has been addressed. @Jorropo do you need this on a more permanent basis? If so, we should find a place to be reporting these
@yiannisbot for now I have all the info I needed :pray:.
I think it could be usefull in the future, right now it's fairly easy to track a feature adoption just by tracking the Kubo versions in user agent. But if more features become optional like graphsync current or more implementations starts being widespread, a table like this would be usefull.
We probably don't need it now tho, I think it would be fair to close this for now and waits for the second time someone asks for this make it permanent.
@yiannisbot for now I have all the info I needed :pray:.
I think it could be usefull in the future, right now it's fairly easy to track a feature adoption just by tracking the Kubo versions in user agent. But if more features become optional like graphsync current or more implementations starts being widespread, a table like this would be usefull.
We probably don't need it now tho, I think it would be fair to close this for now and waits for the second time someone asks for this make it permanent.
Edit: github have fun two general problem bugs where the UI send the same messages twice.
Just note that there is this graph in our weekly reports: https://github.com/protocol/network-measurements/blob/master/reports/2023/calendar-week-11/ipfs/README.md#protocols-1
It shows the 20 most popular advertised protocols
Oh I see.
It's quite unreadable, I think a log scale and more protocols would help.
I think this circle back into my other asks of "could you publish an sqlite or csvs of the data :pray: ?".