Flutterby™! : Google extracting from the commons

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Google extracting from the commons

2024-04-26 23:25:40.319088+02 by Dan Lyke 0 comments

This Metafilter comment on the decline of Google is such a wonderful summary of how, once Google has always been somewhere on the spectrum between cooperative player in an ecosystem and extractive, and how the extractive nature has become overwhelming:

My phrasing of this point differs, but not in disagreement or criticism, just as another way to view it through the lens of wnissen's really excellent phrasing above:

"The original intent of Backrub was to profit off of the work of Internet curators without paying them for their time creating high-quality sites."

Which is the essence of the modern AI content theft problem as well, only starting twenty-five years ago. Once Google's full-text search devalued the effort of curators, most of the unpaid ones stopped doing it at all. Later on, the paid ones got replaced by algorithms. Which means that today, Google Search no longer has the data necessary to function as designed.

[ related topics: Nature and environment Work, productivity and environment Mathematics Net Culture Artificial Intelligence ]

comments in ascending chronological order (reverse):

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.