Facebook’s BSD+Patent license combo fails not because of the license itself but because it ignores the deeper nature of open source.
In July 2017, the Apache Software Foundation effectively banned the license combination Facebook has been applying to all the projects it has been releasing as open source. They are using the 3-clause BSD license (BSD-3), a widely-used OSI-approved non-reciprocal license, combined with a broad, non-reciprocal patent grant but with equally broad termination rules to frustrate aggressors.
The Apache Software Foundation has moved the “Facebook BSD+Patent grant” license combination (FB+PL) to its “Category X” licensing list, effectively banning inclusion of any software under FB+PL from Apache projects. That included RocksDB, which has consequently just dropped FB+PL and added the Apache License v2 on Github, and React.JS which does not look like it will resolve the issue so fast.
Update, 22 September: Facebook has announced it will switch React to the MIT license.
Here’s what we know so far (subject to updates, last day’s in green, latest marked 🆕): Continue reading
The acquisition of virtual reality company Oculus VR by Facebook was announced this week to mixed reactions. Most negative were those who had enabled the Rift VR goggles to be created in the first place — the backers on Kickstarter who provided nearly $2.5m to see the dream become reality. One prominent backer, the founder of Minecraft creators Mojang, was especially upset, deciding that Minecraft will not collaborate with Facebook. In a blog post he wrote:
I did not chip in ten grand to seed a first investment round to build value for a Facebook acquisition.
Maybe there’s more to the Facebook acquisition of WhatsApp than just the centralised consolidation of users and user information that Simon denounced in his previous InfoWorld article. Perhaps this particular addition to their portfolio is Facebook’s move towards becoming the first truly global telco!
The idea makes a lot of sense; not only is the world already familiar with the technology, WhatsApp has the same phone numbers that legacy telcos use, without the need to pay for connection fees across the world’s analog phone network. It’s almost amazing it hasn’t happened already, but conditions for a global telco have only recently become so ideal. Smart phones and globally available internet connections mean the moment has come and the big question remaining is, who’ll get there first?
Read Simons take on the potential for a global telco in his InfoWorld article.
Facebook’s acquisition of WhatsApp gains them almost half a billion users worth of telephone data. We can fully expect them to share their user information once joined, adding a wealth of phone data to Facebook and fleshing out WhatsApp with both Facebook’s data and the results of Facebook’s powerful semantic search. This sort of centralisation avoids giving users control of their own data.
To create a more positive environment in which users retain control of their data, what’s needed are more federated projects. Projects which offer the ability for suitably capable users to run their own service that can federate as a full peer, extending the service without surrendering full control. Diaspora and WordPress are two high profile examples of what federated services can look like, but there are many more available. All are open to user control in addition to service provider hosting.
If we are to maintain control of our own data in the future, federated services offer us much more hope than the route Facebook and WhatsApp are going down. Read more in this weeks InfoWorld article.