We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This relates to ipshipyard/waterworks-community#5 and discussion that has been had in Slack. IP Shipyard, as stewards of the ipfs.io gateway, wants to be able to show stakeholders longer-term trends on gateway usage and activity.
https://probelab.io/ipfsgateways/#daily-unique-clients-accessing-ipfsio--dweblink
Improvements needed:
https://probelab.io/ipfsgateways/#daily-http-requests-to-ipfsio--dweblink-by-region
There are likely other requested graphs in ipshipyard/waterworks-community#5 that may translate to Probelab requests.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Background
This relates to ipshipyard/waterworks-community#5 and discussion that has been had in Slack. IP Shipyard, as stewards of the ipfs.io gateway, wants to be able to show stakeholders longer-term trends on gateway usage and activity.
Specific asks
Unique Clients accessing ipfs.io / dweb.link
https://probelab.io/ipfsgateways/#daily-unique-clients-accessing-ipfsio--dweblink
Improvements needed:
HTTP Requests to ipfs.io / dweb.link, by region
https://probelab.io/ipfsgateways/#daily-http-requests-to-ipfsio--dweblink-by-region
Improvements needed:
Note
There are likely other requested graphs in ipshipyard/waterworks-community#5 that may translate to Probelab requests.
The text was updated successfully, but these errors were encountered: