> Seafile and its desktop and mobile clients are published under GPLv3 with one exception -- the seafile's logo of desktop and mobile clients must be kept when redistribution.
Uhh, that does make it impossible to fork the project under a new name? Also this isn't mentioned anywhere in License.tx which appears to be a run-of-the-mill GPLv3 license file.
Interestingly enough GPLv3 itself states the following:
> If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.
Does that mean that I can just ignore their logo requirement?
So they say it's open source, but there is no link we the source is hosted and how it is actually "verified by the community". In addition it feels somehow weird that they have a free community version and a pro version that has more features and non-open source code. So if I would choose the pro version for features I'm still on the dark side of the moon when it comes to trusting their source code...
edit: I found the source on github, but still missing the relation between pro and community...
I was also alarmed by the fact that they do not have a link to their source code on their website. I did some searching and found that they host their code publicly on Google Code [1]. They really should place a link to their source on their website. I was really confused when I clicked the "Open Source Edition" button only to be presented with binaries.
Snowden claims that encryption works, and I have no reason not to believe him on that. There definitely is significant amount of people doing crypto research who are not (directly) affiliated with NSA, I'd suspect that they all collectively can not either have missed any intentional backdoors or been bought off by NSA.
Yes, if you have nothing of interest for the NSA. Otherwise almost every encryption could be subverted with an access to the servers and soldering gun - you just touch the body of the guy that has knowledge of the keys on the (im)proper places with it.
Uhh, that does make it impossible to fork the project under a new name? Also this isn't mentioned anywhere in License.tx which appears to be a run-of-the-mill GPLv3 license file.