People keep calling it private file sharing, then they make you upload the file to their server first.
You wait, they hold it, your friend pulls it back down from them.
Weird thing to call private.
1
20
That's mayo.pizza.
Pick a file or folder, drop them the pizza link. Browser to browser.
No account. We don't keep the file on the app server. Signaling just introduces the two tabs. If the direct path dies, encrypted bytes can go through a relay. Still unreadable to us.
1
1
24
Leave the sender tab open though. That's where the file actually lives.
mayo.pizza
Spread the link. Grab your slice.
1
ok real talk, your “peer-to-peer” file transfer app is probably lying to you about being peer-to-peer
1
15
your browser can stream files straight to disk btw (File System Access API), most apps are still just… shoving everything into memory like it’s 2015
that’s why your tab dies on big files
1
3
File transfer sites usually upload your file to their server first. mayo.pizza doesn't. Your browser sends it straight to whoever has the link. The server just connects you two, it never holds the file.
Drag a file in. Send the link. It goes browser-to-browser — my server never sees a single byte of it
12
just shipped mayo.pizza 🍕
files go browser to browser, no middle server. no account, no upload, nothing stored.
send a slice 👇 mayo.pizza
🤖 Made with AI
Sending a file shouldn’t mean parking it in someone else’s cloud first.
mayo.pizza streams it browser to browser. The file bytes aren’t stored on our application server.
## Spread the link. Grab your slice. 🍕
12
Sending a file shouldn’t mean parking it in someone else’s cloud first.
mayo.pizza streams it browser to browser. The file bytes aren’t stored on our application server.
Spread the link. Grab your slice. 🍕
Why upload your files to someone else's cloud when you can pass them browser to browser?
mayo.pizza streams files directly between peers. The file itself is never stored on our server.
Spread the link. Grab your slice. 🍕
mayo.pizza
