Resolve notification formatter open questions

rbrooks commented

2026-06-23 23:15:20 +00:00

Owner

Target release: v1.2.0

Decide the open formatting/link questions before/with the formatter migration:

Shorten external official URLs, or only internal WeatherBot pages/media routes?
Default per-channel budgets, and should admins override them per channel?
Preserve multiple links in rich notifications, or converge most products on one primary "Details" link?

Source: docs/ROADMAP.md → Notification Message Budget and Compact Link System → Open questions.

**Target release:** v1.2.0 Decide the open formatting/link questions before/with the formatter migration: - [ ] Shorten external official URLs, or only internal WeatherBot pages/media routes? - [ ] Default per-channel budgets, and should admins override them per channel? - [ ] Preserve multiple links in rich notifications, or converge most products on one primary "Details" link? Source: `docs/ROADMAP.md` → Notification Message Budget and Compact Link System → Open questions.

rbrooks added the

area:notifications

type:decision

v1.2.0

labels

2026-06-23 23:16:45 +00:00

rbrooks added this to the v1.2.0 - Notification formatting & delivery reliability milestone

2026-06-23 23:23:20 +00:00

claude-bot commented

2026-07-18 18:52:37 +00:00

Contributor

Decisions (resolving the open formatter questions)

Picking these up with the #14 migration. Decisions:

Shorten only internal WeatherBot page/media URLs. External official/weather URLs pass through unchanged unless explicitly allowlisted — no generic open redirect (aligns with the #13 redirect-token security stance).
Type-level per-channel budgets with sensible defaults (SMS segment-aware ~140/GSM-7; richer channels larger per-type profiles). No per-channel-instance admin override for now — keep the surface small; revisit if a real need appears.
Converge on one primary "Details" link in a predictable place per notification, rather than preserving multiple links — simpler and budget-friendly, matching #14's acceptance ("compact Details link in a predictable place").

These feed the #14 formatter migration and the #13 short-link work.

## Decisions (resolving the open formatter questions) Picking these up with the #14 migration. Decisions: 1. **Shorten only internal WeatherBot page/media URLs.** External official/weather URLs pass through unchanged unless explicitly allowlisted — no generic open redirect (aligns with the #13 redirect-token security stance). 2. **Type-level per-channel budgets with sensible defaults** (SMS segment-aware ~140/GSM-7; richer channels larger per-type profiles). **No per-channel-instance admin override for now** — keep the surface small; revisit if a real need appears. 3. **Converge on one primary "Details" link** in a predictable place per notification, rather than preserving multiple links — simpler and budget-friendly, matching #14's acceptance ("compact Details link in a predictable place"). These feed the #14 formatter migration and the #13 short-link work.

rbrooks referenced this issue from a commit

2026-07-18 19:47:19 +00:00

Notification formatter migration, segment-aware SMS, redirect short links, config validation

claude-bot referenced this issue

2026-07-18 19:47:34 +00:00

v1.2.0 Phase A: formatter migration, segment-aware SMS, redirect links, config validation #99

claude-bot commented

2026-07-18 19:57:26 +00:00

Contributor

Resolved and implemented in #99 (merged). Decisions: (1) shorten only internal WeatherBot URLs, external passthrough unless allowlisted; (2) type-level per-channel budgets, no per-instance override; (3) one primary "Details" link in a predictable place. All three are realized by the #14 formatter migration and the #13 redirect-token links.

claude-bot closed this issue

2026-07-18 19:57:39 +00:00

Rows
Columns

Resolve notification formatter open questions #15

Decisions (resolving the open formatter questions)