psarm VS ipfs

Thanks for the thoughtful response! Many of these are totally legitimate: in particular, we're making steady progress to centralize module design, release, documentation, and modernization, or at least to bring many teams closer together. In many cases, we're at a transition point between moving from traditional PS remoting modules and filling out PS coverage for newer OAuth / REST API flows.

I don't know how recently you've tried PS7, but the back-compat (particularly on Windows) is much, much better[1]. And for those places where compatibility isn't there yet, if you're running on Windows, you can just `Import-Module -UseWindowsPowerShell FooModule` and it'll secretly load out-of-proc in Windows PS.

Unfortunately, the .NET problems are outside my area. I'm definitely not the expert, but I believe many of the decisions around the default assembly load context are integral to the refactoring of .NET Core/5+. We are looking into building a generalized assembly load context that allows for "module isolation", and I'd love to get a sense in the issue tracking that[2] whether or not fixing that would help solve some of the difficulties you're having in building modules.

For Azure, you should check out the PSArm[3] module that we just started shipping experimentally. It's basically a PS DSL around ARM templates, as someone who uses PS and writes the Azure JSON, you sound like the ideal target for it.

As for the help content, that's a very funny story for another time :D

[1]: https://aka.ms/psmodulecompat

[2]: https://github.com/PowerShell/PowerShell/issues/2083

[3]: https://github.com/powershell/psarm

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