News for hackers. Stuff that matters.
Re:Building a Search Engine for Programmers by hyperpape on Saturday June 13, 2020 @05:35PM (#23512957)
Tools surrounding search history. Things like selecting results as your personal answers to a query, trying to determine when you're asking something you've asked before.

This is based on something Hillel Wayne wrote (@hillelogram) wrote on twitter not that long ago. The gist of it was it's ok that we're all using Google as part of our programming workflows, but why on Earth should we ever need to ask the same question twice? If you can find those threads, there might be more there than what I just said.

Obviously privacy is a concern here, but while I'm leery of Google knowing everything I do, I'm a lot happier with a technical search engine knowing which pieces of syntax I can't remember.

Re:Building a Search Engine for Programmers by mlthoughts2018 on Saturday June 13, 2020 @06:07PM (#23513222)
> “ why on Earth should we ever need to ask the same question twice?”

Isn’t it simple? I don’t want another entity to have data about my personal curated search results.

It’s fine for me if Google sees some essentially anonymous query for “apple” from me, and sees what I selected, and learns in aggregate what searches for “apple” means, maybe even with extra context that helps distinguish different modes in the results.

It starts being a huge problem if the next time I visit, Google first detects it’s me, looks up a special index of my selected results, and modifies the results to my query to be those.

Re:Building a Search Engine for Programmers by quickthrower2 on Monday June 15, 2020 @05:07AM (#23525353)
That horse has bolted