After deploying to host my websites I'm now playing with and I must admit I'm quite impressed how mature and feature-rich the system is. It's certainly a superset of the services IPFS or DAT protocols have to offer.

Just playing with the first native web browsers and it's really cool, also supports .ETH domains. Written in Python using QtWeb

An interesting decentralized, open-source and based application for trading goods and services in local areas. Developed in Italy and currently being deployed in Italy with support of local government as response to the pandemics, but easily ported to any location.

Just wondering: if you publish a website to often what's the best strategy?

1) `ipfs add -r website/`, address using recent CID and set it in DNS using `dnslink`
2) publish recent CID into IPNS (`ipfs name publish CID`)
3) Something else?

Option 1) sucks because each change to website requires updating CID in my website's reverse proxy and DNS.

Option 2) sucks because IPNS so is slooow on both publishing and resolving...

I have just deployed a website that concurrently works on and regular HTTP πŸ˜‚


IPFS -> /ipfs/QmcUqsb9DSwjFHVzLyT6u6TrDSzwh3BfF5qDgSnAiMpJNZ/

Bridged IPFS ->

ENS -> webcookies.eth (you need Almonit or MetaMask browser add-on)

Tor -> 34lrobqqyonldvdkwl64dw2c7kli2d

Yggdrasil ->

DAT -> dat://

Is it just me, but compared to , is so incredibly slow... 🐒

A nice rant about

TBH I made two attempts to use IPFS but it... just doesn't. Using protocol on the other hand I was able to make a working website in ~5 mins

kravietz πŸ¦‡'s choices:

Mastodon πŸ”

Fast, secure and up-to-date instance. PrivacyTools provides knowledge and tools to protect your privacy against global mass surveillance.

Matrix Chat:
Support us on OpenCollective, many contributions are tax deductible!