Slashdot Mirror
Google Search Now Uses Service Worker For Repeated Searches (venturebeat.com)
An anonymous reader writes: Google Search is now using Service Worker to cache repeated searches, loading results twice as fast. The tidbit was shared this week by Dion Almaer, Google director of engineering, and Ben Galbraith, Google senior director of product, at Pluralsight Live in Salt Lake City, Utah. "Google Search's mission is to get relevant results to you as quickly as possible," Almaer said onstage. "So they invested in the largest deployment of Service Worker probably out there by being able to extra work on the fly and give you results sometimes twice as fast."
Is there any way to prevent Google from using Service Worker? That would be far more valuable to me than being able to repeat a search in half the time.
Akira though
Is waiting for a web search to return the results actually thing people sit and wait for? I can't remember ever having to wait, even when having to use dial-up. It smells like a non-news item, trying to get users to go back to google.com.
I can’t say that I’ve ever thought “these search results loaded too slowly”. I have, on the other hand, said “why doesn’t Google do something about these pages which somehow manage to get highly ranked but don’t actually contain content which answers my question?”
#DeleteChrome
I can’t say that I’ve ever thought “these search results loaded too slowly”.
I just opened up Google and typed: "Are you slow Google?" The first line said "About 705.000.000 results (in about 0,45 seconds)". Yeah. There's a lot of things to complain about but speed of loading results is not one of them.
But only if you've already asked the same thing before.
And only if you don't care for anything that happened since the LAST time you searched.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
I haven't seen all the details yet, but the description of those "Service Workers" suspiciously sound like yet another vector for tracking the user's browsing across different web sites. I for one sure want that everything related to a web-site is gone from my computer when I close the last browser tab related to that web-site. And I do not want any "background service" implanted into my browser from visiting some site.
Whatever 'Service Worker' is...
Search results are no longer about what you want, it is about what everyone else wants. What web publishers want; what advertisers want; what politicians want; what corporations want; what governments want; what google wants; and finally, just maybe, they might include what you want.
I have, on the other hand, noticed that the DNS TTL for google.com is 300 seconds. Isn't that too low? Is it really necessary for a DNS server to check with google every 5 minutes?
Actually I use DDG as my default engine - have for a year or two. But occasionally when I don't get the search results I want, out of old habits I fall back to Google... and am invariably disappointed.
#DeleteChrome
No you clearly didn't get anything.
At best you could claim from my post that there are 705million answer to the question. But they could be 705 million "NO!"s
These service workers are underpaid minions for the tech giant, slaves that come running every time those upper class pages make a request. It's the gig economy, exploiting workers who linger in the background, hoping for something to do. Shamefully discarded when there isn't enough for them to do. They're probably using foreign undocumented code, too!
> You mean sites that already have full control over everything on the page?
> They are relatively tame, highly restrictive and can only affect the site they belong to.
Is what they said about JavaScript. There aren't any vulnerabilities associated with JavaScript, right?
The same origin policy is a good idea, but browsers and web developers keep screwing it up, over and over again. Cross site request vulnerabilities and the most common type of vulnerability there is, according to HackerOne.
( https://www.zdnet.com/article/... )
Cross site request forgery is another huge issue.
Regarding "can only afford the site they belong to", the docs for service workers should be read as "we wish service workers only affected the same site, and they'll be CVEs issued for many of the thousands of different flaws which allow sites to install service workers affecting other sites".
He must be so overworked!
I have noticed on the occasional google test (the geek thing to keep track), they have been getting worse and more biased, more advertiser friendly, except when they are not. I noticed they would kick the advertisers regular search results, 'below the fold', when they served up the ad, to get you to click the ad and make the advertiser pay for that search, because the end user did not see them in the results and clicked the ad instead. Really bent that. You pay google ads words for worse google searches, greedy is as greedy does. So you know google's search algorithms now incorporate a whole range of adwords algorithms, which ever serves the most profit for them at the time or in the most crazy way, serves the political ideology of the board and fuck the investors.
What is it with tech companies and that delusion of total power, why does it always infest the minds of it's board members and get seemingly rational people to do insane things for this quarters return when it will kill the company over the long term.
Chaos - everything, everywhere, everywhen