⋔ about ⋔ contact ⋔ licensing ⋔ oostats ⋔ wiki ⋔ support ⋔ keys ⋔ faq ⋔ archives ⋔
307 words by gman999 written on 2017–03–24, last edit: 2017–09–03, tags: advocacy, bsd, relays ⋔ Previous post: March in Amsterdam ⋔ Next post: Tor Relay on a BeagleBone Black Running OpenBSD -current
A lot of major firms use BSDs. You just aren’t probably aware of them.
From WhatsApp to Juniper and Netflix, and blue-chip storage vendors like NetApp and Isilon, the BSDs are quietly omnipresent.
Some use the BSDs in their infrastructure, others use BSD code in their products. The liberal BSD license places negligible restrictions on the code usage, but doesn’t compel firms to publicize it.
The BSD license, whether the two- or three-clause versions, are catered for developers to share code, in that they are clear and succinct, and don’t require a lawyer to interpret them. Of course if you ask a lawyer, they will try to convince you legal counsel is necessary for reading a menu at a restaurant.
Many of the firms contribute code back into the BSD projects, a number also provide infrastructure, while others donate to projects such as OpenBSD and FreeBSD.
There’s always room for a little more.
TDP is going to be putting out a public call in the near future, asking BSD-employing firms to run a Tor relay on their preferred BSD. These entities already maintains the infrastructure, staff and know-how and can easily work in another bare-metal server into their operation.
In December 2014, the Mozilla Foundation began running 12 Tor relays. TDP believes this is an effort that needs to be replicated by BSD-using firms and entities. Hosting relays as corporate infrastructure provides legitimacy to online free speech.
BSD firms running Tor relays benefits the BSDs, the privacy enhancing community and the firms themselves, and our open letter should clearly make that case.
Copyright © 2015–2018 by The Tor BSD Diversity Project (TDP). All Rights Reserved.