4 ms·

Hi, Great idea, thanks for this. I didn't have the time to test it thoroughly yet. One observation though: the hash IDs should be shorter, in my humble opini

Hi, Great idea, thanks for this. I didn't have the time to test it thoroughly yet. One observation though: the hash IDs should be shorter, in my humble opinion, as to be able to read it once on one screen and type it in on another. Or, communicate over the phone. If IDs are so complex that I need to copy-paste them around, then, that kind of defeats the purpose. Thanks.

logicallee 2y ago
Thanks for the positive feedback! I'm not sure, but think that if IDs were much shorter then people could impersonate peers and receive files that weren't intended for them. Sending an ID by text message, email, Facebook messenger, etc, works well but large files tend to fail, Facebook downscales videos for example and Google has a small attachment file size limit, after that it offers to put files in a google drive link but people might not have space for that on their Google drive. By sending the file via WebRTC there are no size limitations, it is just a convenient way to send a full resolution video in the moment. I tried it from my iPhone to computer, it worked better than trying to send the same file on Facebook (which reduces the quality, it gets downsampled) or trying to send it by email. Sharing the client ID was easy for me by email and it worked for me.
- atmanactive 2y ago
  You could lock the ID once transfer has started, no?
  - logicallee 2y ago
    I mean that with short ID's you could be transferring to the wrong person. Someone could squat all the short ID's, I think. (Just have a browser open for all of them and accept any downloads.) Then they would get things that weren't intended for them. I am not an expert on WebRTC but I think this is why the ID's have a length like that, to prevent multiple people from using the same ID.
    - atmanactive 2y ago
      Yes, the worldwide scope is the problem here. I could envision a drop-down where users could choose the desired scope, like, for example: LAN, City, Country, Continent, and World. The wider the scope, the more chars used for the hash ID.
- vednig 2y ago
  Tried to build doshare.me, we've yet to work on P2P capabilities

logicallee 2y ago

Thanks for the positive feedback! I'm not sure, but think that if IDs were much shorter then people could impersonate peers and receive files that weren't intended for them. Sending an ID by text message, email, Facebook messenger, etc, works well but large files tend to fail, Facebook downscales videos for example and Google has a small attachment file size limit, after that it offers to put files in a google drive link but people might not have space for that on their Google drive. By sending the file via WebRTC there are no size limitations, it is just a convenient way to send a full resolution video in the moment. I tried it from my iPhone to computer, it worked better than trying to send the same file on Facebook (which reduces the quality, it gets downsampled) or trying to send it by email. Sharing the client ID was easy for me by email and it worked for me.

atmanactive 2y ago
You could lock the ID once transfer has started, no?
- logicallee 2y ago
  I mean that with short ID's you could be transferring to the wrong person. Someone could squat all the short ID's, I think. (Just have a browser open for all of them and accept any downloads.) Then they would get things that weren't intended for them. I am not an expert on WebRTC but I think this is why the ID's have a length like that, to prevent multiple people from using the same ID.
  - atmanactive 2y ago
    Yes, the worldwide scope is the problem here. I could envision a drop-down where users could choose the desired scope, like, for example: LAN, City, Country, Continent, and World. The wider the scope, the more chars used for the hash ID.
vednig 2y ago
Tried to build doshare.me, we've yet to work on P2P capabilities