Skip to content

docs(authentication): notifying a user through Internet Identity - #438

Open
sea-snake wants to merge 15 commits into
mainfrom
docs/guides-authentication-notifications
Open

sea-snake wants to merge 15 commits into
mainfrom
docs/guides-authentication-notifications

Conversation

@sea-snake

Copy link
Copy Markdown
Contributor

Summary

  • New page, guides/authentication/notifications.mdx: asking a user for permission to notify them through Internet Identity, naming the sending canister at /.well-known/ii-notification-senders, and sending from a Motoko or Rust canister.
  • Covers the two behaviours that surprise people: a notification is addressed to a principal rather than a browser, so Internet Identity wakes every browser that identity has registered; and dropping someone from an app's own recipient list unsubscribes nothing, because the subscriptions live in Internet Identity against the anchor.
  • Cross-links app-metadata.md both ways. The notification's title is the app's name followed by the title the canister sent, falling back to the origin's hostname, and the logo is the icon, so that document brands notifications and not just the sign-in screen.

Structural decisions

  • sidebar.order: 8, appended rather than slotted mid-list, so no existing page is renumbered. The section reads as "set up sign-in, then get more from it", and reaching a user after they have left belongs at the end of that.
  • .mdx rather than .md for the Motoko and Rust tabs, in that order.
  • Per the no-duplication rule, the send section carries the one send call and links to the crate and the Mops package for endpoints!, init, and the full Notification type, rather than reproducing the library's README.

Verified

  • npm run build passes.
  • No em or en dashes, no banned vocabulary.
  • Internal links are relative with a .md extension; both targets checked with ls.
  • API surface and behaviour checked against dfinity/identity-notifications at main and the Internet Identity source, not from memory: the title composition and hostname fallback are from the service worker's wake-up path, and the sender list limits and cache windows from the senders cache.

@sea-snake
sea-snake requested review from a team as code owners October 27, 2026 12:04
@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

🤖 Here's your preview: https://dpfyp-oaaaa-aaaam-ahcqa-cai.icp0.io

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant