Systems like IPFS use hashes of data to reference content by itself, rather than by an arbitrary location/name.
Traditional identifiers are required in order to work with legacy URI systems like web browsers.
This poster should detail the work that relates to creating a bridge between these protocols. Such as the ipfs-companion browser extension.
Use whatever resources available to you, in order to come up with a visual representation of the topic that can be projected on to a poster (similar in spirit to the poster description but with whatever creative freedom your group prefers :^)
- What is the current state of dweb protocol and address handling in web browsers?
- What is needed for other vendors to implement support?
- How have IPFS nodes handled migrating to browser compatible addresses?
- What challenges have there been in handling compatibility?
https://github.com/ipfs/ipfs/issues/337
https://github.com/ipfs/in-web-browsers/blob/master/ADDRESSING.md
https://bugzilla.mozilla.org/show_bug.cgi?id=1428446
https://github.com/ipfs/in-web-browsers/issues/147
https://bugs.chromium.org/p/chromium/issues/detail?id=64100
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/29sFh4tTdcs
whatwg/html#3936
https://github.com/ipfs/specs/tree/master/dweb-addressing
