3 ms·
This is pretty cool, good job! I have a few questions: * How long are you pinning files for? * Is there a maximum size up to which you'll pin files? Also, a
by StavrosK 9y ago
This is pretty cool, good job! I have a few questions:
* How long are you pinning files for?
* Is there a maximum size up to which you'll pin files?
Also, a tip: You can speed up your service by exposing the bridge on your pinning node. That way, your files don't have to go from node to node, the end user can just fetch them from your node's local pin store.
EDIT: Quickly skimming your code, it seems like you aren't uploading the files anywhere or pinning at all? Unless I'm mistaken, you're running ipfs-js and instantiating a node in the user's browser, which means that the user will have to keep the browser open for the file to be available, no?
- prophesi 9y agoI believe they're using Eternum's API to pin the content. I didn't look at the code, but the download link I got in the email is from https://eternum.io https://eternum.io
- StavrosK 9y agoAh yes, true. I missed that in the code, my TypeScript isn't great. Doesn't the page still have to stay open until Eternum has finished pinning, though?
- alexsicart 9y agoYes, it should take some minutes! I'll add this to new features. Thanks! :)
- alexsicart 9y agoYes right now we are using Eternum API for the MVP to pin the content, but the next feature will be pinning in our server. Uploading the file to IPFS (front-end), then from the emai-server, downloading the file from hash to our own server and then connecting it to gateway https://filenation/ipfs/{hash} https://filenation/ipfs/{hash} (everything in the same server to save a lot in bandwidth)
- deleted 9y ago[deleted]