<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Alert-Hub.org CTO Journal</title>
    <link>https://blog.alerting-apps.net/</link>
    <description>Technical notes, experiments, announcements, and working documentation from Alert-Hub.org projects.</description>
    <atom:link href="https://blog.alerting-apps.net/feed.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Wed, 22 Jul 2026 15:40:00 GMT</lastBuildDate>
    <item>
      <title>Active Mirrors for Official CAP Feeds</title>
      <link>https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-07-22-active-cap-feed-reflector/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-07-22-active-cap-feed-reflector/</guid>
      <description>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.</description>
      <pubDate>Wed, 22 Jul 2026 15:40:00 GMT</pubDate>
    </item>
    <item>
      <title>A Human-Readable View of Alert Hub Monthly Reports</title>
      <link>https://blog.alerting-apps.net/posts/cap-aggregator-workbench/2026-07-22-monthly-report-viewer/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/cap-aggregator-workbench/2026-07-22-monthly-report-viewer/</guid>
      <description>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.</description>
      <pubDate>Wed, 22 Jul 2026 15:25:00 GMT</pubDate>
    </item>
    <item>
      <title>Keeping CAP Alerts Readable as Browsers Retire Native XSLT</title>
      <link>https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-07-22-cap-xml-after-browser-xslt/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-07-22-cap-xml-after-browser-xslt/</guid>
      <description>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.</description>
      <pubDate>Wed, 22 Jul 2026 15:20:00 GMT</pubDate>
    </item>
    <item>
      <title>Tightening the CAP Profile for Flood Hub Guidance</title>
      <link>https://blog.alerting-apps.net/posts/flood-hub-guidance-feed/2026-06-13-flood-guidance-cap-profile-alignment/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/flood-hub-guidance-feed/2026-06-13-flood-guidance-cap-profile-alignment/</guid>
      <description>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.</description>
      <pubDate>Sat, 13 Jun 2026 13:20:00 GMT</pubDate>
    </item>
    <item>
      <title>Telegram Targets for CAP Alerts in multi-channel-relay</title>
      <link>https://blog.alerting-apps.net/posts/multi-channel-relay/2026-06-10-telegram-targets-for-cap-alerts/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/multi-channel-relay/2026-06-10-telegram-targets-for-cap-alerts/</guid>
      <description>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.</description>
      <pubDate>Wed, 10 Jun 2026 15:35:00 GMT</pubDate>
    </item>
    <item>
      <title>multi-channel-relay for CAP Alert Fan-Out</title>
      <link>https://blog.alerting-apps.net/posts/multi-channel-relay/2026-06-10-multi-channel-relay-for-cap-alert-fan-out/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/multi-channel-relay/2026-06-10-multi-channel-relay-for-cap-alert-fan-out/</guid>
      <description>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.</description>
      <pubDate>Wed, 10 Jun 2026 10:45:00 GMT</pubDate>
    </item>
    <item>
      <title>Measuring Controlled Vocabulary Term Salience</title>
      <link>https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-05-vocabulary-term-salience/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-05-vocabulary-term-salience/</guid>
      <description>A new vocabulary salience model records archive-wide evidence for controlled terms, so vocabulary discussions can be grounded in observed CAP alert usage.</description>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Making Background Automation Observable</title>
      <link>https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-05-background-automation-system-audit/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-05-background-automation-system-audit/</guid>
      <description>A missing auto-loaded source exposed a useful operational gap: background register sync needed a durable audit trail, consistent instance identity, and an admin view.</description>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Turning Flood Guidance Into CAP</title>
      <link>https://blog.alerting-apps.net/posts/flood-hub-guidance-feed/2026-06-03-flood-guidance-cap-experiment/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/flood-hub-guidance-feed/2026-06-03-flood-guidance-cap-experiment/</guid>
      <description>A field note on an experiment that polls Google Flood Hub flash-flood guidance, reconciles warning changes, and can publish generated CAP alerts through multi-channel-relay.</description>
      <pubDate>Wed, 03 Jun 2026 16:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Andorra Adds a CAP Feed</title>
      <link>https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-03-andorra-cap-feed-fah-update/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-03-andorra-cap-feed-fah-update/</guid>
      <description>News from Eliot: the Filtered Alert Hub sources file now includes Andorra's operating MeteoAlarm CAP feed, with alert content available in Catalan, Spanish, French, and English.</description>
      <pubDate>Wed, 03 Jun 2026 15:15:00 GMT</pubDate>
    </item>
    <item>
      <title>Reporting, Legacy Cleanup, and SNS Push Ingest</title>
      <link>https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-03-reporting-legacy-sns-ingest/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-03-reporting-legacy-sns-ingest/</guid>
      <description>A note on monthly reporting, legacy compatibility observation, and a default-off SNS push ingest path through the canonical alert pipeline.</description>
      <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Controlled Vocabularies for CAP</title>
      <link>https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-03-controlled-vocabulary-exports-skos-oet/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/alert-hub-v2-node/2026-06-03-controlled-vocabulary-exports-skos-oet/</guid>
      <description>A technical note on controlled-vocabulary work for CAP emergency alerting: versioned OET exports, SKOS RDF/XML, archive keyword analysis, and reusable embedding metadata.</description>
      <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Context S3 connections can be copied safely</title>
      <link>https://blog.alerting-apps.net/posts/multi-channel-relay/2026-05-27-context-storage-connection-copy/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/multi-channel-relay/2026-05-27-context-storage-connection-copy/</guid>
      <description>A note on copying context-owned S3 storage connections without exposing credentials in the browser, plus a quieter card-based editing workflow.</description>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>ah-cap-commons moves to Jackson 3 and JDK 25</title>
      <link>https://blog.alerting-apps.net/posts/ah-cap-commons/2026-05-27-jackson-3-jdk-25-upgrade/</link>
      <guid isPermaLink="true">https://blog.alerting-apps.net/posts/ah-cap-commons/2026-05-27-jackson-3-jdk-25-upgrade/</guid>
      <description>A compatibility note on moving the shared CAP XML model to Jackson 3 and JDK 25 while preserving the existing model shape.</description>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>