- cross-posted to:
- [email protected]
- privacy
- privacy
- cross-posted to:
- [email protected]
- privacy
- privacy
cross-posted from: https://lemmy.ml/post/26803468
https://positive-intentions.com/
A webapp for P2P E2EE messaging and file transfer. its a fairly unique approach to secure messaging.
the project isnt ready to replace any existing apps or services, but given the competative market for this kind of project, id like to push it out to get feedback.
i made an attempt to create documentation on the website, but otherwise feel free to reach out with questions about how it works.
Eepy
No audits and doesn’t want to share the code
https://www.reddit.com/r/crypto/comments/1iumxl3/how_far_can_i_push_closesource_code_towards_being/
if youre asking for an audit, i expect you have an idea that they arent cheap. its simply beyond my means. the project is too complicated for pro-bono work.
the chat app (which contains file-transfer capabilities) is open source. id like to develop the p2p capabilities into a SaaS and so its logical to lean towards close-source for the “file” app.
Thank you for chiming in!
I can definitely respect your desire to build something that can support you and I wish you luck. It’s a cool concept and I really like the idea for it. I’m definitely not your target audience as I’m not interested in closed platforms after experiencing enough rug pulls, nor am I interested in privacy-focused applications that aren’t completely open source under a strong copyleft license with reproducible builds. I suspect that many in the privacy community feel the same way. However, if your tool makes it easy for Alice to send Bob (neither of whom have ever used your service) a 300 GB file and do video calling/screen sharing without hassle then I imagine you’ll have some users.
EDIT: I see in that reddit thread that you haven’t found being open source to be much of a draw. That makes sense to me. At this point, I don’t view being open source as a positive, I view it as basic table stakes. Being open source with a strong copyleft license and a DCO instead of a CLA to prevent relicensing approaches being featureful to me. It’s unfortunate how many projects use a CLA with copyright transfer. Signal fails in this regard, for example. It may be possible for Whisper to relicense future releases to something that is not truly free.
thanks for your reply.
can i do both? the chat app is completely open source. thats the thing i wanted to get traction on, but it doesnt seem to be working. which is understandable with things like bugs and audits missing.
so for a new approach with “file” i’m creating an app that is simplified to being purely for file transfer. i hope this simplication can also lead to more stable functionality to hopefully get to a level where it can send 300gb over webrtc. id like to this approach to remain close source so that i can create something competative in the market for file-transfer.
Sad to hear