In terms of block stores we support local disk, or S3 compatible.
You can log in through any peergos instance (including localhost) and your writes are persisted directly to your instance. The whole thing is also independent of DNS and the TLS CAs (except of course if you use a public web interface)
- TXT record with an IPFS content identifier
- A record pointing to an IPFS gateway that ran on my laptop (and was restricted to only serving my own content)
- fallback A records that pointed to the public IPFS gateways
i could publish new content from my laptop, and as long as i had one other reader who browsed it via native IPFS (i did), then i could pretty safely not worry about my own uptime.
that was pretty useful to me at the time who had no clue how to be a sysadmin and keep good uptime and whatnot.
Arweave is better suited to archival storage. There are options for participants to ban particular types of content which may be illegal to host in their jurisdiction. This was designed to prevent the spread of CP, terrorism related info, etc. but that means it is also susceptible to DCMA issues too.
Peergos kinda do it but maybe it's only for the transport and it uses S3 or something like that.
> Arweave is better suited to archival storage
Thanks, I'll take a look.
I wish there was more exciting ipfs news beside nfts.
EDIT: Arweave seems to be part of the crypto/web3 thing I'm not a fan of.