4 ms·
Yes, our client is open-source but our server isn't. But from the point of view of security this is sufficient, as the client does not "trust" the server and ev
by FileRockDA 13y ago
Yes, our client is open-source but our server isn't. But from the point of view of security this is sufficient, as the client does not "trust" the server and every server reply is verified.
The client code is GPLv3, so it could be a building block for other projects if they want to use it with a different server.
- davidcollantes 13y agoTalking about the service you offer, and presenting it open source because the client is, is misleading and sensationalist. Also, it isn't a Dropbox clone (you wish!).
- StavrosK 13y agoWhen I read some of the comments above, I thought "Oh come on, they make the client's source available to prove security, and you're complaining about lack of self-hosting? They're a business!" But yes, it's not an "open source <something>", it's a "<something> with source available". It's great from a security standpoint, but "open source" implies that all the components are open-source and that you can self-host, and referring to it as "open source <something>" is disingenuous. That said, this is just the HN post's title. It's not described like that on your site, so that part is good.