GitHub now supports 451 status code for DMCA blocked content

The 451 status code is now supported | GitHub Developer Guide https://developer.github.com/changes/2016-03-17-the-451-status-code-is-now-supported/

GitHub now returns a 451 HTTP status code for repos that have been blocked/removed due to a DMCA notice.
The new 451 code should be used in place of a generic 403 to indicate that content is not available for legal reasons. The reason is likely to be a DMCA notice, but could be used for content that has license restrictions, or other legislative or regulatory blocks.

onwCloud, CERN, and petabytes of data

As a result of this, for ownCloud 9.0 we developed new Storage and Sharing APIs, which make it possible to write storage connectors that access and use advanced capabilities and metadata directly from the storage. One example is the EOS filesystem that is developed and used by CERN to store and manage their huge amount of scientific data. This filesystem can provide metadata, such as ETags, FileIDs, and more, which can be used by ownCloud 9.0 directly, avoiding the need to store this in the ownCloud database and providing the sought-after reduction in overhead. The option to leverage existing sharing capabilities of the storage layer (if available) is also possible, which removed the need to store sharing information in the central database.

— Open collaboration: ownCloud, CERN, and AARNET | Opensource.com https://opensource.com/business/16/3/cern-and-owncloud?sc_cid=70160000000q67aAAA

The new release of ownCloud 9 brings a number of new features including improvements to the API that allows CERN to use ownCloud as a frontend to their massive data store. Other new features beef up the Libre office based collaboration tools and add additional storage options.