DeepText: Facebook's text understanding engine

Re:DeepText: Facebook's text understanding engine by daveguy on Wednesday June 01, 2016 @10:52PM (#11820042)

This pisses me off to no end. When I disable something like web browsing history because I get a nagging feeling that Google knows more about me than it should.

Then on the way out of work I try an "OK Google. Directions home"[0] to get a time estimate or best route estimate and it tells me I have to turn on browser history to continue or some other such bs. I wonder when Google Now will understand "Ok google. F?!k you Google."

[0] correction: that's more likely "ok Google. OK Google! OK GOOGLE! Damnit (click google now, click microphone). Directions home."

[ Parent | on HN ]

Re:DeepText: Facebook's text understanding engine by gvurrdon on Thursday June 02, 2016 @04:34AM (#11821113)

This particular point was rather annoying, and involved working around it in this manner:

Me: "OK Google, navigate home" Google: "You need to turn on web and app activity." Me: "OK Google, navigate to $NUMBER $STREET, $TOWN." Google: "No problem".

But, they then decided that web and app activity was essential in order to give me commute information, and the only way I found around this was to turn it back on and start doing almost all my searches via Duckduckgo.

[ Parent | on HN ]

Re:DeepText: Facebook's text understanding engine by daveguy on Thursday June 02, 2016 @10:32AM (#11822710)

I have done the same thing. My default search engine is now duckduckgo. Changing the default theme to blue/green (upper right corner) made a huge difference. I don't know why duckduckgo uses a black and gray color scheme that essentially does not distinguish between link/site/description. Makes the results appear very muddled when they are, in fact, usually comparable to google.

[ Parent | on HN ]