thanks!

im a developer im not much of an expert on licences of any kind. i created code and decided to open source it here: https://github.com/positive-intentions/chat . when i say the close source app is "based on" the open source code, i hope it doesnt undermine that it itself is a fully functional p2p messaging system (im of the opinion that all projects will always need refinement). anyone with issues about close-source code should take a look at the open-srouce version. its basically more functional but it seems too complex to maintain as open source andd thus this new project.

id like to offer the statics as a zipped folder. this is in the roadmap, but the code will be minified and obfuscated. about as opaque as possible for "source available". i dont know much on the matter, but id like to learn more about if this can be made into libre software. its hardly modifyable or studyable.

while i dont want you to "trust me bro", i am actively developing it and improving the functionality. so that static bundle will have to be build by the CI/CD and it will update along with the app. it goes without saying, the project is not mature enough to have things like security audits.

thanks! for your feedback there! ahh the connection bugs. unfortunately this is is one of the trickier bugs. im working towards fixing that asap. i have an idea of a fix, but im trying to avoid rewriting a core piece. have you tried closing the app on both devices and trying again (sorry, i know its a bit cliche).

if its not a secret, can you maybe tell me more about your LAN setup for me to set something up and try? i certainly aim for it to "just work".

If interested in how it works and to see code examples, this project is based on my beefier open-source code seen here: https://github.com/positive-intentions/chat

People in here are either wannabe snowden or sell some grass

By the way this is a maintaned fork of your Android Client: https://github.com/iyox-studios/iyox-Wormhole

Thanks. I hope to get to a point where I can make the experience as seamless as workhole.

To compare solutions, a key details around providing my app as a webapp, is to avoid the requirement of a client. this opens up the set of compatible platforms.

(Note: it's a common request for me, so by popular demand, i will aim to provide binaries for the major platforms.)

Strong title needed for strong claims.

Its based on open source code. https://github.com/positive-intentions/chat . I'd be happy for feedback on that too.

Webrtc would be able to outperform all other methods for transfer speed (useful for when sending larger files)

I'm sure there is a market for eople who want to transfer files. With a zero-installation, zero-registration, it should make it easy for people to get started.

Thanks for the empassioned speech/statement!

Perhaps you'd be interested in one of my open source projects. It's a beefier version of the app presented in the parent post.

https://github.com/positive-intentions/chat

On the point about open source, it isn't easy to pull off. I can confirm it isn't the case that open-source be flooded with some kind of collective community review/support. It's been an option for the chat app for a while and I've tried actively promoting it, it's clear that the project is simply too complicated.

I'm a bit disappointed in how hard I tried on the open source project for it to not get the traction I wanted. To create somthing close-source and competitive in the file-transfer space is only logical at this point.

I'm sure with an enthusiastic speech like that, you're doing your part for supporting the open source community. Unfortunately I couldn't figure out how to get it to filter down to me.

Absolutely. Also, it probably is in your best interest to advertise details of your cryptography. What data is shared with whom, what algorithms are used, etc.; if you're doing something more exotic / low-level, Alice-Bob diagrams can be helpful. I'm not sure what other people do but when looking at security-sensitive software, the first thing I do is look for the cryptographic setup and research it.

Thanks.

I have a similar open source project. https://github.com/positive-intentions/chat

My general thoughts are that it isn't sustainable. While it clearly isn't a contender in the messaging-apps market, I think it demonstrates a unique concept in how it works as a webapp.

For me, it's an achievement for it to be comparable to those tools. I aim to get to a similar feature set and make the user experience intuitive.

Thanks!

Here is the foss equivalent of this project: https://github.com/positive-intentions/chat

Unfortunately, open source isn't sustainable. I'm investigating close-source as a way to create something competitive. My plan is to try to sell it on the Play store.

As for pairdrop, their approach to peer discovery relies on knowing the network you're connected to. This makes it easy to find peers in cases where you use the same WiFi network. In mine I'm using WebRTC to allow connections over the internet. Peer discovery is achieved by using crypto-random IDs exchanged as a link or QR code.

Ultimately it's worth noting my app is a work in progress. I hope I can update the UX to make the functionality as seamless as pairdrop.

Nice! Can you tell me more about zero-knowledge encryption?

In my app I'm using asymmetric encryption to exchange a symmetric encryption key (Diffie-helman). I'm curious about other approaches for P2P authentication.

Thanks!

Perhaps you'd like to give feedback on a separate but similar foss project: https://github.com/positive-intentions/chat

I haven't heard of Dibbles. Can you point me to their site?

This is using the WebRTC protocol. As a webapp it's immediately good to go, there isn't a need to run something like a FTP server.

Of course limitations apply like sending larger files nukes my ram... But I after it's sent, it seems to settle down.