4 ms·
way back (well before Ethereum and NFTs), i hosted a blog on IPFS. DNS level stuff: - TXT record with an IPFS content identifier - A record pointing to an IPF
by colinsane 3y ago
way back (well before Ethereum and NFTs), i hosted a blog on IPFS. DNS level stuff:
- 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.
- brunoqc 3y agoI like this about ipfs. I don't understand why ipfs didn't lit the world on fire yet and they only seems to care about web3/crypto/nft these days.
- acdha 3y agoIPFS doesn’t solve the major problems most people have: you still need to pay for guaranteed hosting and most content in the world is private, not something you want to share widely. Toss in the designed-in performance issues and it’s less surprising that it’s remained a niche.