Last update on 09.05.2022 …

We have updated our TOS § 7 Copyright and Database rights to make clear, that content included in or provided or served through any BKA.li service will remain with the respective owner…

We’ve decided to ban the communities !privacy@lemmy.ml, !privatelife@lemmy.ml as well as !Technology@lemmy.ml because they were moderated by a narcissistic Drama Queen who gets aggressive and d…

We are going to drop Plume on blog.bka.li.
With almost any update there are new problems, which kills the complete instance, without that anything is written down on their Gitea instance or any other places, where one could search. …

Due to increased activity of known and extremist trolls whose only purpose in life is obviously to spread hate, lies and agitation because they are clearly overwhelmed and/or dissatisfied with their own lives, from the USA and Sweden, as well as the…

English version below …

When you want to test, e.g. federation from Mastodon, … feel free to use this post…

Sorry for the misfunctioning search today. With the last update came an undocumented setting to the settings.yaml for searx, which broke the result page.
I’ve fixed both searx instances, the live one with the dynamic ip, and the fallback instance…

Due to multiple attacks via 12 different IP addresses against our mail server, we now block the complete network range of Serverion BV (AS211252).
Affected ranges:…

Because BKA.li don’t offer any platform for toxic and abusive internet user, I added additional rules for spamassassin for directly kick such bad users out of all mailboxes I’m running. Especially for contact option I offer for teleyal.blog and support for [BKA.li](https://bk…

When I open a news page, I want to read the news and no comments from disgruntled nutcases who clutter the internet with their nonsense!..

I’ve started an Uptime-Kuma in addition to the default status page to be more transparent for the services provided by BKA.li…

Sorry for the short outage this morning. Normally I’m able to move services without any downtime to another server, but I forgot an option, I have on this domain, which changed the DNS zone automatically.
The problem has been solved and should not occur again…