spec VS ipvfoo

There's ucan too, which fills some similar-ish roles. It's definitely not quite as comprehensive & featureful as ocapn, but worth mentioning. https://ucan.xyz/

Thanks for the mention! Capyloon (https://capyloon.org) had a grant from Protocol Labs (the IPFS stewards) in 2022 so we focused quite a bit on that indeed. We learned a lot - especially about the maturity and usability of the IPFS stack.

I'm still very bullish on the dWeb pieces: content based addressing, UCANs (https://ucan.xyz/) for distributed auth, new web app models (https://hackmd.io/@robin-berjon/tiles) to create an ecosystem that is not locked by centralized app stores.

There's a lot to do, all contributions are welcome (frontend, device ports, platform apis...). We have a Matrix channel (https://matrix.to/#/#capyloon:matrix.org) and you can try desktop builds easily following the steps at https://github.com/capyloon/nutria#quick-start

https://ucan.xyz - similar technology

..which builds on https://ucan.xyz/ for auth. I’m also curious to learn what Chatternet does differently, and whether that’s necessary.

Given all the recent chatter about Chrome turning evil, I spent a few days polishing my Chrome extension (IPvFoo, for observing the IPv6 transition) to run properly on Firefox. Technically it's been available since 2017, but there were numerous compatibility bugs that I was hoping Firefox would fix eventually. I just hacked around the remaining bugs, so Chrome/Firefox are now at feature parity from a common codebase:

https://github.com/pmarks-net/ipvfoo

The browser add-on IPvFoo can tell you if you're using native IPv4 or a fallback mode. It'll also tell you what IP addresses you're talking to for a given page to load, which is incredibly useful.