There are some false positives in that dataset, but I would still recommend it if you really want to err on the side of caution and don’t mind the false positives. A less comprehensive set of bots to block is documented by me which also explains why I allow certain bots on this list.

Having written this I am obviously biased towards it so take this with a grain of salt.

Scrapers I block (and allow), with explanations

Here’s my thought process when deciding whether to block a scraper from seirdy.one, the scrapers I block, the scrapers I allow, and the ways I block them.

^{Seirdy’s Home}

Thx for your link and efforts @Seirdy !

All this said, being part of a decentralized web, as pointed out in this toot, our publicly visible interaction lands on other instances and servers of the #fediVerse and can be scrapped there. I wonder if this situation actually might lead, or should lead, to a federation of servers that share the same robots.txt "ideals".

As @Matthias pointed out in his short investigation of the AI matter, this has (in my eyes) already unimagined levels of criminal and without any doubt unethical behavior, not to mention the range of options rouge actors have at hand.

It's evident why for example the elongated immediately closed down access to X's public tweets and I guess other companies did the same for the same reasons. Obviously the very first reason was to protect their advantage about the hoarded data sets to train their AI in the first place. Yet, considering the latest behavior of the new owner of #twitter, nothing less than at least the creation of #AI driven lists of "political" enemies, and not only from all the collected data on his platform, is to be expected. A international political nightmare of epical proportions. Enough material for dystopian books and articles for people like @Cory Doctorow, @Mike Masnick ✅, @Eva Wolfangel, @Taylor Lorenz, @Jeff Jarvis, @Elena Matera, @Gustavo Antúnez 🇺🇾🇦🇷, to mention a few of the #journalim community, more than one #podcast episode by @Tim Pritlove and @linuzifer, or some lifetime legal cases for @Max Schrems are at hand.

What we are facing now is the fact that we need to protect our and our users data and privacy because of the advanced capabilities of #LLM. We basically are forced to consider to change to private/restricted posts and close down our servers as not only the legal jurisdictions are way to scattered over the different countries and ICANN details, but legislation and comprehension by the legislators is simply none existent, as @Anke Domscheit-Berg could probably agree to.

Like to say, it looks like we need to go dark, a fact that will drive us even more into disappearing as people will have less chance to see what we are all about, advancing further the advantages off the already established players in the social web space.
Just like Prof. Dr. Peter Kruse stated in his take about on YT The network is challenging us min 2:42 more than 14 years ago:
"With semantic understanding we'll have the real big brother. Someone is getting the best out of it and the rest will suffer."

Fehler offenbar behoben

Habe aufgrund Deines Hinweises mal das PHP-Log von Uberspace aktiviert. Das dauerte sehr lange und hatte schon durchs Einschalten dutzende ERRORs im sehr langen Logfile.
Dann auf die PHP-Version auf 8.1 umgestellt und erneut das PHP-Log aktiviert. Drei Zeilen im Log und "ready to handle connections".

Laut History war zuvor PHP 8.0 aktiviert und war wohl Ursache des Problems. Irgendetwas muss vergangene Nacht bei Uberspace verändert worden sein.

Die Instanz läuft nun wieder erwartungsgemäß und Deine Hilfe bei der Konsole hat mich auf die Spur gebracht.
Vielen vielen Dank dafür!

Das war zwar wirklich herumstochern im Nebel, aber oft reichen grobe Indizien, um ein Problem einzugrenzen. Von Beginn an war da das Gefühl, es liegt in der Infrastruktur begründet. Daher auch zunächst die Tests bezüglich DNS, Quota usw.

Es brauchte nur den passenden Funken - Logfiles. Ich arbeite einfach zu selten auf dieser Ebene, um von selbst darauf gekommen zu sein.

Zeit für den zweiten Versuch eines Liberapay-Kontos. Hatte bei einem früheren Versuch 2021 keine Einzahlung hinbekommen oder einfach das Prinzip nicht verstanden.