ipfs-webui VS ipfs

ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '["PUT", "POST"]' ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["http://192.168.77.214:5001", "http://localhost:3000", "http://127.0.0.1:5001", "https://webui.ipfs.io"]'

webui.ipfs.io

You could also do this: ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["http://IP_ADDRESS_OF_MY_PI:5001", "http://localhost:3000", "http://127.0.0.1:5001", "https://webui.ipfs.io"]' and ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '["PUT", "POST"]' ... again, I'm not on fire so obviously I didn't do this myself.

The webui has a pretty cool inspect function that visualizes the CID contents quite nicely.

Try the webui in a browser directly that used to work better for me than the electron wrapped webui. (https://webui.ipfs.io/)

Here is link number 1 - Previous text "bug"

(Low level local pins are not really useful for Desktop users, but since we support remote pinning since IPFS Desktop v0.15.0 and ipfs-webui v2.12 we show them for completeness :))

u/Amoreska do you mind providing more details in https://github.com/ipfs/ipfs-webui/issues/1793 ? Namely, your platform, desktop version + what you mean by "space cap" :)

> CDNs

If you think IPFS is trying to "re-spin CDNs as their invention", I'm pretty sure you misunderstand what IPFS. The homepage is a great starting point if you're curious rather than antagonistic: https://ipfs.tech/

> IPFS doesn't solve persistence of data

I don't think it claims to solve this either? What it does claim to solve is the persistence of identifiers of data.

> doesn't solve churn in p2p systems

What P2P system has ever done so or even claimed to have done so?

We will create a web app that will let users mint a NFT in one click: creating an AI art from a prompt, storing it on IPFS and mint the unique NFT in Polygon so you can see it on OpenSea. Pretty cool right ?

IPFS, which stands for Inter-Planetary File System, is a decentralized storage system where files are distributed among peers in a peer-to-peer (P2P) network. It operates on a "content addressable" model, meaning that each file is given a unique hash that serves as its identifier. By using this hash, you can retrieve any file from any IPFS node in the network.

Like this? https://ipfs.tech/

Was thinking of something and figured it would be a good opportunity to ask here. With the censorship madness going on in the world and furry community included, I often worry if even places like e621 can remain free and open in the face of increasing pressure by increasingly angry and authoritarian crowds. For both this and other geek reasons I've been interested in decentralized internet technology for a long time, following projects like IFPS which I just love as a concept.

Using the Interplanetary File System, a real thing that exists today, designed for this purpose.

I post a lot about IPFS, I was using the 'ipfs mount' to virtually offer my entire collection from my NAS (on a private 'swarm' of course) to the remote stations.