3 ms·

If it is decentralized, then why do I need node-js? Why do I need a webserver?

yosamino 9y ago
Because the datastructure being manipulated is the "decentralized" feature here. And to manipulate a datastructure you need software. I am intrigued by your comment and your expectation about"decentralized", though. And now I am curious: What were you expecting ?
- timthelion 9y ago
  I was expecting a standalone html file that could be run by clicking on it, or, due to that "same origin" b_llsh*t [1], at least served using any generic http server, not one which has to be specially configured and installed. [1] I know the security reasons behind this, I just find the hassle to be a counter-logical irksome, and insecure in most cases, hack.
  - KirinDave 9y ago
    I suspect you didn't read my reply, because if you did you'd recognize that [1] is simply not true. The only considerations here are simplifying the programming model. AFAICT, nothing in this demo needs a dedicated node server, it just simplifies the explanation. Odds are though that if you're going to need your own personal centralization of some sort if there is any concept of user privilege in your system.
KirinDave 9y ago
Actually, you absolutely could host the website inside IPFS and if you don't mind going to an incomprehensible ipfs.io/ipfs/___ address, it'll fetch. The webserver is there in this case to make life easier during dev, and to make it easy to call your local ipfs API service to do things like monitor the messages on the pubsub.
lgierth 9y ago
PeerPad, which evolved from the data structure in this tutorial, can totally fine be run from any location: - https://peerpad.net https://peerpad.net - https://ipfs.io/ipns/peerpad.net https://ipfs.io/ipns/peerpad.net - https://ipfs.io/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD https://ipfs.io/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6... - http://localhost:8080/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD http://localhost:8080/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW... And with the ipfs-companion browser extension: - dweb:/ipns/peerpad.net - dweb:/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD - ipns://peerpad.net - ipfs://QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD Or by grabbing it using `ipfs get /ipns/peerpad.net` and clicking the html file in the resulting directory.

Because the datastructure being manipulated is the "decentralized" feature here. And to manipulate a datastructure you need software. I am intrigued by your comment and your expectation about"decentralized", though. And now I am curious: What were you expecting ?

timthelion 9y ago
I was expecting a standalone html file that could be run by clicking on it, or, due to that "same origin" b_llsh*t [1], at least served using any generic http server, not one which has to be specially configured and installed. [1] I know the security reasons behind this, I just find the hassle to be a counter-logical irksome, and insecure in most cases, hack.
- KirinDave 9y ago
  I suspect you didn't read my reply, because if you did you'd recognize that [1] is simply not true. The only considerations here are simplifying the programming model. AFAICT, nothing in this demo needs a dedicated node server, it just simplifies the explanation. Odds are though that if you're going to need your own personal centralization of some sort if there is any concept of user privilege in your system.

KirinDave 9y ago

Actually, you absolutely could host the website inside IPFS and if you don't mind going to an incomprehensible ipfs.io/ipfs/___ address, it'll fetch. The webserver is there in this case to make life easier during dev, and to make it easy to call your local ipfs API service to do things like monitor the messages on the pubsub.

lgierth 9y ago

PeerPad, which evolved from the data structure in this tutorial, can totally fine be run from any location: - https://peerpad.net https://peerpad.net - https://ipfs.io/ipns/peerpad.net https://ipfs.io/ipns/peerpad.net - https://ipfs.io/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD https://ipfs.io/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6... - http://localhost:8080/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD http://localhost:8080/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW... And with the ipfs-companion browser extension: - dweb:/ipns/peerpad.net - dweb:/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD - ipns://peerpad.net - ipfs://QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD Or by grabbing it using `ipfs get /ipns/peerpad.net` and clicking the html file in the resulting directory.