On Tools and Tempests: What TYPO3 Might Learn from a Kernel Argument

First of all: I’ll follow whatever will be decided. Still let me add my own personal opinion, which you don’t need to like or follow. But the dialogue day showed me we need to speak up and listen to each other.

For me, it is mostly about: Ethics and Environmental impact. Does TYPO3 want to be built with something that’s leading to a faster destruction of our own world? Does TYPO3 want to be built on something unethical? For me the entire AI topic is unethical and destroying our world way faster than we do anyway. That’s the two main reasons why I still refuse to actually even give AI a try.

We do open source, we say we want to respect people ( https://docs.typo3.org/permalink/guide-policy:coc-basic-rules ). This is also political, this is about humans. If I’m not mistaken @oli4 also said we should think broader than just TYPO3, we should think about humanity and our impact in the world.

Using AI has an impact, it says: We are fine with the companies that build the “tools” and how they build them. And I’d like to say no: We are not fine with that. And we are also fine with destroying our own environment for ourselves quicker. It is okay to destroy islands and lives. Which I find strange for an open source project that want to expand in the world.

We should also respect that there is a huge community out there that is against AI, e.g. take https://codeberg.org/ethical-foss/open-slopware .

Anyway, I’m happy if there is a decision, and we can focus on other things than to think and discuss this topic. But maybe this topic will come up anyway from time to time, as things might change and need a new decision.

Also in the end: You never know if any contribution was done with help of any AI. So the decision made by TYPO3 as project will mainly be a statement and impact how others think about AI. And some might follow the decision and contribute or not contribute with help of AI. But some might just not care, maybe not even read the decision, and contribute with or without AI anyway.

One addition: TYPO3 itself is suffering from the AI landscape, maybe Server Team has more concrete insights. But it seems the ydeploy Anubis to block AI scraper on various parts of our own infrastructure, e.g. see: Slack and some meeting minutes. Anubis right now seems to be deployed in front of:

So we as TYPO3 already fight against AI scrapers.

So TYPO3 would, if it allows AI contributions, somehow say it is fine to increase the resource usage and pressure on our own infrastructure, as well as everyone elses infrastructure.

5 Likes