im working on a p2p file transfer app. at the moment its a close-source webapp, but i hope to work towards some selfhosted options as seen on my other projects.
the storage is local-only from your browser/device. so like “the cloud”, but the cloud storage capacity is made up of your devices.
ive recently updated the landing page and i hope ive got it as simple as possible to transfer a file from one device to another.
im looking for feedback on the experience.
(Note 1: its still a work in progress. if there is an issue, you can usually refresh the browser and try again)
(Note 2: it seems important to mention: this app is not libre software. This needs more consideration to see if I can align to this. For information and open-source examples of the code in action, take a look at the docs and github for decentralized chat)
Closed source and a crowded market.
Sorry to say, but I don’t think you understand the audience for this.
If it’s not open source then forget about it, it won’t go anywhere. I’ve had that stance of all software for decades now, but in the last few years boat loads of others have caught on.
Its simple really. If the software is open source (ALL of it, servers, clients) we can all check it and all be sure it does what is advertised. If not, we have no way of knowing what you’re doing, especially on the server side of things, and if we’ve finally collectively learned on thing, it’s that we can’t trust companies on the server side of things. Data WILL be used in other ways than advertised.
Since this software is supposed to be a security product, trust is paramount, and it’s bot there at all. Unless this product would be open source I won’t even look at it.
Cool project, but it seems to be very similar to PairDrop with the major downside of not being open-source. What would be the advantages of using this project over existing FOSS-solutions?
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.
Foss or gtfo. Im not letting a black box see my files. I dont care what you claim, I have been burned before.
I tried foss. I couldn’t get it to work so i’m trying something different.
I’m the farthest thing from an expert when it comes to programming, etc., but my understanding was that the FOSS end of it is more about which license you use to distribute, and whether or not you provide the code to the public?
I don’t really understand how that would affect the functioning of the app itself. But again, I’m not a programmer so maybe I’m missing something here.
I’m no expert on the matter of licences either. I made the open source code some bsd licence because some of the dependencies called for it.
I created some code and made some open source. I don’t have to apply that to all my projects.
So it’s like croc, but closed source?
I have a weird setup with open and closed source.
I have open source examples of this code in action. If interested: https://github.com/positive-intentions/chat
I understand you want to make money from this, but for privately sending files, the much more mature and free open source projects will be greatly preferred. So I dont see this app going anywhere. Closed source doesn’t lend itself to privacy all that well. Gl.
