GlobalFileRegistry provides a centralized database that contains the unique identifiers of millions of infringing files captured and collated on behalf of multiple content owners, where “unique identifier” means a filehash, URL, Content Management System ID or other means of uniquely identifying a particular data item on any of the network types supported by Global File Registry.
Adding content to the GlobalFileRegistry database
We provide each content owner and their employees with secure authenticated login to the GlobalFileRegistry database via a BackOffice interface. Content owners can log in to quickly register and assert that a particular content item is owned by them and should be taken down on a particular search engine, torrent site or P2P network.
An additional Web Services Interface allows content owners to batch-register ownership of thousands of unique identifiers. Instead of employees needing to manually enter the unique identifiers for thousands of files, content owners can connect their databases, or the databases of companies they already contract to patrol search engines and P2P networks, directly to the GlobalFileRegistry database.
Content owners can either use this Web Services Interface themselves, or they can contract with 3rd-party companies – including companies who provide audio and video fingerprinting services – to input unique identifiers into the Global File Registry database on their behalf.
Web site connectors
Web site web search engines, torrent sites and social networking sites who subscribe to Global File Registry’s file take-down service can connect directly to the Global File Registry server using our file taken-down Web Services Interface. Your server(s) can then periodically connect to ours to receive a feed of the latest take-down notices from GlobalFileRegistry. This allows you to automatically and seamless remove those files from you database, so that they no longer appear on your web site or as search results in your search engine.
P2P networks work in a very different way to web sites and typically can’t make use of the Web Services Interface used by web sites and search engines. Accordingly, GlobalFileRegistry services the file- and user- take-down requirements of P2P networks via a proprietary “P2P connector”.
The P2P connectors comes in two halves: A Server-side Connector, which runs on Global File Registry’s servers, and a Client-Side Connector, which is bundled with supporting P2P applications.
The P2P network developer ships the Client-Side Connector with their P2P application. Each time the user performs a P2P search or tries to download a file, the P2P application passes the filehash of each file returned as a search result, or of the file the user has requested to download, to the Client-Side Connector, and requests the take-down status of that filehash.
The Client-Side Connector makes contact with the Server-side Connector, requesting the status of those file hashes. This is done over an encrypted and authenticated channel, ensuring that results cannot be tampered with.
The result is that files marked with take-down notices in the GlobalFileRegistry database simply disappear from supported clients on that P2P networks, and don’t even show up as search results.
Through its extensive P2P knowledge and experience, GlobalFileRegistry is uniquely able to build these connectors and publish take-down information into supported P2P networks.
The DMCA requires that, in addition to removing infringing files, repeat infringing users also need to have their accounts disabled. Since most decentralized P2P networks don’t have any user login capability, in order to provide the fastest possible implementation time (i.e. you want to go live tomorrow!), our Client-Side Connector provides a complete user login and take-down system. Working in conjunction with supporting server-side login and registration pages, the Client-Side Connector provides your P2P application with a ready-to-go secure, authenticated and encrypted login system. We’ll even give you the complete ready-to-use server-side ASP.NET code. If you don’t have any servers capable of acting as login servers, we can host your user login on our servers.
The DMCA requires that, in the event that a file is incorrectly taken down, that the file can be restored within 48 hours. Accordingly, the Global File Registry database and Connectors support such file put-back functionality.
With millions of P2P clients each generating periodic requests for filehash take-down status on multiple files, clearly the system needs to be architected for massive scalability. The Global File Registry system has been engineered to meet this demand. Scalability is achieved through a number of methods, including but no limited to:
- a client-side cache avoids multiple lookups for a given identifier in any one session,
- the grouping of multiple requests into a single signed data packet reduces client-server traffic,
- ultra-fast in-memory hash lookup tables allow a single server to process tens of thousands of content identifier lookups per second
- patent-pending filtering on P2P supernodes prevents infringing shared files from being indexed by the network, dramatically reducing the client-side filtering requirements.
Global File Registry customers can log into the GlobalFileRegistry BackOffice to view comprehensive file and network statistics showing the number of take-downs issued for their content, or for their search engine or P2P network, view an audit trail showing which of their employees logged in and issued take-down notices, and more.