• Clean Dependencies
• Update READMEs & Docs
• Update CLI
• Test, Test, Test
• Save CID on Pinata
• Update social.defluencer.eth
• Pin on local node

Identity documents as keyring with many key pairs is the idea.

• Browser WebCrypto API https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto
• IPFS node local IPNS keys
• Browser crypto wallet (Metamask or Brave)
• HW wallet either via Metamask OR WebHID API
• Future IPFS Ledger App via WebHID API

IPNS & DAG-JOSE have specific requirements. They cannot use messages signed by cryptocurrency wallets because of the prefixed and hash used.

The solution would be to have a master key that is persistent and secure (HW wallet prolly) and authorise less secure but easier to use keys to update IPNS and sign block.

See Project for more info

• Bundle IPFS with the app.
• Change the IPFS config to allow the app access.
• Add a new feature for all the workarounds.
• Workarounds for not having access to; metamask, WebCrypto, etc...
• Configure Windows builds.

Would be cool to display if the content is pinned or not and add a button to pin content.

• Yew v0.20 released
• Yew-router 0.17 released
• Yew-agent 0.2 not released for some reason???
• Ybc need some code changes

OK!

I need HashRouter which is implemented only on the master branch of yew-router .

I also need ybc which is not updated for Yew 0.19 But there's a fork of it pretty much all done.

Then I could not compile for WASM because it seams like my ipfs-api and yew conflict in some way that make yew compile with tokio which cannot compile for WASM, how? IDK! Since both crate compile for WASM separately but not together???

I fixed it by forking yew master and removed tokio (which should not affect anything but does) from the dependency.

Hopefully, updates will get merged so that I don't have to rely on so many forks.

Would be cool to have a way to export/import all user data as a .car file