1 - Go to https://filenation.io/
2 - Click on Upload Files button. Locate the file that you want to upload and click open.
3 - Click on “Send Files to” and add the recpient email address.
4 - Click on “Your Email” and add your email address.
5 - Click on “Send”.
6 - The file will be added to IPFS and sent to the sender's email, keep page still open until Eternum has finished pinning :)
Try it out and tell me how I can improve it to empower more people with this amazing P2P technology :)
* 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?
I've spoken to a few people from the IPFS team, but they couldn't figure out the cause. Hopefully the next version makes discovery more reliable and fixes this (the files are quite quick to download once peers discover each other).
Once they're connected, however, I haven't had any performance issues unless I was using IPNS. Though I only use IPFS to host static sites ( https://ipfs.poeti.codes/ipns/dreams.poeti.codes/ )
For the curious: you'd run `ipfs id` on the nodes to get their addresses. Then you'd run `ipfs config edit` on them and add the other node's address to the bootstrap section. https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#b...
But yeah... They'd still mysteriously not connect to each other at times.
Hearth is basically hit and miss for that reason, sometimes files show up right away and it's amazing, sometimes they time out and it's useless. Very frustrating, and there's absolutely nothing we can do about it.
Currently the "About" link goes to Github, which I found odd...
Would be one approach. Or, as a link is sent "out of band", I suppose one could simply provide a symmetric key in the email. Not as secure - but might be sufficient.