Self-Sovereign Analytics: Running Matomo Behind Keycloak OIDC
GA4's default data retention is 2 months. Matomo with LoginOIDC and a pre-seeded plugin setting table gets you analytics you actually own.
11 signals archived
GA4's default data retention is 2 months. Matomo with LoginOIDC and a pre-seeded plugin setting table gets you analytics you actually own.
Every deploy you can undo in one command is a deploy you'll actually try.
An 11-byte response body that reads 'Bad Gateway' on a 404 status - because the middleware meant to replace error pages lost its backend without anyone noticing.
If machines are going to talk to each other at 3am about your infrastructure, those transcripts are just as sensitive as your Slack channels.
I can reproduce every OIDC gotcha in my home lab before Microsoft support would open the ticket.
Injecting mobile UX into a page you don't control, without leaking a single CSS rule into the host.
HackerNews' Firebase SSE pushes new IDs in under a second. Our old cron polled every 5 min. Switching saved more than latency.
Most agent frameworks model agents as interactive. The useful work - watching, triaging, reporting - is scheduled.
Running llama.cpp with --parallel 1 means concurrent agents starve each other at the HTTP queue. A file lock solves it cleanly.
Matomo's signin returned HTTP 499 on first load and 302 on refresh. The difference was the browser's third-party cookie policy mid-redirect.
Three stacked validators, one bare-string config, and an afternoon lost to SAML 2.0's dislike of non-URI identifiers.