this post was submitted on 23 Apr 2024
549 points (97.1% liked)

Technology

59569 readers
4136 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Edward Zitron has been reading all of google's internal emails that have been released as evidence in the DOJ's antitrust case against google.

This is the story of how Google Search died, and the people responsible for killing it.

The story begins on February 5th 2019, when Ben Gomes, Google’s head of search, had a problem. Jerry Dischler, then the VP and General Manager of Ads at Google, and Shiv Venkataraman, then the VP of Engineering, Search and Ads on Google properties, had called a “code yellow” for search revenue due to, and I quote, “steady weakness in the daily numbers” and a likeliness that it would end the quarter significantly behind.

HackerNews thread: https://news.ycombinator.com/item?id=40133976

MetaFilter thread: https://www.metafilter.com/203456/The-core-query-softness-continues-without-mitigation

you are viewing a single comment's thread
view the rest of the comments
[–] redcalcium@lemmy.institute 2 points 7 months ago* (last edited 7 months ago)

Just for some perspective, if you want to know how little reach the fedi post with the link to this blog post got: the first post in this thread already has more likes and boosts after less than a hour since posting it than my blog post ever did that he felt the need to confront me over.

The author is probably weren't aware that their blog post get a huge engagement on hacker news and the ceo got a lot of flak there, which was probably why he felt the need to reach out and "correct" the author.