cloudflare-docs VS ipfs

Slightly related - CloudFlare account_id and zone_id are safe to be public

https://github.com/cloudflare/cloudflare-docs/issues/474

https://community.cloudflare.com/t/api-zone-id/355566

> The Zone ID and Account ID are not sensitive. Sensitive data like account API Key, Secrets etc. can all be revoked, rotated or changed. See the comment 36 below on the Wrangler repo: as per our security team, it’s completely Fine to have your zone_id and account_id public, the Global API key and associated email address should be kept secret.

I have created an issue in their docs repository to address that misleading statement.

I don't strictly know if this is related, but the terms are being revised due to the release of R2: https://github.com/cloudflare/cloudflare-docs/issues/7186

CloudFlare cannot protect applications that use # in URLS: https://github.com/cloudflare/cloudflare-docs/issues/7062

https://www.youtube.com/watch?v=KMEgJRqYzzg https://www.youtube.com/watch?v=QcXmGQqtUn0 https://www.youtube.com/watch?v=5dkzFrJ044o https://www.youtube.com/watch?v=48NWaLkDcME https://www.youtube.com/watch?v=4lGzIZqVN8Q https://www.smashingmagazine.com/ https://www.cloudflare.com/ https://prerender.io/ https://developers.cloudflare.com/

You can check the changes here: https://github.com/cloudflare/cloudflare-docs/commits/produc...

We're working on the documentation, I agree it can certainly be thin (or just not understandable). Please do file an issue for any improvements you'd like to see: https://github.com/cloudflare/cloudflare-docs/issues

I think you can also implement it as a private route via the gateway, so you access the private address of bitwarden instead of bypassing auth to a public host name (this I haven’t tried, but maybe another worthwhile option?) https://github.com/cloudflare/cloudflare-docs/blob/production/content/cloudflare-one/tutorials/zero-trust-network-access.md

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