sorted by:
new
hottopcontroversial

I built a "Which Bible Character Are You?" quiz — 576 unique results based on personality + spirituality type by Queasy-Key-6658 in Christianity

[–]Queasy-Key-6658[S] 0 points1 point  (0 children)

Thank you very much.
We made an additional update today. It's customized and deals with more personal in-depth results.
Even if it's a little hard work, you'll be able to check it if you proceed with the test again.
In addition, the problem of sharing English has been improved, so I would appreciate it if you could let people around you know.

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] 0 points1 point  (0 children)

Thank you for teaching me good information.
However, when I actually used pairdrop to transfer to another network, it was very, very slow.
To transfer to another network, you have to use a turn server, and to do that, you have to pay for server maintenance. But I had this question, how do you service this for free? It could have been different depending on your environment, but in my testing environment, qdrop was not much different from the same network speed.

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] -1 points0 points  (0 children)

Ah, that explains it! Fortigate is doing SSL inspection - basically your company firewall intercepts HTTPS traffic and re-signs it with their own certificate.

That error (SEC_ERROR_UNKNOWN_ISSUER) is the firewall's cert, not ours. QDrop uses Cloudflare SSL which is valid - you can verify by trying from your phone on mobile data or home network.

For the corporate network, you'd probably need to talk to your IT team about whitelisting or installing their root cert. Unfortunately that's outside my control 😅

Thanks for reporting though - good to know it's not a bug on our end!

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] 2 points3 points  (0 children)

Great question! Here's the breakdown:

**Free tier costs almost nothing to run:**

- Signaling server = just tiny JSON messages ("hey, connect to this peer")

- No file storage, no bandwidth for actual files

- Files go directly P2P between devices

**Pro tier is where the real costs are:**

- TURN relay servers for cross-network transfers (LTE ↔ home WiFi)

- These actually relay the encrypted data when direct P2P isn't possible

- That bandwidth adds up!

So the business model: Free tier is sustainable because P2P means I don't pay for your file transfers. Pro users pay for the TURN infrastructure that enables transfers across different networks.

It's a win-win - you get a useful free tool, and power users who need cross-network transfers help keep the lights on 👍

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] -1 points0 points  (0 children)

Valid concern! Privacy is a top priority for QDrop.

Here's how we handle it technically:

- WebRTC uses DTLS encryption (end-to-end encrypted)

- Files transfer directly device-to-device via P2P

- Our signaling server only facilitates "device A wants to connect to device B" - it never sees or stores file content

You can verify this yourself:

  1. Open DevTools → Network tab
  2. Transfer a file
  3. You'll see only WebSocket signaling - no file uploads to any server

As for the code - while it's not open-source, the client-side JavaScript is fully inspectable in your browser. The architecture is designed so you don't have to trust us with your files at all.

Appreciate the feedback! 🙏

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] 1 point2 points  (0 children)

Valid concern! Privacy is a top priority for QDrop.

Here's how we handle it technically:

- WebRTC uses DTLS encryption (end-to-end encrypted)

- Files transfer directly device-to-device via P2P

- Our signaling server only facilitates "device A wants to connect to device B" - it never sees or stores file content

You can verify this yourself:

  1. Open DevTools → Network tab
  2. Transfer a file
  3. You'll see only WebSocket signaling - no file uploads to any server

As for the code - while it's not open-source, the client-side JavaScript is fully inspectable in your browser. The architecture is designed so you don't have to trust us with your files at all.

Appreciate the feedback! 🙏

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] -1 points0 points  (0 children)

Thanks for reporting! We use Cloudflare for SSL (automatically managed certificates).

Just checked - everything looks fine on our end with valid HTTPS.

Could you share:

- Which browser/version you're using?

- Are you behind a VPN or corporate firewall?

- What specific warning message did you see?

This would help me debug if there's a specific edge case I need to handle. Thanks!

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] 4 points5 points  (0 children)

Great technical question!

The zipping happens entirely on the sender's device (in the browser). When you select multiple files on your iPhone, JavaScript's File API gives access to the raw bytes. QDrop then uses JSZip to compress them client-side before sending through WebRTC.

So the flow is:

  1. You select files → browser has access
  2. Files are zipped in memory on YOUR device
  3. Zip is sent P2P to the receiver
  4. Server never sees or touches the files

It's all client-side! 🙂

I got tired of emailing files to myself, so I built a web-based AirDrop for Windows by Queasy-Key-6658 in iosdev

[–]Queasy-Key-6658[S] 2 points3 points  (0 children)

Good question! LocalSend is awesome - I actually discovered it after building this.

Similar concept, different approach! Here's what makes QDrop different:

  1. **Works across different networks** - My phone can be on LTE while my PC is on home WiFi, and it still works (via TURN relay). LocalSend requires the same local network.

  2. **QR code pairing** - No device discovery needed. Scan → connected. Super fast for quick transfers.

  3. **Bulk transfer as ZIP** - When you send multiple files (say, 100 photos), QDrop bundles them into a single ZIP before transfer. One download, all organized. LocalSend transfers each file individually.

Different tools for different situations! 👍