I am pretty sure the issue was a broken regex in a fail2ban config, trying to ban requests to ".so" files, but not scoping the check correctly to the request field in the logs. It triggered on the referrer containing ".social", so it blocked many instances

@foobarth Ne, tatsächlich nicht. Ich habe beschlossen, mehr von meinen "aktiven" Hobbies zu machen. Außerdem gibt es auf media.ccc.de und in den Mediatheken ja viel Content und von meiner Bücherei gibt es auch ein erstaunliches online Angebot an Serien, etc. Bei Nebula sind auch ein Paar der Kanäle, die ich gerne schaue. Aber ganz klar: alles nicht das gleiche, was YouTube zu bieten hat. Und in Ausnahmefällen werde ich wahrscheinlich auch in Zukunft noch (ohne Account) bei YT schauen

@ascherbaum How do you "correctly" write the number "twenty and a half" in German digits? It is "20,5" (with a comma, not a dot). It doesn't matter if the unit is mm, € or °. Eventually I gave up fighting software with decimal points and changed my locale. You are right - in most software, the _defacto_ standard is a decimal point (because it is US centric). digiKam does the right (but unhelpful) thing and properly adapts to how a _German_ expects the numbers (but not computers)

@ascherbaum It depends on what you mean by "valid coordinates" - they certainly are the valid ones for _your_ locale. The issue is that most programs (in this case OSM and GMaps) are US centric and only considers US number formatting as "correct". So technically digiKam is right here, but Google probably would never fix this. I don't know if there is a way in digiKam to ignore your global locale settings 🤔

@ascherbaum Looks like the issue is the (German) number format with a comma instead of a full stop. I don't know anything about this software, but you probably _could_ change your computer settings to use "." as a numerical separator (which would mess it up if you rely on the German format in other programs…)