4 ms·

Personally I've been using magic wormhole lately. It's p2p and very easy to use. https://github.com/warner/magic-wormhole https://github.com/warner/magic-wormh

Personally I've been using magic wormhole lately. It's p2p and very easy to use. https://github.com/warner/magic-wormhole https://github.com/warner/magic-wormhole

Mashimo 8y ago
I could not find an example on the gibhub page, but here is the timecode from a video that shows it in action: https://youtu.be/oFrTqQw0_3c?t=129 https://youtu.be/oFrTqQw0_3c?t=129 Also: https://magic-wormhole.readthedocs.io/en/latest/welcome.html#example https://magic-wormhole.readthedocs.io/en/latest/welcome.html... Looks neat.
StavrosK 8y ago
I love magic wormhole, you give the recipient three words and a number and the file is sent peer-to-peer. No messing about with routing or anything.
- 3pt14159 8y ago
  How is it for getting around weird networks (double NAT, etc)?
  - StavrosK 8y ago
    It's been great every time I've used it, I think it has a relay server as a last resort if it can't get a p2p connection. Never had problems with it.
  - deathanatos 8y ago
    > The library depends upon a “rendezvous server”, which is a service (on a public IP address) that delivers small encrypted messages from one client to the other. This must be the same for both clients, and is generally baked-in to the application source code or default config. > This library includes the URL of a public rendezvous server run by the author. Application developers can use this one, or they can run their own (see the https://github.com/warner/magic-wormhole-mailbox-server https://github.com/warner/magic-wormhole-mailbox-server repository) > For now, bulk data is sent through a “Transit” object, which does not use the Rendezvous Server. Instead, it tries to establish a direct TCP connection from sender to recipient (or vice versa). If that fails, both sides connect to a “Transit Relay”, a very simple Server that just glues two TCP sockets together when asked. If I understand the docs correctly, it always uses a centralized server to establish the transfer. Once the transfer is established, it'll attempt to transfer the files directly, if possible, but if not, it'll fall back to using a relay. And so many people are trapped behind NAT these days, I don't know that the need for this will be all that unusual.

Personally I've been using magic wormhole lately. It's p2p and very easy to use. https://github.com/warner/magic-wormhole https://github.com/warner/magic-wormhole

Mashimo 8y ago

I could not find an example on the gibhub page, but here is the timecode from a video that shows it in action: https://youtu.be/oFrTqQw0_3c?t=129 https://youtu.be/oFrTqQw0_3c?t=129 Also: https://magic-wormhole.readthedocs.io/en/latest/welcome.html#example https://magic-wormhole.readthedocs.io/en/latest/welcome.html... Looks neat.

StavrosK 8y ago

I love magic wormhole, you give the recipient three words and a number and the file is sent peer-to-peer. No messing about with routing or anything.

3pt14159 8y ago
How is it for getting around weird networks (double NAT, etc)?
- StavrosK 8y ago
  It's been great every time I've used it, I think it has a relay server as a last resort if it can't get a p2p connection. Never had problems with it.
- deathanatos 8y ago
  > The library depends upon a “rendezvous server”, which is a service (on a public IP address) that delivers small encrypted messages from one client to the other. This must be the same for both clients, and is generally baked-in to the application source code or default config. > This library includes the URL of a public rendezvous server run by the author. Application developers can use this one, or they can run their own (see the https://github.com/warner/magic-wormhole-mailbox-server https://github.com/warner/magic-wormhole-mailbox-server repository) > For now, bulk data is sent through a “Transit” object, which does not use the Rendezvous Server. Instead, it tries to establish a direct TCP connection from sender to recipient (or vice versa). If that fails, both sides connect to a “Transit Relay”, a very simple Server that just glues two TCP sockets together when asked. If I understand the docs correctly, it always uses a centralized server to establish the transfer. Once the transfer is established, it'll attempt to transfer the files directly, if possible, but if not, it'll fall back to using a relay. And so many people are trapped behind NAT these days, I don't know that the need for this will be all that unusual.