Aman Singh Katal

I forgot to add that IPFS, supports, all content types From Images to direct .torrent files Everything described in all of our NIPs is supported by IPFS

i am not using chatgpt, i am using a translator AI, i do not speak english > We know what IPFS is. That's not the question. The question is how...

> The way to integrate IPFS with Nostr is easy. Just include a URL like `https:///ipfs/` > > This is backwards and forwards compatible. I've been doing it on Ditto:...

> The IPFS path gateway is standardized: https://docs.ipfs.tech/concepts/ipfs-gateway/#gateway-types > > This is superior to ipfs:// URIs because it works on the legacy web, AND ipfs enabled tools can resolve it....

> It sounds like what you want is Blossom. https://github.com/hzrd149/blossom doesn't sound decentralised, and requires always on server i assume

> The http url renders great on Amethyst. :) > >  Exactly, it renders good as long as gateway is up see this...

> Is there an Android app that serves IPFS images as a full node? If so, then we could just create a setting to load the image from the local...

I will start a pilot with **ipfs://** uri **_without changing NIP 01_** as suggest by @vitorpamplona i will talk to few clients devs to see if they can support this...

> The point of this long reply isn't to say that IPFS wont work or isn't a good system for censorship resistant media. but simply that we don't need a...

Maybe easier would be to introduce a new tag in https://github.com/nostr-protocol/nips?tab=readme-ov-file#standardized-tags ["ipfs", "img", "IPFS CID"] ["ipfs", "vid", "IPFS CID"] ["ipfs", "other", "IPFS CID"] This way it doesn't modify NIP 1,...