Active Mirrors for Official CAP Feeds
A field note on the Alert Hub RSS reflector: an independently hosted mirror intended to keep official CAP alerts reachable when national network rules impede access across borders.
Project journal
Working notes from the Alert Hub codebase: CAP emergency alerting, controlled vocabularies, reporting, ingestion, interoperability, and the operational details where discussion and feedback would be useful.
Latest increments
Short implementation notes that connect design intent, code changes, and operational questions across the Alert Hub workspace.
A field note on the Alert Hub RSS reflector: an independently hosted mirror intended to keep official CAP alerts reachable when national network rules impede access across borders.
The finalised Alert Hub monthly report can now be read and explored in the CAP Aggregator, with Markdown and JSON downloads for reuse outside the application.
A field note on two ways to preserve human-readable Common Alerting Protocol documents after Chromium removes native XSLT: HTTP content negotiation and an experimental script-loaded XSLT processor.
A follow-up note on aligning generated Flood Hub guidance CAP with a narrower authority-facing profile: clearer sender identity, authority audience text, fewer optional elements, and a two-hour freshness window.
A field note on adding Telegram as a downstream target for relayed CAP messages, with context-owned target configuration and delivery receipts visible in the operator view.
A technical note for organisations that need to receive Common Alerting Protocol alerts and relay them safely to internal systems, public feeds, and operational partners.
Browse journal
My current emphasis is interoperability: CAP, OET, controlled vocabularies, SKOS, analytics, and operational workflows that other people can inspect, question, and reuse.