Skip to main content
100%

Gist 856f34e76a439df2c77e4585cc17d659

✓ Published0🌍 Public
Aandrewxhill
Last edited Apr 5, 2019
Created on Apr 5, 2019

This visualization tests the availability and response times of 19 public IPFS gateways by repeatedly pinning random-content files to a local peer and requesting them through each gateway. It measures either the HTTP status code or elapsed request time (in seconds) for every attempt, with timeouts recorded as 9999 and non-200 responses stored as their status code. The code uses the `ipfsapi` Python library to add files to a local IPFS node and the `requests` library to perform timed HTTP GET requests against each gateway URL. Results are printed as tuples of gateway name, time/status, and the content hash, revealing which gateways are fastest, slowest, or failing entirely.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 1e7ec4d379a1e6a16c5277c92d626b4f

This visualization demonstrates the Powergate stack for Filecoin API management, showing how components like reputation indices, wallet management, and the FFS system coordinate network activity. It uses a CLI demo video embedded via an HTML5 player, with the gRPC API layer visible in the linked `.proto` files. The data sources include miner activity, slashing events, and deal information collected from the Filecoin network. The example relies on standard web technologies—HTML video playback and embedded media—rather than a specific JavaScript visualization library, focusing instead on the interactive deal management and configuration workflow.

Aandrewxhill
60% match
Loading thumbnail…

Gist 3588675371923377e776ce4856ed20c5

This interactive visualization maps a network of HTTP and API development tools, drawing nodes and links from a Markdown file that lists GitHub repositories. Using a force-directed layout, it clusters projects like `httpexpect`, `acme-dns`, and `space-cloud` to reveal relationships between mocking, testing, and live-relay utilities. The graph employs `d3.forceSimulation` for physics-based positioning and `d3.geoPath` to render the connecting edges, with node size and color encoding repository activity. The data source is the apifoo.md file contents.

Aallyraza
59% match
Loading thumbnail…

Gist API Latency

This histogram visualizes the distribution of GitHub Gist API response times in milliseconds for 10,000 requests, broken down by endpoint type: single-gist queries (light blue) versus user-gist listings (dark blue). The stacked bars reveal that the slow tail of the distribution comes almost entirely from the listing endpoint. The chart is rendered as SVG using D3 v3, with `d3.scale.linear`, `d3.svg.axis`, and data loaded from a TSV file via `d3.tsv`. Axis labels and percentage annotations are drawn using SVG text elements.

Mmbostock
59% match
Loading thumbnail…

Gist 4b02d1558eb34ecad764c3ccf5289600

This example demonstrates a web interface for managing decentralized file storage on Filecoin, showing how users interact with a bridge API to store, deposit, release, and check the status of files. The code uses React hooks like `useState` and calls to a custom `api` object with methods such as `.store()`, `.addDeposit()`, `.releaseDeposit()`, and `.status()`, which handle file uploads, bridge deposits, fund releases, and deal status queries. Uploads are tracked in a state array, and responses include IPFS CIDs, while alerts and console warnings report errors or confirm actions. The visualization relies on the API's JSON responses rather than a rendering library.

Aandrewxhill
59% match
Loading thumbnail…

Gist 32c349dbe43e41e4653eb958d4b9a667

This visualization checks the availability of open geographic data files from the French National Institute of Geographic and Forest Information (IGN) by scraping their data download page for FTP/HTTP links to .zip and .7z archives, then using cURL to send HEAD requests to each URL. For every file, it records the HTTP/FTP status line or the Last-Modified header returned by the server, and then filters out entries that do not return “HTTP/1.1 200 OK” or a Last-Modified header, leaving a list of URLs with errors. The result is a simple diagnostic dataset showing which IGN data downloads are broken or unavailable, useful for monitoring the availability of open geographic datasets. The visualization is essentially a status report, listing failed URLs and their corresponding error messages or missing headers.

TThomasG77
58% match
Loading thumbnail…

Gist 449f03e29089da44d87837c741ee51b3

This example visualizes pairwise round-trip times between PlanetLab hosts, plotting measured latency against geographic distance. It shows scatterplots and cumulative distribution functions for two measurement sets taken at different times of day, revealing the relationship between network delay and physical separation. The code uses gnuplot to render the graphs, while Perl scripts compute great-circle distances from latitude/longitude coordinates. Ping commands with ten packets per host pair generate the underlying latency data.

Aallyraza
57% match
Loading thumbnail…

Gist 1075489a3f6f94d13b2ab76cff4c7cea

This example visualizes the asynchronous execution order of Node.js operations by logging their completion times relative to a shared start timestamp. It uses Node’s `https.request` to fetch Google’s homepage, `crypto.pbkdf2` for four CPU-intensive password hashes, and `fs.readFile` to read a local file. The console output reveals how the event loop interleaves I/O callbacks, with the network request finishing before the file read and hash computations, illustrating the non-blocking concurrency model.

Aamazingandyyy
57% match
Loading thumbnail…

Gist 1074953

This example demonstrates server-side request benchmarking and logging through real-time socket events. The code uses the `GO.aop` aspect-oriented programming module to intercept controller execution, measuring rendering time with the `GO.time` vendor library. Each HTTP request triggers two socket emissions: one reports the page render duration via a benchmark message, while the other logs Apache-style visit details including the URL and user-agent. Data is transmitted through `GO.Socket.emit` with timestamps and unique identifiers generated by `GO.utils.uid`.

Aalessioalex
56% match