This project is building on Fleek now, but to host it there we need to update the DNS.

Fleek expects to see a CNAME record for dag.ipfs.io to 634c28dae701e8ca2e20.b-cdn.net.

The hold up is this requires us to delete the existing dag.ipfs.io zone from dnsimple and then update the ipfs.io zone to include the CNAME. Dnsimple does not support creating that CNAME from the dag.ipfs.io zone.

The site is already building to http://634c28dae701e8ca2e20.b-cdn.net/

@achingbrain gave feedback that it would be useful to visualise from an existing CID (as well as drop/select file).

Loading big graphs is really slow because the UI waits for the whole thing to be loaded before rendering - could it add nodes to the graph as they come in instead?

Currently not shown.

#6 (comment)

When adding a file to https://dag.ipfs.tech, the CID at the bottom links to https://cid.ipfs.io still. The IPFS logo in the top-left also still links to https://ipfs.io

Currently in Safari drop area is not full screen height

I was playing around with dag.ipfs.io and I noticed the number of children on the graph is not getting updated. Initially the graph is set to 11 children. However, it is always shown with 174 children.

I was able to reproduce it in Chrome and Firefox, and also locally by cloning the repo.

Here are some screenshots:

Also tried locally on commit 430f648 and it worked all fine. It seems the last commit broke things.

The file used is QmcXVBPfq7jNjRd13BmRkJoobHw4KU4RnD5GSySnk36UWU but behaves the same with different files.

Implement metrics in this project

• #38
• #39

Additional context

• ipfs/ipfs-gui#105
• ipfs/ipfs-gui#117
• https://github.com/ipfs-shipyard/ignite-metrics/blob/main/docs/telemetry/COLLECTION_POLICY.md

Currently you have to drop files one at a time - it would be good if you could drop a directory.

#6 (comment)

I'm trying to analyse some real-world DAGs and the nodes end up being teeny-tiny - I can pan around but some way of zooming in and out would be great:

The line halfway down is a DAG..

I think intro text would help make this even better as a standalone learning experience, in 2 areas:

1. What does this thing do?

It could take a few forms. In order of my personal preference:

• small section that's visible by default, and doesn't impede usage of visualizer, but can be dismissed via click or scroll
• in the header, always visible
• triggered by a help or about link
• splash screen upon first load

Here's a first pass of the text, interested in comments!

"DAGs (directed acyclic graphics) are the core data structure of IPFS. They enable efficient data verification and management. Upload a file, then click menu options to explore the different ways that file can be split up into chunks."

2. What do these things mean?

The menu options might also benefit from some description. Example below:

Add telemetry according to ipfs/ipfs-gui#105.

See ipfs/ipfs-gui#105 (comment) for more
details about why there is no UI treatment.

Users will be able to opt out by executing the function removeMetricsConsent in their browser console: removeMetricsConsent(). They can re-add consent using addMetricsConsent().

A neat feature would be to add a button that will return the command used for the options selected. This would serve multiple purposes:

• It would be nice to see a live example of what some of the available commands on the CLI are.
• It would help tie in Explore.ipld.io, dag.ipfs.tech & cid.ipfs.tech
• This will help create tutorials and help users understand the basics of what happens when a file gets added to IPFS.

I want to take the CID from dag.ipfs.tech to explore.ipld.io and look at the data there. If I knew the exact command then I could add it to ipfs on my own machine and see it later on the explore site. This would make it easier to explain the different block/dag altering options there are, how the data format looks, and how the CIDs also change.

cc @lidel @SgtPooki @aschmahmann

Steps to produce:

1. Upload a file (https://user-images.githubusercontent.com/305332/60381585-735fc800-9a57-11e9-906f-29db82f57e55.jpg)
2. Change chunk size to 32 bytes
3. Change to flag dag format
4. Move the root away from it's default location and observe the links being stuck in place without following the root node representation.

What I saw:

This is using MacOS 10.14.5 (18F132) using Chrome Version 72.0.3626.121 (Official Build) (64-bit).

Originally opened by @pranshuchittora in ipfs-inactive/website#407 ... quoted below:

Hi, I am not able to find the repo for the dag.ipfs.io so opening the issue here.

While tinkering with the DAG I found out that the source maps are being shipped @prod.

Just CRA things :)

ipfs-inactive/website#407 (comment)