-
Notifications
You must be signed in to change notification settings - Fork 58
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
Atomic-Server + Content Addressing (like IPFS) #66
Comments
Responsibilities of IPFS module in server
ImplementationFull ipfs node in app (depracated)The EDIT: It's no longer maintained Client-only - use external gateway
https://docs.rs/ipfs-api/0.11.0/ipfs_api/#writing-a-file-to-ipfs IROHNew rust implementation: https://github.com/n0-computer/iroh Seems to be promising! Unclear if it can be embedded, yet. EDIT: Iroh Can be embedded! |
Since Atomic Data uses a lot of (non-local) HTTP resources, there is a risk of remote errors that make data unfetchable. When a server goes down, a resource has changed or a domain name hasn't been paid for - the request will fail. That is part of the web, and we have a chance to encounter this every time we open a webpage.
With Atomic Data, however, we rely even more intensely on remote data. Atomic Properties, for example, tell us something about the datatype of an Atom. When parsing triples with new properties for a client, the properties need to resolve. IPFS might help with this, as it can enable 'freezing' of resources. The frozen resources could still contain a link to the original source (HTTPS address) which can be used for updating properties.
The text was updated successfully, but these errors were encountered: