dat VS ipfs

I'm surprised you didn't include things like `dat`[0]

[0] https://github.com/dat-ecosystem-archive/dat

Gun is an opinionated high level and complete solution, it may provide more than what you need. I would think a more modular alternative is suitable, something like using libp2p. Anyway, you should take a look at the dat ecosystem and the ipfs ecosystem. Also, a really neat and clever way to simply do distributed peer discovery, removing the need for a signalling server, is bitboot (it uses mainline DHT).

Dat/Hypercore lets people share data with others, and you can build applications on top of it

> 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 ?

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.

I've been on the IPFS bandwagon for a while.

This looks pretty promising; I am assuming this is what you are talking about? https://ipfs.tech/

When first moving it to something new, ever considered https://ipfs.tech/ ? I wonder what the pain points would be making an imgur like system on top of that.

If you want it generally available, IPFS is a nice option. Then any other hoarders that pin/cache the data act as +1 source, similar but different to torrents. There are public gateways but they can get hammered with heavy traffic and aren't always the best.

> Is this meant to be understood by geniuses or something?

Nope; anyone who has some basic programming knowledge and perhaps a high level understanding about how different programming languages work. And the ability to connect some dots together.

> “it’s JSON with types and functions and hashed references”

Another way to say this: it's executable YAML, which is a strict superset of JSON [1]. I like YAML, so that's what came to mind when looking at ScrapScript code. I also like clean, minimal syntax when I can get it, like YAML, CoffeeScript or Haml.

> “it’s a language with a weird IPFS thing”

I’ve been playing with IPFS [2] since its early days in 2015, though not much recently, though this will probably get me back into it. Content addressing solves a lot of problems that I won’t get into here but it’s certainly not that hard to grasp. IPFS is available for pretty much every browser these days and is integrated into the Brave browser [3].

> all programs are data

This concept has been around since the creation of Lisp in the 1950's. This enables all kinds of cool features the computer science types get excited about. I've known about this concept since the 80's when I used to teach kids Logo (which is a Lisp). The term used nowadays is homoiconicity [4] but that term wasn't in widespread use until fairly recently.

Bottom line: ScrapScript sounds very interesting and I'm looking forward to checking it out.

[1]: https://yaml.org/spec/1.2.2/#12-yaml-history

[2]: https://ipfs.tech

[3]: https://brave.com/brave-integrates-ipfs/

[4]: https://en.wikipedia.org/wiki/Homoiconicity

IPFS is like an open-source CDN (content delivery network).