Marcin Rataj

Meant user being in control of which gateway is used :)

The idea of "pet names" was part of https://github.com/ipfs-shipyard/ipfs-webui/issues/891 but only "Add connection" button was added to the Peers screen. Labeling peers was descoped because while we could implement it...

This is blocked until high level API support for peerstore metadata is present in both js-ipfs and go-ipfs (like https://github.com/ipfs-shipyard/ipfs-webui/issues/1018#issuecomment-610623276 or even more generic kv approach).

Good arguments, especially the one about [GoogleSafeBrowsing](https://safebrowsing.google.com/)'s false-positives for public gateways 👍 CIDv1 format is strongly related to discussion at [ipfs/in-web-browsers: Tackle identifying origins with (or without?) fs: paths](https://github.com/ipfs/in-web-browsers/issues/6). I...

Some cool mockups from https://github.com/ipfs-shipyard/ipfs-webui/pull/1062#issuecomment-508318007 (Peers screen): > @lidel We can pull the colors from the theme.json in `ipfs-css`, but we can't generate the icons in CSS. > > Here's...

Thanks! Hashicon playground at https://etcdevteam.github.io/hashicon/examples/ is pretty good:  What I meant by fungible library is that we could tweak hashicon aspect ratio to produce symmetric hexagons (matching IPFS logo)....

Relevant, for future reference, sigils from Urbit: https://urbit.org/blog/creating-sigils/

While https://github.com/ipfs-shipyard/ipfs-webui/pull/1069 introduced generic identicons on _Peers_ screen, we do not show it on _Status_, nor use IPFS-specific graphics (see discussion and examples above). I also had this idea of...

PerCID (https://percid.va.gg) by @rvagg is server-side generated, but fun and worth honorary mention here: > [](https://percid.va.gg/#bafkreifxsq4f6li666vu3ett2gighanuj4xw6jmiupx3s2sjdcbtdgchkm) > @lidel got a cursed one on the first try...

Related prior art: visualizing the DHT lookup http://research.protocol.ai.ipns.localhost:8080/blog/2021/a-visualization-tool-for-the-ipfs-dht/