Human Creations

Last year I wrote about how you can use ActivityPub, through the Fediverse to publish your own content, and being in control of it.

As part of a recent keynote that I gave at the Dutch PHP Conference I returned to this subject, but also reflected on what happens with the content you publish, and your rights over it.

Because in the last year, it has become clear, that lots of large and wealthy companies, don't really care about the latter.

What I mean by this becomes clear with the following examples.

When Gary Gale one day went to visit his Vaguely Rude Places Map site, he found that (AI) bots had eaten through his map tile allowance. He now hosts his site behind Cloudflare, being beholded to a Big Tech™ company again.

When I look at the web server logs for the php.net sites, I see that most of the uncached requests come from bots.

This also happens to other large sites, such as OpenStreetMap, which got hit by AI DDos Scraper Bots requesting an extreme amount of content from 100,000+ IP addresses; or Fediverse instances, such as infosec.exchange, which had to deal with more load.

All this scraping comes at a cost, but not to the scrapers, nor the users of these tools.

Although the content is freely available, the services hosting content still need to be funded. Instead of you giving up your privacy, you will need to pay for those with actual money for them to thrive, and exist.

But AI impacts content in other ways as well.

I need to be clear of what I mean with AI. I don't mean the visual recognition models to detect cancer faster, sifting through loads of data to find patterns, fraud detection, speech recognition, translation services, or deciphering my terrible handwriting.

I specifically mean Generative AI through LLMs — for articles, source code, and "art".

I have no beef with the actual technology either, only the exploitative nature of how these currently are created and hyped up.

Just like the Luddites weren't against new technology, but how this technology was used to exploit them.

A photo of my two books — © Derick Rethans

I have written two books in my life, many years ago. The material in them has been slurped up into the LLMs, and one of them was originally part of the Anthropic law suit where they settled for using pirated copies of the books.

Mind you, not for using the book as training material.

Although the settlement was for 1.5 billion dollars, I still ended up getting nothing, as only American authors were compensated.

There are similarities with the code that I, and many others, have written.

Code, published under an open license. But these licenses often require attribution. How much attribution is now given when one of your chat bots produces parts of my code?

Nothing.

Which means that these tools are in breach of the licences under which the original code was published, and hence shouldn't exist.

Unfortunately, some governments, like mine in the UK, are less concerned about AI companies stealing content, although there are some indications that they've changed their tune.

I never gave permission for any of my content, be it books, code, nor photos, to be used by these tools, but they're still making money of it.

As a matter of fact, they are not only making money of it, but also making it a lot harder to host things ourselves by driving up costs for CPUs, GPUs, memory, and storage.

They are literally stealing things to sell back to us, whilst at the same time making sure we have to use their services as it is becoming too costly to have a decent set up in our homes and offices.


But lets get back to content. I like writing. I am not great at it, but I find it pleasing to show others what I have worked on, and the adventures I have had.

I write for humans, and therefore, I also expect that when I read something, it is also written by humans. I prefer to be able to see the writing style of specific authors, as that is part of the experience. They own their voice.

In my case, that has always been including em-dashes wherever I can.

What I do not like to read is generic and bland text. Text that has no weird grammarisms, flair, or emotions.

That is text that comes out of LLMs: Generic slop.

I feel the same about AI "Art".

Over-polished generic images and logos, that you see more and more on signs in front of shops, the Web, and in presentations at conferences.

Not only do I find them boring, it is also taking work away from actual artists. I thought that computers were around to do the boring monotonous work?

AI takeover — © Tjeerd Royaards — Used under licence

This cartoon, by Tjeerd Royaards, nails it on the head.

Unlike AI companies slurping up all content on the Internet, I asked the author for permission to include this into my presentation.

He said no. — "I don't allow the free use of my work, as I depend on my drawing to make a living"

So I went and purchased a digital license.

And this makes perfect sense.

Quality content created by artists, authors, and software professionals is worth something important. And these creators need to be rewarded for their creative work.

Unlike the AI slop generators, I value original art: Writing, photos, images, and source code.

Content by humans, for humans.

Shortlink

This article has a short URL available: https://drck.me/human-creations-k5v

Comments

No comments yet

Friday Night Dinner: The Island

I had many a pint in The Island when I moved to London 16 years ago, as it was the closest reasonable pub. I don't remember haven eaten there, but having walked past more recently, I suggested it for a Friday Night Dinner.

On a rainy evening we headed to this pub in the middle of a residential neighbourhood. It was already buzzing outside, with people hiding away from the rain under the awnings, smoking away. My wife could also unfortunately smell this cigarette smoke when seated inside, close to a window, which put her off the food.

For our starter, we picked a scotch egg to share. It was nicely flavoured with a runny yolk, and was served with a sweet curry sauce. For my main I choose the slow roast free-range pork belly, served with white beans, winter kale, salsa verde. The skin wasn't particularly very crackly, and a little chewy at times. The white beans were OK, but could have been a bit softer too. My wife had the onglet steak, which was served with gentleman's relish and fries. The fries were nicely cooked and crispy, but the steak was cooked medium to well-done, rather than the ordered medium rare.

But what left down the meal, and the Island experience generally was the haphazard service. Upon arrival, it was speedy, although my wife, who arrived first, had to wait quite some time for the table to be prepared. We felt left to our own devices after our mains. It took a very long time for the dessert menu to show up, and then a significant amount of time before we could request, and then receive the bill.

One of my personal pet peeves in restaurants is that when the bill is presented, the waiting staff often do not have the payment terminal with them, and have to go and fetch it separately. This is a waste of everyone's time especially as we'd like to get going, and I'm sure the restaurant would like to fill the table with some more paying guests. In this case with the meal being mediocre it was more annoying than usual.

Unfortunately The Island didn't live up to my memories, nor our expectations, and it seems unlikely we'll be back for a meal or drinks.

Scotch Egg
Scotch Egg
1 / 3
Slow Roast Pork Belly
Slow Roast Pork Belly
2 / 3
Onglet Steak with Fries
Onglet Steak with Fries
3 / 3

Shortlink

This article has a short URL available: https://drck.me/the-island-k5p

Likes

Comments

No comments yet

Friday Night Dinner: Sunday in Brooklyn

James Street is full of restaurants. It's near Oxford Street and Bond Street, so an excellent place to enjoy a meal after a hard day of shopping, if that's your thing. We hadn't done any shopping, but after a week at work, a relaxing dinner is always welcome.

Sunday in Brooklyn is their second venue — their first one is in Notting Hill — and styled after a Brooklyn Brunch spot. So good for breakfast (weekdays) and brunch, but they also serve dinner in the evening.

We were seated in the front room with a bunch of other pairs of diners. The vibe was relaxed. The menu is fairly extensive with starters, salads, Italian plates, burgers, and mains. We weren't overly hungry, so picked the corn ribs to share as a starter. These were cut into quarters, slightly crispy, and were served with a slightly underwhelming peanut-flavoured dip (it wasn't really necessary as the corn ribs were delicious by themselves). They weren't the easiest to eat — fingers required — but yet very tasty.

For her main, my wife selected the flame grilled salmon. This came with a smashed avocado and pineapple salsa. Although tasty, the salsa being cold, whilst the salmon was hot, was a little odd. On the side, she also had a green bean and almond side, which worked better with the fish than the cold salsa. I had the grilled sirloin steak, with a peppery three pepper sauce, and served with a side of crispy and garlicky fries.

After our mains, we did have a look at the dessert menu, but opted against it. Even though our waitress was highly recommending having the Sunday Pancake™ that they're apparently famous for. We were too full— maybe something to try another time.

We enjoyed our Friday meal at Sunday in Brooklyn, and perhaps we should come back and have an actual brunch, and then also try their signature pancakes.

Corn Ribs
Corn Ribs
1 / 5
Grilled Sirloin Steak
Grilled Sirloin Steak
2 / 5
Flame Grilled Salmon with Salsa
Flame Grilled Salmon with Salsa
3 / 5
Green Beans with Almonds
Green Beans with Almonds
4 / 5
Fries
Fries
5 / 5

Shortlink

This article has a short URL available: https://drck.me/sunday-in-brooklyn-k4b

Likes

Comments

No comments yet

Become a Patron!
Mastodon
GitHub
LinkedIn
RSS Feed
Flickr
YouTube
Vimeo
Email

My Amazon wishlist can be found here.

No AI Webring
previous | random | next

Life Line