snapdrop VS FilePizza

rather worried that it's going to go the same fate as [Sharedrop](https://github.com/ShareDropio/sharedrop) and [Snapdrop](https://github.com/SnapDrop/snapdrop) where they recently got taken over by LimeWire the crypto/AI company.

If the constraint is that you don't want to install any software, there are a bunch of these web based AirDrop clones, besides the ones mentioned here are two more:

https://pairdrop.net/

https://snapdrop.net/

I've tried PairDrop, it works well.

I love Snapdrop [0] for that use case, since it doesn't require downloading/installing an app.

[0] https://snapdrop.net/

Snapdrop is very easy to use but does not work with a VPN, nor does it support infinite file size and WebRTC relaying.

> My fave is https://snapdrop.net

it's so funny how everyone have a favorite. They all use standardized hacks on top of hacks, just because ISP do not want to let you serve content and will fight for NAT, which is their only line of defense from everyone else messing with their precious IGMP multicast hacks so they can subsidize their TV business on your internet bill. it's all so funny.

but the best joke is how microsoft and apple both tried to "make things work" in the late 90s (?) with their special zero-conf-by-other-names trainwreak of network protocols.

There's no end in sight.

Learn More: Snapdrop

Hmm. I'm not a WebRTC pro but looked into it recently for a hobby project and felt that the typical WebRTC TURN implementation still leaves the TURN server in a quite trusted position. My rough understanding:

- (1) Each client generates a key pair

- (2) The fingerprint of the public key is part of the SDP message each client generates

- (3) The SDP message is somehow exchanged between the clients, out of band, and the session is started. The client's verify the remote peer using the public key from the SDP message.

The problem is that it's not really feasible in most circumstances to exchange the full SDP message out of band, so instead the service provide some mechanism to map a shorter ID in a URL to a centrally stored copy of the SDP. I think this might be where it happens for filepizza [0].

This means that a malicious file sharing operator, being in control of both the TURN service and the out-of-band signalling mechanism, could just MITM the DTLS connection and snoop on all the data going by. The peer's think they have each others public keys but they just have two keys owned by the server.

[0]: https://github.com/kern/filepizza/blob/main/src/channel.ts

Is there a tl;dr on the crdt/collaboration feature? How does one get the share up and running, do you get a special link that you can send to someone? How smooth can it get? I'm guessing it's hard to do without some sort of relay system (like syncthing) or servers for hosting links (like https://file.pizza )

Not magic-wormhole compatible, but saw these two shared on other comments:

- https://sendfiles.dev

- https://file.pizza

Learn More: FilePizza

There are a few browser based p2p file sharing tools [1] and a bunch of CLI tools out there as well for the same job.

# Browser Based

1. FilePizza https://file.pizza/

alternatively, if going the p2p route, they could try something like file.pizza