IPFS Thread

IPFS dedicated thread. ITT we discuss IPFS, share IPNS websites, publish own sites, share helpful links, Q&A. Q: What is an IPFS? A: Inter-Planetary File System. p2p decentralized. Q: How is it better or different from other alternatives? A: It gained some tracktion & adoption, in comparison with less popular alternatives. It is open source & ready to use. Q: What is IPNS & how does it work? A: IPNS is a sort what decentralized domain name hash to a web page. When you publish an web page, document, in IPFS it become reacheable via unique hash, however if you update document, hash changes, IPNS aims to resolve this. In http://www. pages, domains, url links get removed. In IPFS they are supposed to be stored permanently. in order to use IPFS you need an IPFS compatible web browser, extension, and better run your local node/resolver. URLs: https://ipfs.tech ipns://ipfs.tech

some links ipfs://vitalik.eth ipfs://amoebacore.eth ipns://k51qzi5uqu5dk8jpgw2ga3qoit4k9ocb328w8mxqlnw36k4m8ebt43ngmonioc/ IPFS doesn't nor require a crypto blockchain. Common sites, pages in IPFS are basic HTML+CSS are in spirit of classic web1.0, gemini, gopher. And not bloated with overloaded front-end frameworks. A dynamic content is possible to publish. things to look for: IPFS search engine, webring of IPFS sites. Maybe we could make Lainchan ipfs webring?

>>86480 Can I route IPFS traffic through Tor?

>>86489 If you really want, in theory! You can easily find 3rd party unofficial tutorials for that, on search engine. But "officially" (on github Issues) not (yet). Since it was made without anonymity goal in mind, in the beginning. Like still many other software, that been made without anonymity goal, that still usable : torrent, ceph, irc ... etc you can implement & commit code changes, to resolve this issue, if you are a developer. I don't want to derange this thread, in to discussing infinite 3rd party integration issues. Because I do want to focus on limited implemented features that should work (and still deserve some research).

how does the architecture of distributed web3 back-end works, designed? when html document get published on IPFS, it's just an static html document. If you need to publish future editorial changes to your html document, it could be referenced by IPNS. but what aboud publishing dynamic web3 app? which part of CLIENT software, of ipfs/web3 stack can serve distributed computations (like apache mod_php, node.js) ? and what part of this stack is distributed database cluster replicated & served by p2p client nodes?

>>86723 orbit-db was recently revived and has https://api.orbitdb.org/module-Sync.html with this https://github.com/orbitdb/orbitdb/blob/main/docs/CONNECTING_PEERS.md#browser-to-browser-and-node-daemon-to-browser its absolutely frosty can also plugin in ethereum ecdsa stuff to control commits to the db really cool

ipfs is real cool but after i install it i don't know what to do next. i got big buck bunny off it which was fire

>>86480 There's also a bunch of tools to deploy websites on IPFS: https://blumen.stauro.dev https://orbiter.host And the official https://github.com/ipshipyard/ipfs-deploy-action