Google and Twitter are teaming up to share data on the sex offender and child porn database

TechCrunch article Google is partnering with Twitter and Yahoo to create a searchable database of sex offender records, with the aim of “making it easier for law enforcement to find and prosecute criminals.”

The database, which Google acquired from Yahoo in June, has already provided police with names, photos, dates of arrest, and addresses of alleged offenders.

The service also provides information on child porn, but this time the data will be tied to a specific database.

The news comes amid a spate of arrests for child sex crimes and related offenses, including cases of sexual assault and harassment.

The database will be accessible to the public via the Google search interface, with Google CEO Sundar Pichai promising that it will be a “full-featured search engine” that will “provide the best possible data for law-enforcement, and the media as well.”

While it’s unclear if the search engine will be integrated into Google’s existing criminal databases, it’s a big step forward for a company that has long been criticized for its reluctance to engage in data-sharing with law enforcement.

Google has previously denied sharing the names of people who have been convicted of sex crimes with law-makers and others.

It also has an “adult search” feature, which has a long history of being used by companies like Facebook to track users and to identify people who are likely to be involved in sexual activity.

The company also previously refused to reveal the names and locations of individuals it has arrested.

Redis database migration to Amazon Elasticsearch

By Peter HynesThe latest version of the Redis Docker Engine is now available for AWS Elasticsearch.

The new version has some major improvements, including support for a wide range of metrics including time-series and search, as well as the ability to migrate between database snapshots.

The Docker Engine version 1.1.2 is available from Docker Hub and the new version 1, 1.2 and 1.3 are available on the Redistributable Releases page.

In addition to the new release, there are also a couple of fixes and improvements.

The first is a bug in the search field, which has caused a few problems in the past.

The second is a memory leak in the default configuration.

It seems the memory leak has been fixed, but there’s no update on whether the other fixes will fix the leak in a future release.

The most notable change is the ability for the Elasticsearch module to run on EC2 instances that are running Redis on top of the EC2 instance.

This can be a very handy feature for deploying to multiple EC2 environments.

Redis and Amazon ElasticSearch have a long history.

In 2012, Amazon released a version of Redis based on the EC3 version of EC2, while the ElasticSearch version of Amazon Elastic is based on EC3.

The two projects share the same naming scheme and both are built on top the Redisc for Java module.