blymp.io is a webapp that allows you to easily transfer files between devices with high speeds. It uses modern technologies like WebRTC, Blobs and WebSockets to allow files to be transferred as fast as possible. And it's ad-free!
I browsing my bookmarks of file transfer services. I opened a nice one called lokki.cloud. But when I opened it, it redirected me to a way better version called blymp.io! I found it to be way easier to use then WeTransfer and most other services that I know! So I shared it on PH!
(lokki.cloud was made by @vantezzen, so I am not sure if he also made blymp.io.)
@oompietijn73 Hey Tijn, thank you for hunting blymp.io! 🚀
Yes, blymp.io is also made by me. It uses the same technologies as lokki.cloud under the hood (still Peer-to-Peer transfers with Socket as a fallback) but I've rewritten the frontend in ReactJS so it could be more responsive and in order for the code to be more maintainable.
I also changed the name as ".cloud" suggested that the files would be stored or transferred on my servers which is not the case (unless it falls back to sockets, then it will transfer them but not store them).
For anyone interested: Blymp.io is also completely open-source! https://github.com/vantezzen/bly...
Your product scared me a bit:)
I am working on a similar tool which will be launching soon. But my product is in a completly different domain altogether.
Great job.
So, how does it work? I didn't see any tutorial or anything informing users to get connected. Both devices need to be connected to internet or through local network?!
At least some sort of text indicating users would have been great.
@jack_vice Thank you for your feedback. I just published a new update to blymp.io that adds a tutorial to the homepage on how to get started. Let me know if this addition helped you getting started with blymp.io
@manishmshiva It looks like you haven't reaIly looked at the way this works, have you? You can't steal anyones files using the 4 digit code as you have to enter the code *before* you can even select the files. Additionally, the code is linked to the receiver, not the sender: If you somehow guess the code of someone else, the only thing you can do is trying to send one of your own files. Also, receiver codes are very short-lived: They are only valid for the few seconds to minutes it takes you to enter the code onto another device - after that the code cannot be used by someone else.
Of course you could now argue that someone could send you a virus by brute-forcing your receiver code, but in that case I trust the user to not open the files he received without even sending them.