by tuanm on 5/13/2023, 6:31:21 AM
by outofpaper on 5/13/2023, 2:10:37 AM
This almost defeats the whole purpose of IPFS's automatic caching of resources. Using HTTP gateways is something anyone already can do in any browser and with a little work on the side of web devs can be done automatically. At the moment what's the point of using Durin?
by jeroenhd on 5/13/2023, 9:23:17 AM
Opening an IPNS domain in this app just takes me to a public resolver (ipns.4everland.io) in my browser rather than doing any IPFS work on my phone. Not very exciting to be honest.
by optimalsolver on 5/13/2023, 3:21:23 PM
Here for the name:
by hot_gril on 5/13/2023, 1:37:56 AM
I'm rarely interested in these things, but IPFS seems really nice as far as I've used it, and underrated too.
Was chatting with players of the niche open-source AssaultCube computer game, and turns out they have a not-so-great solution for custom map textures/models. Was thinking of dropping in an IPFS client for them.
by xrd on 5/13/2023, 11:44:13 AM
It's fascinating that iOS safari works correctly but not Chrome. I always assume iOS Safari will be crippled for anything innovative. Another nail in the Google coffin.
by transfire on 5/12/2023, 4:23:19 PM
Anyone use this yet?
by MadcapJake on 5/12/2023, 9:53:21 PM
Clicking links is taking me to my default browser.
Durin focuses on web3.storage gateway at this moment. AFAIK, using this provider requires the authorization for HTTP requests, also limits the storage usage, and ensures the content pinning feature. It doesn't seem to be a new thing added to the protocol but a mobile application supporting interacting with an IPFS gateway via HTTP requests. With current features I saw in Durin for Android, my uploaded content list isn't able to be synchronized across my devices. Anyway, it's prospective in bringing the protocol into mobile devices. Cannot wait to see how far we'll go.