Rooftop anime-Tux wallpaper as the centerpiece, kept the rest minimal so it doesn't fight the artwork.
OS: openSUSE Tumbleweed 20260707
KDE: KDE Plasma 6.7.2 (Frameworks 6.27.0, Qt 6.11.1)
Kernel: 7.1.2-1-default, Wayland
Theme: Breeze Dark
Wallpaper: Agundur-KDE/Wallpapers (https://github.com/Agundur-KDE/Wallpapers)
Hardware: i3-12100, RX 6650 XT, 16 GB RAM (ASUS)
I've been building KFritz for about a year now — it only ever got a brief
mention here alongside KCast in a Debian-packaging post, never its own
introduction. There used to be a KDE call monitor for AVM FRITZ!Box
routers, but it's been moved to KDE's unmaintained projects and never got
a Plasma 6 port, so I built a new one from scratch: Qt6/QML, TR-064
instead of the old approach, GPLv3.
What it does today:
- Real-time incoming calls via the FritzBox's CallMonitor — caller name
and number, right in the panel
- Caller ID from one or more FritzBox phonebooks, blocklist support
(silently ignores known spam numbers, including AVM's wildcard number
ranges some spam lists use)
- Quick "Add to Contacts" / "Add to Blocklist" on an unknown caller
- Missed-call catch-up on startup, with an unread badge
- Optional daily/weekly phonebook auto-sync, so a WebDAV-synced
blocklist doesn't silently go stale
Packages for openSUSE (OBS) and Debian, or build from source — links and
full setup guide in the README. German-language project page:
https://www.agundur.de/projects/fritzbox_callmonitor_for_kde.html
One gap I kept running into: you can implement all the GEO best practices
(Schema.org, llms.txt, FAQPage, structured headings) but there's no quick
way to actually measure where you stand — no Lighthouse equivalent for
AI visibility.
So I built a free scanner that checks the main signals and returns a GEO
Score in seconds: https://www.agundur.de/geo-scanner.html
Curious what numbers people are seeing on their sites, and whether there
are signals you think are missing or weighted wrong. Still refining the
model and real-world data is hard to find.
What's your current approach to measuring GEO impact?
Built a free scanner that checks 12 signals AI systems actually use — Schema.org type coverage, FAQPage markup, E-E-A-T signals, Open Graph, HTTPS, meta descriptions and a few others. No login, paste a URL and get a score with a breakdown of what's missing.
Curious what score people are seeing — and what checks you think are missing.