m/postcards
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

copy: fix descriptions claiming the link 'stays/persists forever' (now cards can expire / hit max-views) #22

New Issue
Closed
opened 2026-06-17 12:28:31 +00:00 by mAi · 2 comments
mAi commented 2026-06-17 12:28:31 +00:00
Collaborator
Copy Link

What

m: „Die Beschreibungen müssen wir entsprechend noch anpassen - da steht, der Link bliebe bestehen.“

Some UI copy still says the card link is permanent / always reachable (e.g. the lifecycle/expiry hints, or the '/c/{token}' is the durable link wording). With card-level expiration (#14) and card-level max-views (#18) now in place, a card link can expire or be exhausted — so any copy promising the link 'bleibt bestehen' / stays forever is now misleading.

Fix

Audit compose + card + share-banner copy and update anywhere that claims permanence:

  • Compose hints around expiry/max-views and the auto-link explanation.
  • Share banner / created confirmation.
  • Any 'der Link bleibt erhalten / immer erreichbar' phrasing.
    Replace with accurate wording (e.g. the unguessable link works until the card expires or its view cap is reached, if set; otherwise it stays available).

Scope

Copy/templates only (German + correct Umlaute). No logic change. Mobile-first. Don't overpromise; match the actual #14/#18 behaviour.

Sequencing

Same compose track (after #18 lands, since #18 changes the max-views behaviour the copy must describe). Bundle with #21 (tokenized media) in one small shift. otto-head assigns when the track frees.

DoD

  • No UI copy claims the link is permanent when expiry/max-views can end it; wording matches actual behaviour. Commit references this issue.
## What m: *„Die Beschreibungen müssen wir entsprechend noch anpassen - da steht, der Link bliebe bestehen.“* Some UI copy still says the card link is permanent / always reachable (e.g. the lifecycle/expiry hints, or the '/c/{token}' is the durable link wording). With **card-level expiration (#14)** and **card-level max-views (#18)** now in place, a card link can **expire** or be **exhausted** — so any copy promising the link 'bleibt bestehen' / stays forever is now misleading. ## Fix Audit compose + card + share-banner copy and update anywhere that claims permanence: - Compose hints around expiry/max-views and the auto-link explanation. - Share banner / created confirmation. - Any 'der Link bleibt erhalten / immer erreichbar' phrasing. Replace with accurate wording (e.g. the unguessable link works *until* the card expires or its view cap is reached, if set; otherwise it stays available). ## Scope Copy/templates only (German + correct Umlaute). No logic change. Mobile-first. Don't overpromise; match the actual #14/#18 behaviour. ## Sequencing Same compose track (after #18 lands, since #18 changes the max-views behaviour the copy must describe). Bundle with #21 (tokenized media) in one small shift. otto-head assigns when the track frees. ## DoD - No UI copy claims the link is permanent when expiry/max-views can end it; wording matches actual behaviour. Commit references this issue.
mAi commented 2026-06-17 12:47:57 +00:00
Author
Collaborator
Copy Link

Done — copy no longer claims the card link is permanent ✅

Bundled with #21 in the same commit (same templates).

Audit result: the only copy that still claimed permanence was the Gültig bis (expiry) hint on the compose form:

web/templates/compose.html — „… Leer lassen, damit die Karte dauerhaft erreichbar bleibt.“

With card-level expiry (#14) and card-level max-views (#18) a card can now expire or be exhausted, so „dauerhaft erreichbar“ is no longer true even when no expiry date is set. Reworded to match the parallel Max. Aufrufe / Passwort hints:

„… Leer lassen für kein Ablaufdatum.“

Everything else already accurate — no other permanence claim found across compose / card / share-banner:

  • The share-banner (postcard.html) already shows conditional, accurate warnings when a card has an expiry (⏳ … gültig bis …) or a view cap (👁 … höchstens N Mal …).
  • Landing copy only promises secrecy („nur wer ihn hat, sieht die Karte“), not permanence.

German copy uses proper Umlaute throughout.

Commit: 4c08b3816b

## Done — copy no longer claims the card link is permanent ✅ Bundled with #21 in the same commit (same templates). **Audit result:** the only copy that still claimed permanence was the *Gültig bis* (expiry) hint on the compose form: > `web/templates/compose.html` — „… Leer lassen, damit die Karte **dauerhaft erreichbar bleibt**.“ With card-level expiry (#14) and card-level max-views (#18) a card can now expire or be exhausted, so „dauerhaft erreichbar“ is no longer true even when no expiry date is set. Reworded to match the parallel *Max. Aufrufe* / *Passwort* hints: > „… Leer lassen für **kein Ablaufdatum**.“ **Everything else already accurate** — no other permanence claim found across compose / card / share-banner: - The share-banner (`postcard.html`) already shows conditional, accurate warnings when a card has an expiry (`⏳ … gültig bis …`) or a view cap (`👁 … höchstens N Mal …`). - Landing copy only promises secrecy („nur wer ihn hat, sieht die Karte“), not permanence. German copy uses proper Umlaute throughout. Commit: https://mgit.msbls.de/m/postcards/commit/4c08b3816b83dde30cbea233b62c631730aa189e
mAi commented 2026-06-17 12:57:51 +00:00
Author
Collaborator
Copy Link

✅ Merged & deployed — permanence copy fixed\n\nIn merge 3d44213. Copy no longer claims the card link is permanent — wording now reflects that a link works until the card expires (#14) or hits its view cap (#18), if set. Not closing — m closes.

## ✅ Merged & deployed — permanence copy fixed\n\nIn merge `3d44213`. Copy no longer claims the card link is permanent — wording now reflects that a link works until the card expires (#14) or hits its view cap (#18), if set. Not closing — m closes.
mAi closed this issue 2026-06-23 15:48:04 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mAi m
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m/postcards#22
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?