 use it instead :)

------
saganus
Interesting.

Would it make sense to pair this with WireGuard, to provide end-to-end
encrypted file transfer?

If we setup a WireGuard connections between two nodes, then run the server and
client through this link, it should work seamlessly, right?

------
xori
Well fucking done. I wanted to build this ~5 years ago, but nodejs wasn't
mature enough. I tried in Java but doing your own UPnP implementation is no
fun.

~~~
whatl3y
Thanks! Yeah nodejs streams and async IO seemed like an ideal use case for
this type of tool, plus I wanted to have the easiest approach to passing files
between 2 people as possible (we use it at work all the time). Obv a lot has
happened in 5 years with nodejs, so I realize it was likely an order of
magnitude easier for me to get up-and-running in the last couple months with
this tool than it would've been for you 5 years ago haha.

------
kazinator
Name taken almost nine years ago by the TXR Language.

~~~
whatl3y
Thanks for the heads up on the name clash (obviously never heard of the TXR
language before this). I named it based on a couple of factors being 1.
something that's easy to remember and makes sense (txr ~ transfer) and 2. the
NPM module name wasn't taken yet :)

I can change the name, but our projects are pretty much totally different and
I'm not trying to make any money off this tool so would prefer to just leave
it as is if it won't confuse too many people.

~~~
kazinator
> _obviously never heard_

In 2009, I didn't rely on what I heard of or hadn't heard of; I googled very
thoroughly before naming my project and its principal executable.

A name clash is a problem for any FOSS distro that builds both packages.
People don't directly choose and use everything that is installed in a distro.
A lot of is is pulled in by dependencies, for instance.




File sharing is for everyone. With Dropshare Cloud - tisba
https://dropshare.cloud/
======
tisba
That service is actually a batteries included hosting service for the very
well made desktop file sh