Persist state on web3 #50
Replies: 5 comments 2 replies
-
Thanks for the suggestion! I will add it to my list as Web3 is the rage now. I know https://js.ipfs.io/ was something I had been considering for this. I want to keep as much as possible on the client side. |
Beta Was this translation helpful? Give feedback.
-
IPFS is a possibility, but the downside of it would be that there is no guarantee your data would stay hosted unless the user would also host their own server or pay for Pinata (pinning service), which kind of defeats the purpose. That's why I mentioned SkyNet since there is a minimum uptime and free tier guarantee. |
Beta Was this translation helpful? Give feedback.
-
Ah cool, thanks for the tip. I am new to Web3, but will look into it more. |
Beta Was this translation helpful? Give feedback.
-
Surprised at 3 down votes to the idea. I wonder is the issue Web3? Do people want persistent storage? What would it be used for? Why would it be a good/bad idea? |
Beta Was this translation helpful? Give feedback.
-
Persistent storage would be great, but maybe just as a sync to a node.js instance running on a self-hosted server? The backend for storing could be either filesystem directly, or maybe even a database for parts which are not very large. |
Beta Was this translation helpful? Give feedback.
-
This is a really cool project and it would be nice to be able to "login" to such a webtop from anywhere.
I imagine that on exit the IndexedDb contents could be synced to Sia SkyNet, StorJ, Filecoin or others (encrypted) and that one can retrieve their private state using a login screen.
Beta Was this translation helpful? Give feedback.
All reactions