Re:MEGA source code
by binarycrusader on Saturday January 28, 2017 @12:14PM
(#13507462)
Which appears to be a violation of GitHub's terms of service, which explicitly require the ability to fork projects:
"By setting your repositories to be viewed publicly, you agree to allow others to view and fork your repositories."
Re:MEGA source code
by true_religion on Sunday January 29, 2017 @05:00AM
(#13513411)
Independent development (forking) doesn't imply that you can redistribute those versions to arbitrary parties.
At least someone can review the code, but is this enough to trust them? I am talking about the people who really worries about their files on cloud storage services.
Re:MEGA source code
by notyourwork on Saturday January 28, 2017 @11:27AM
(#13507151)
It is not enough as this does not assert they are executing this code and not a modified version.
How would one go about asserting that?
Lately I've spent some time contemplating how to establish trust in cloud services, this particular nut I haven't been able to crack yet.
Interesting problem, right? Not an expert in the area, but blockchain implementers say they solve this issue. Afaik then there isn't one trusted party, but anyone can compile and run the code and be a provider (and be paid), and a single untrustworthy party won't bother because his chances of compromising the user's data is small.
Whatever they release, there is no way to prove that that is the code that is actually running on their servers.
Re:MEGA source code
by imatworkyo on Saturday January 28, 2017 @11:16AM
(#13507053)
is open source the point here?
[0] https://github.com/meganz/MEGAsync/blob/master/LICENCE.md