Hugo Dias

@hugomrdias

Joined on Dec 18, 2018

  • ![filecoin-logo](https://hackmd.io/_uploads/r1VBqDcvR.svg =100x) <span style="color:#D8DEE9" >Filecoin for dApps</span> Upgrading Filecoin support in the world of dApps. <small>https://hackmd.io/@hugomrdias/fildev2024</small> Note: We will go over the next wave of tools and integrations that will enable more developers to build on Filecoin and FEVM.
     Like  Bookmark
  • Connecting IPFS users and permissions to DIDs with UCAN ![](https://i.imgur.com/HzloABo.png =300x) IPFS þing - July 13, 2022 Note: How many of you know UCAN and DIDs? How can we bridge dids and ipfs data (CIDs) with UCANs
     Like  Bookmark
  • Exploring ways to improve IPNS! slides: https://hackmd.io/@hugodias/ipns Who are we? Hugo Dias & Adin Schmahmann Porto, Portugal & Boston, USA :heart: IPFS Core Developers :cat: Note:
     Like  Bookmark
  • Authors Hugo Dias Irakli Gozalishvili 0. Abstract UCAN.storage defines the UCAN protocol used by web3.storage and nft.storage. It inherits all the UCAN characteristics by just defining a specific set of capabilities and facts. Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
     Like  Bookmark
  • New runner for browser tests Slides: https://hackmd.io/@hugodias/playwright-test Who am I? Hugo Miguel Rodrigues Dias @hugomrdias Developer Experience SIG
     Like  Bookmark
  • # manual writing urls http://ipfs.io/ipfs/<HASH> http://ipfs.io/ipns/docs.ipfs.io http://<HASH>.ipfs.ipfs.io http://<HASH>.ipfs.dweb.link http://docs.ipfs.io.ipns.dweb.link # companion redirect http://192.0.0.1/ipfs/<HASH> http://<HASH>.ipfs.localhost opt-out: https://github.com/ipfs-shipyard/ipfs-companion#redirect-opt-out (https://docs.ipfs.io/#x-ipfs-companion-no-redirect) # manual daemon running http://<daemon gateway ip>/ipns/docs.ipfs.io/page1/index.html dns over https to cloudfla
     Like  Bookmark
  • # IPNS over DNS - two routers: one local and one internet connected - publish - ignore the dns local router for now - basic strategy its just publish to all available routers - use a --local experimental (or not) flag to enable the local dns router - parallel - resolve - parallel - return the first response - stream ? - options - alias - describe the name server as a multiaddr - support multiple in the next iteration - ipns subdomain just in the
     Like  Bookmark