{"id":3268,"date":"2013-05-05T10:28:10","date_gmt":"2013-05-05T16:28:10","guid":{"rendered":"https:\/\/www.roughtype.com\/?p=3268"},"modified":"2013-05-05T14:32:40","modified_gmt":"2013-05-05T20:32:40","slug":"all-ears","status":"publish","type":"post","link":"https:\/\/www.roughtype.com\/?p=3268","title":{"rendered":"Speak no evil"},"content":{"rendered":"

\"ears\"<\/a><\/p>\n

Slashdot notes<\/a> that Google has filed for a patent<\/a> on what it calls a “policy violation checker,” which comprises “methods and systems for identifying problematic phrases in an electronic document, such as an e-mail.” Here’s how it works:<\/p>\n

A context of an electronic document may be detected. A textual phrase entered by a user is captured. The textual phrase is compared against a database of phrases previously identified as being problematic phrases. If the textual phrase matches a phrase in the database, the user is alerted via an in-line notification, based on the detected context of the electronic document.<\/p><\/blockquote>\n

“Problematic phrases,” Google explains, “include, but are not limited to, phrases that present policy violations, have legal implications, or are otherwise troublesome to a company, business, or individual.”<\/p>\n

The patent application, which was published last week, sketches out various ways the service might work. For instance, the “in-line notification” could take the form of the immediate “underlining or highlighting” of the problematic or troublesome word or phrase as it’s typed. The notification could also be accompanied by “a hyperlink to a webpage.” The system could also use “machine learning techniques to identify problematic phrases without human intervention.”\u00a0Most interesting of all, the system could be programmed “to alert a third party to a match between a textual phrase and a phrase in the database.” For instance, “if a user creates a text document, presentation, or other document with a problematic phrase, the policy violation checker may notify a member of the legal department of the existence of the document.”<\/p>\n

One can imagine all sorts of immediate applications for a service that highlights and records “problematic phrases” as you type them. But it strikes me that the policy violation checker’s real potential will emerge only when Google perfects its neuronal interface \u2014 the one that Sergey Brin described<\/a> as “a little version of Google that you just plug into your brain.” At that point, policy-violation checking could become preemptive. The moment a problematic thought entered your mind, you would be alerted to the looming transgression and the thought would be deleted before it even reaches the expression stage. No one else would need know the incident ever occurred, except, of course, the designated third party.<\/p>\n

Photo via\u00a0x-ray delta one<\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Slashdot notes that Google has filed for a patent on what it calls a “policy violation checker,” which comprises “methods and systems for identifying problematic phrases in an electronic document, such as an e-mail.” Here’s how it works: A context of an electronic document may be detected. A textual phrase entered by a user is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-3268","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/3268","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3268"}],"version-history":[{"count":10,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/3268\/revisions"}],"predecessor-version":[{"id":3281,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/3268\/revisions\/3281"}],"wp:attachment":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3268"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3268"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3268"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}