You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's decentralized and, in fact, webtorrent apps can work with no server at all.
So, looking at the readme, you have to get your infohash and add it to the clientside JS to access your app.. You can't add your hash to your app before seeding it because you don't know it yet and everytime you change anything you re-seed with a new hash..? If that's not the case and the node stuff can generate an infohash then the readme is a bit misleading in it's example.
Also that it uses node at all and has the above quote is likely misleading to less experienced developers who may not fully understand the concept of a fully clientside app, SPA or not - most people developing SPAs do it from node using React or something and might be surprised when (obviously, to more experienced people) there's no server-side processing available anywhere.
Also; project is dead it seems, eh?
The text was updated successfully, but these errors were encountered:
It's decentralized and, in fact, webtorrent apps can work with no server at all.
So, looking at the readme, you have to get your infohash and add it to the clientside JS to access your app.. You can't add your hash to your app before seeding it because you don't know it yet and everytime you change anything you re-seed with a new hash..? If that's not the case and the node stuff can generate an infohash then the readme is a bit misleading in it's example.
Also that it uses node at all and has the above quote is likely misleading to less experienced developers who may not fully understand the concept of a fully clientside app, SPA or not - most people developing SPAs do it from node using React or something and might be surprised when (obviously, to more experienced people) there's no server-side processing available anywhere.
Also; project is dead it seems, eh?
The text was updated successfully, but these errors were encountered: