<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: maste</title>
    <description>The latest articles on Forem by maste (@masettermusk).</description>
    <link>https://forem.com/masettermusk</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3626163%2Fdcaffc82-8ca0-4bc4-9e77-2db34a7b3875.png</url>
      <title>Forem: maste</title>
      <link>https://forem.com/masettermusk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/masettermusk"/>
    <language>en</language>
    <item>
      <title>ZetaShare | Building Truly private file transfer with WebRTC</title>
      <dc:creator>maste</dc:creator>
      <pubDate>Sun, 23 Nov 2025 21:34:07 +0000</pubDate>
      <link>https://forem.com/masettermusk/zetashare-building-truly-private-file-transfer-with-webrtc-35jp</link>
      <guid>https://forem.com/masettermusk/zetashare-building-truly-private-file-transfer-with-webrtc-35jp</guid>
      <description>&lt;p&gt;I built ZetaShare because I wanted a file transfer service that doesn’t spy on me — no tracking, no data collection. The project was inspired by ToffeeShare, but after seeing it abandoned and being unable to contact the developers, I decided to build my own alternative.&lt;/p&gt;

&lt;p&gt;In case you're curious about how the system works under the hood, here’s a simplified explanation of the current architecture:&lt;/p&gt;

&lt;p&gt;How ZetaShare works (simplified):&lt;/p&gt;

&lt;p&gt;The sender uploads a file on the website. The server doesn’t store the file — After uploading, the sender receives a 6‑digit ID. This ID becomes the identifier for the transfer session.&lt;/p&gt;

&lt;p&gt;The receiver opens the link with the ?id= parameter, for example: &lt;a href="https://zetashare.com/?id=123456" rel="noopener noreferrer"&gt;https://zetashare.com/?id=123456&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;When the receiver joins the link, the server sends the receiver’s SDP offer to the sender. (This is part of the WebRTC signaling process.)&lt;/p&gt;

&lt;p&gt;The sender responds by sending back their own SDP answer.&lt;/p&gt;

&lt;p&gt;Both sides then exchange ICE candidates through the server.&lt;/p&gt;

&lt;p&gt;After the WebRTC handshake is complete, a direct P2P connection is established between sender and receiver — and the file starts transferring directly between the two devices.&lt;/p&gt;

&lt;p&gt;So the server is only used for:&lt;/p&gt;

&lt;p&gt;exchanging SDP offer/answer&lt;/p&gt;

&lt;p&gt;relaying ICE candidates …and nothing else. No file, no metadata, no tracking.&lt;/p&gt;

&lt;p&gt;Once the WebRTC connection is established, all data flows peer‑to‑peer, fully outside the server.&lt;/p&gt;

&lt;p&gt;What works now:&lt;/p&gt;

&lt;p&gt;WebRTC P2P transfers — files go directly between users.&lt;/p&gt;

&lt;p&gt;No metadata collection — unlike other services that send file metadata through signaling servers (like ToffeeShare), our server only handles SDP and ICE candidates.&lt;/p&gt;

&lt;p&gt;No accounts required — just drag, drop, and share.&lt;/p&gt;

&lt;p&gt;Unlimited file sizes.&lt;/p&gt;

&lt;p&gt;Completely free — no ads at all.&lt;/p&gt;

&lt;p&gt;What’s missing (in my view):&lt;/p&gt;

&lt;p&gt;Only TLS (WebRTC’s built-in), no proper end-to-end encryption yet.&lt;/p&gt;

&lt;p&gt;No password protection.&lt;/p&gt;

&lt;p&gt;Links will have an expiration option soon.&lt;/p&gt;

&lt;p&gt;Mobile file transfer speed needs improvement.&lt;/p&gt;

&lt;p&gt;Coming next:&lt;/p&gt;

&lt;p&gt;Password protection&lt;/p&gt;

&lt;p&gt;File expiration option&lt;/p&gt;

&lt;p&gt;Mobile performance improvements&lt;/p&gt;

&lt;p&gt;Proper end-to-end encryption&lt;/p&gt;

&lt;p&gt;Try it out: &lt;a href="https://zetashare.com" rel="noopener noreferrer"&gt;https://zetashare.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;These are the features I could think of, but if you have better ideas, I’d love to hear them. I can’t promise to build everything, but I’ll definitely try.&lt;/p&gt;

&lt;p&gt;I’m using AI to help me because my English isn’t perfect — sorry if it sounds a bit AI-generated!&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>programming</category>
      <category>productivity</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
