undefined | Better HN

0 pointssaurik7y ago0 comments

FWIW, you are in fact talking to a team of people who are core Free Software people (such as Brian Fox, who was the first person employed by the Free Software Foundation)... but like, it must be pointed out that your Tor library is almost certainly a client library, and the license of the Tor server you are accessing would not affect the ability for people to use it: "statically linking Tor" is kind of simplistic, as it assumes Tor is a monolithic component (and maybe it strangely is... I honestly have never looked much at its code).

In case it helps immediately clarify: you absolutely will be able to use the Orchid platform to build commercial, closed source distributed, semi-distributed, and even centralized applications.

For philosophical background on this, I encourage reading the position of Richard Stallman on why the Ogg Vorbis library should not be licensed under GPL. Our mission (to decentralize software and communication) causes similar quirks.

https://lwn.net/2001/0301/a/rms-ov-license.php3

(Exactly what the boundaries are on the components and under what license they will be released is thereby not yet finalized as we continue to work on architecture, but there are at least a couple things we are building that will seriously be released under 0-BSD.)

0 comments

1 comments · 1 top-level

kodablah7y ago

I appreciate your efforts and all efforts to improve privacy. The library I was referencing is actually for building Tor servers too, though even just its client part communicates with either a local Tor daemon or the statically linked Tor in the executable, both of which would be subject to the AGPL regardless of the server part. But if the principles are similar to the Ogg lib and liborchid is LGPL/BSD/MIT/Apache/etc then we are in complete agreement. Consider me as one of those that, when the core lib is built/available, will make things with it.

j / k navigate · click thread line to collapse