Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Share read-only web3.storage capabilities #105

Open
DougAnderson444 opened this issue Apr 10, 2024 · 5 comments
Open

Share read-only web3.storage capabilities #105

DougAnderson444 opened this issue Apr 10, 2024 · 5 comments

Comments

@DougAnderson444
Copy link

I'm looking to share read-only pointers to a database. After seeing this comment I'm under the impression this isn't a feature yet.

Am I right in deducing that if we add a function similar to shareWith(did) with only can: 'clock/head' we would create a read-only version of shareWith?

capabilities: [{ can: 'clock/*', with: this.clockSpaceDIDForDb() }],

@DougAnderson444
Copy link
Author

Also, what is the .xts extension that is being used here?

@jchris
Copy link
Contributor

jchris commented Apr 17, 2024

Thanks @DougAnderson444 -- this is a .ts file I just changed it because it is breaking the build. The IPFS connector is a long story, but the short version is the architecture is right, but it's currently way more complex than it needs to be, because the web3.storage team added delegation features we can use to no longer need most of that code. I'm not sure where to find it in their docs, but basically their email validation agent sets up the ablity to delegate so that Fireproof code doesn't have to manage devices anymore.

IPFS has gotten to be higher priority in the last couple of weeks, so if you are up for it, I'd love to have a call and learn more about your use case. Or you can email me async at [email protected]

@jchris
Copy link
Contributor

jchris commented Apr 18, 2024

Thanks for the call. Check out the demo video linked here storacha-network/project-tracking#1 (comment)

@jchris
Copy link
Contributor

jchris commented Apr 23, 2024

@DougAnderson444 I updated the IPFS connector code so the build is clean. I haven't had a chance to test drive it yet, but at least now the busywork is cleaned up #108

@jchris
Copy link
Contributor

jchris commented May 3, 2024

Tracking current client update progress here #111

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants