<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pmalay on Medium]]></title>
        <description><![CDATA[Stories by Pmalay on Medium]]></description>
        <link>https://medium.com/@pmalay694?source=rss-7f1102b9b620------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*pf-0KDYlQxyzW7g-</url>
            <title>Stories by Pmalay on Medium</title>
            <link>https://medium.com/@pmalay694?source=rss-7f1102b9b620------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:42:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pmalay694/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Your Files Don’t Need a Middleman]]></title>
            <link>https://medium.com/@pmalay694/why-your-files-dont-need-a-middleman-f5ac9c5f77d8?source=rss-7f1102b9b620------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5ac9c5f77d8</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[file-sharing]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[file-transfer]]></category>
            <category><![CDATA[webrtc]]></category>
            <dc:creator><![CDATA[Pmalay]]></dc:creator>
            <pubDate>Sun, 16 Aug 2026 06:38:02 GMT</pubDate>
            <atom:updated>2026-08-16T06:38:02.734Z</atom:updated>
            <content:encoded><![CDATA[<p>You have a 2GB video you need to get to a client tonight.</p><p>You open a file-sharing site. You wait for the upload bar to crawl to 100%. You close your laptop, relieved — done.</p><p>Then, twenty minutes later: <em>“Hey, the link says it’s still processing.”</em></p><p>Your file didn’t disappear. It’s just doing something slow and invisible: sitting on a server somewhere, waiting for someone else to come download it.</p><p>Here’s the part that should bother you more than it does: <strong>the technology to skip that entire step has existed in your browser since 2011, for free, and almost nobody uses it for files.</strong></p><h3>The Upload-Then-Download Problem</h3><p>Here’s what actually happens when you “share” a file the normal way:</p><ol><li>You upload it to a server.</li><li>The server stores it.</li><li>Your recipient opens a link.</li><li>The server sends it back down to them.</li></ol><p>Two full trips, for one file. You’re paying for it in time — and, quietly, in privacy. Your file sits on someone else’s hardware, even if just for a few hours. Someone, somewhere, technically <em>could</em> open it.</p><p>This is why big files crawl, why “unlimited” transfer usually isn’t, and why free tiers cap you at 2GB — storage isn’t free for the company hosting it, even if it’s free for you.</p><h3>The Trick Video Calls Have Been Using All Along</h3><p>Here’s what most people don’t know: your browser already has a way to talk <em>directly</em> to another browser, with nothing in the middle holding your data.</p><p>It’s called WebRTC — the same tech behind Zoom, Meet, and Discord calls. On a video call, your camera feed isn’t uploaded to a data center and downloaded by the other person. It goes straight from your device to theirs, live.</p><p>That same pipe can carry a file exactly as easily as it carries video. Once two browsers connect, sending a file is just… sending data. No upload bar. No “processing.” No storage step, because there’s nothing to store.</p><p><strong>This is the whole idea behind </strong><a href="https://sendrop.xyz/"><strong>Sendrop</strong></a> — the tool I built around exactly this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kw5NkvRLanLounWVWt5JLw.png" /></figure><p><em>[Diagram: Traditional Cloud Transfer vs. Sendrop’s Direct Transfer — see attached image]</em></p><h3>How Two Browsers Actually Find Each Other</h3><p>If there’s no server holding your file, how do two strangers’ browsers even find each other?</p><p>They need a quick introduction — a <em>signaling server</em>. Think of it as a matchmaker: it helps your browser and your friend’s browser swap just enough information to locate each other, like exchanging phone numbers, then it steps out of the way completely. It never touches your file.</p><ul><li><strong>Signaling</strong> (Sendrop uses Redis and Pusher here) briefly relays connection info so the two browsers can find each other.</li><li><strong>STUN</strong> helps a browser learn its own public address on the internet — like checking your own mailing address before telling someone where to send a letter.</li><li><strong>TURN</strong> is the fallback for when direct connection fails — a strict firewall, a corporate network, certain routers. TURN literally stands for <em>“Traversal Using Relays around NAT”</em> — it’s the internet’s official term for “plan B.”</li></ul><p>Sendrop tries the direct route first, since it’s fastest, and only falls back to TURN when it has to.</p><h3>Facts About File Sharing That’ll Mess With Your Head</h3><p><strong>1. The early internet was 100% peer-to-peer — no middlemen at all.</strong> ARPANET, the internet’s ancestor, was designed so every machine could talk directly to every other machine. There was no “cloud.” The centralized, everything-goes-through-a-server model we take for granted today is actually a <em>later</em> patch, not the original design.</p><p><strong>2. That patch exists because we ran out of addresses.</strong> In the early ’90s, engineers realized IPv4 was going to run out of unique addresses for every device on Earth. Their emergency fix, introduced in 1994, was NAT — Network Address Translation — which lets many devices share one public address. It saved the internet from a real crisis. It also accidentally made direct connections between two random computers much harder, which is the entire reason STUN and TURN had to be invented decades later just to undo the side effect.</p><p><strong>3. Skype used to route your calls through strangers’ laptops — on purpose.</strong> For most of its early life, Skype was a peer-to-peer network. Some users’ computers were quietly promoted to “supernodes” that helped route other people’s calls, without those users necessarily realizing it. Skype didn’t move to centralized, company-run servers until years later.</p><p><strong>4. BitTorrent gets <em>faster</em> the more popular a file is — the opposite of a cloud server.</strong> A busy cloud server slows everyone down as more people request the same file. BitTorrent, built in 2001, does the reverse: more people sharing a file means more sources to download pieces from simultaneously, so popular files often move faster, not slower. It’s one of the most efficient distribution systems ever built, and it works on the same core idea Sendrop uses — go direct when you can.</p><p><strong>5. WebRTC exists because Google bought a company most people have never heard of.</strong> In 2011, Google acquired a small firm called Global IP Solutions and released its video-calling core technology to the world for free, as an open standard, instead of keeping it proprietary. That single decision is why virtually every video-calling app today — and, by extension, tools like Sendrop — can move data browser-to-browser without asking anyone’s permission or paying a licensing fee.</p><p><strong>6. WebRTC has no “unencrypted” mode. It’s not optional.</strong> Unlike a lot of “secure” file tools where encryption is a checkbox or a premium feature, WebRTC’s spec requires encryption (DTLS-SRTP) for every connection. There is no version of it that sends your data in the clear — it’s not a setting you can turn off, because it was never built with one.</p><p><strong>7. A file transfer with no cloud storage step is, structurally, almost impossible to intercept later.</strong> If a file only ever exists on two devices — sender and receiver — for the few minutes a transfer takes, there’s no database of files sitting around somewhere to be breached, subpoenaed, or scanned six months from now. Most cloud services technically <em>can</em>access what passes through their servers, because it lives there, even briefly. A direct connection never gives anyone that option.</p><h3>Where Sendrop Fits In</h3><p>Sendrop is built exactly around this direct-first model:</p><ul><li><strong>No login.</strong> Open it, drop a file, get a link.</li><li><strong>No file size limit.</strong> There’s no cloud storage to hit a cap on.</li><li><strong>No cloud storage.</strong> On a direct connection, your file never touches a server — it goes browser to browser.</li><li><strong>TURN fallback when needed</strong>, so the transfer still completes even when direct P2P isn’t possible — just a bit slower.</li><li><strong>Free, for now.</strong> Direct transfers cost almost nothing to run, so they’ll likely stay free. The TURN relay path may eventually need a small fee to sustain, since relaying data isn’t free — but that’s a future decision, not a current one.</li></ul><p>Try it here: <a href="https://sendrop.xyz/"><strong>sendrop.xyz</strong></a></p><p>It’s for the same person who’s always defaulted to WeTransfer or Send Anywhere out of habit — students sending project files, developers sharing build artifacts, or anyone who just wants to get a file from A to B without creating an account first.</p><h3>Getting the Fastest Possible Transfer</h3><ul><li><strong>Keep both tabs open</strong> until the transfer finishes — there’s no persistent storage to resume from later.</li><li><strong>Same network = fastest.</strong> Sender and receiver on the same Wi-Fi means a nearly instant direct connection.</li><li><strong>If it feels slower than expected</strong>, you’re likely on the TURN fallback path rather than a direct connection — it still works, just at relay speed instead of direct speed.</li></ul><h3>Further Reading</h3><ul><li><a href="https://webrtc.org/">WebRTC official site</a> — the open project behind the browser-to-browser protocol</li><li><a href="https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API">MDN: WebRTC API</a> — technical reference for how it works under the hood</li><li><a href="https://www.rfc-editor.org/rfc/rfc8656">RFC 8656: TURN</a> — the spec for how relay fallback works</li><li><a href="https://www.rfc-editor.org/rfc/rfc8489">RFC 8489: STUN</a> — the spec for how devices discover their own network address</li></ul><p>Next time you’re staring at an upload bar, remember: the internet’s original design didn’t need one. That’s the whole bet behind <a href="https://sendrop.xyz/"><strong>Sendrop</strong></a> — drop a file, share a link, no middleman required.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5ac9c5f77d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>