ZetaShare 构建基于 WebRTC 的私密文件传输
我创建ZetaShare是因为我想要一个不监视我的文件传输服务——没有追踪,没有数据收集。这个项目的灵感来源于ToffeeShare,但在看到它被遗弃并无法联系到开发者后,我决定自己构建一个替代方案。
如果你对系统的工作原理感到好奇,这里有一个简化的当前架构说明:
ZetaShare的工作原理(简化版):
发送者在网站上上传文件。服务器不存储文件——上传后,发送者会收到一个6位数字的ID。这个ID成为传输会话的标识符。
接收者通过带有?id=参数的链接打开,例如:https://zetashare.com/?id=123456
当接收者加入链接时,服务器会将接收者的SDP提议发送给发送者。(这是WebRTC信令过程的一部分。)
发送者通过发送自己的SDP应答进行回应。
双方随后通过服务器交换ICE候选者。
在WebRTC握手完成后,发送者和接收者之间建立了直接的P2P连接——文件开始在两个设备之间直接传输。
因此,服务器仅用于:
交换SDP提议/应答
中继ICE候选者……其他什么都不做。没有文件,没有元数据,没有追踪。
一旦WebRTC连接建立,所有数据都通过点对点方式流动,完全不经过服务器。
目前可用的功能:
WebRTC P2P传输——文件直接在用户之间传输。
没有元数据收集——与其他通过信令服务器发送文件元数据的服务(如ToffeeShare)不同,我们的服务器仅处理SDP和ICE候选者。
无需账户——只需拖放并分享。
无限文件大小。
完全免费——没有广告。
我认为缺失的功能:
仅有TLS(WebRTC内置),尚未实现真正的端到端加密。
没有密码保护。
链接将很快提供过期选项。
移动文件传输速度需要改进。
接下来要推出的功能:
密码保护
文件过期选项
移动性能改进
真正的端到端加密
试试吧:https://zetashare.com
这些是我能想到的功能,但如果你有更好的想法,我非常乐意听取。我不能保证会实现所有想法,但我一定会尽力。
我正在使用AI来帮助我,因为我的英语并不完美——如果听起来有点像AI生成的内容,请见谅!
查看原文
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.<p>In case you're curious about how the system works under the hood, here’s a simplified explanation of the current architecture:<p>How ZetaShare works (simplified):<p>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.<p>The receiver opens the link with the ?id= parameter, for example: https://zetashare.com/?id=123456<p>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.)<p>The sender responds by sending back their own SDP answer.<p>Both sides then exchange ICE candidates through the server.<p>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.<p>So the server is only used for:<p>exchanging SDP offer/answer<p>relaying ICE candidates …and nothing else. No file, no metadata, no tracking.<p>Once the WebRTC connection is established, all data flows peer‑to‑peer, fully outside the server.<p>What works now:<p>WebRTC P2P transfers — files go directly between users.<p>No metadata collection — unlike other services that send file metadata through signaling servers (like ToffeeShare), our server only handles SDP and ICE candidates.<p>No accounts required — just drag, drop, and share.<p>Unlimited file sizes.<p>Completely free — no ads at all.<p>What’s missing (in my view):<p>Only TLS (WebRTC’s built-in), no proper end-to-end encryption yet.<p>No password protection.<p>Links will have an expiration option soon.<p>Mobile file transfer speed needs improvement.<p>Coming next:<p>Password protection<p>File expiration option<p>Mobile performance improvements<p>Proper end-to-end encryption<p>Try it out: https://zetashare.com<p>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.<p>I’m using AI to help me because my English isn’t perfect — sorry if it sounds a bit AI-generated!