A bilingual Canadian site that combines two models:

• Switch recipes, after DI.DAY and Doeidag: move one service away from Big Tech on the first Sunday of every month.
• Cancel links, after Resist and Unsubscribe: direct instructions for cancelling U.S. subscriptions, each paired with alternatives.

Status: scaffold with sample data. Every entry is marked verified: false and shows a "sample entry" notice until reviewed.

See LAUNCH.md for the launch checklist.

• English and French are equal. The build fails if any text is missing in either language.
• Listed alternatives are Canadian owned, open source, or European owned, ranked in that order. Anything else is a labelled exception.
• Services owned in Russia, Belarus or China are never listed.
• Every claim about headquarters, ownership or open source needs a supporting source. The build fails without one.
• Headquarters and ownership are recorded separately. Ownership decides. null means "not yet researched".
• No trackers, cookies, third-party scripts or web fonts.
• Static HTML only, so the site can move from GitHub Pages to Codeberg Pages or any other host without code changes.

Requires Node.js 22 or later.

npm install
npm start          # local server with live reload
npm test           # unit tests, content check, build, HTML and internal links
npm run check:links     # also checks external links (needs network)
npm run check:wikidata  # compares ownership with Wikidata (needs network)
npm run check:a11y      # axe-core in Firefox (run `npx playwright install firefox` once first)
npm run check:a11y:chromium  # Chromium only
npm run check:a11y:all       # Firefox, then Chromium
npm run french          # lists French text that needs review
npm run check:reviews   # lists entries by review date

1. Push to a repository with main as the default branch.
2. In Settings, Pages, set Source to "GitHub Actions".
3. The workflow sets the path prefix automatically, so project pages (/repo-name/) and custom domains both work.
4. The site rebuilds every Monday so the next date stays correct.

Every build and pull request:

• Content rules: both languages complete, a source for every claim, inclusion and exclusion rules.
• HTML validation and links between pages, including # anchors.
• Accessibility. axe-core runs on every page in Firefox, in light and dark colour schemes, at desktop and phone widths. Any WCAG 2.2 A or AA failure stops the deploy. Best-practice findings and items needing human review appear in the run summary. Automated testing finds only part of the problems, so manual and screen reader testing are still needed.
• French review. A warning, not a failure, lists French text not yet reviewed against the current English.

Every Monday:

• The site rebuilds so the next date is correct.
• Link check. Every URL in the data files is requested. Broken links (404, 410, no response, repeated server errors) open or update an issue titled "Broken links". Responses such as 403 and 429 usually mean a site refused an automated request, so they are listed for a person to check but do not open an issue on their own.
• Accessibility in Chromium. The same axe-core check runs in Chromium, to catch problems that appear in only one browser engine. WCAG failures open or update an issue titled "Accessibility problems in Chromium".
• Ownership check. For each alternative with a wikidata ID, the check follows "parent organization" and "owned by" up to the top owner and compares that owner's country, and the headquarters country, with the data. Any disagreement opens or updates an issue titled "Ownership changes to review", and ownership moving to an excluded country is called out.

Neither check edits the data. Wikidata can be wrong or out of date, so a maintainer confirms changes against a primary source.

On the first of each month:

• Review dates. Entries whose last_reviewed date has expired open or update an issue titled "Content due for review". The report also lists entries due in the next 30 days, so they can be reviewed before the first Sunday. Reviews last 12 months for alternatives and recipes and 6 months for cancel entries, set in data/review.yaml. Entries never reviewed are listed but do not open an issue.

Every alternative, cancel entry and recipe has a "Report a problem with ..." link, whatever its review state. It opens the bilingual issue form in .github/ISSUE_TEMPLATE/out-of-date.yml with the entry name and page filled in.

Mastodon is the preferred route, because it does not need a GitHub account. When mastodon is set in data/site.yaml, each entry invites people to mention the project account first, with GitHub as the second option.

Every day, .github/workflows/mastodon.yml reads mentions of the project account and opens one issue per public mention, with a link to the original post and any entries it names.

• Public posts only. Unlisted, followers-only and direct messages are skipped and never copied anywhere, because their authors did not publish them openly.
• No pinging on GitHub. @name and #123 in quoted posts are altered so they do not notify GitHub users or link to issues.
• Read only. The account's token needs only the read:notifications scope. The script never posts, replies or dismisses notifications, so maintainers still see every mention in the Mastodon app.
• No duplicates. Before opening an issue, it searches existing issues for the post's link.

Setup:

1. Create the project account on mstdn.ca. See LAUNCH.md about whether to mark it as automated.
2. In the account's Development settings, create an application with only the read:notifications scope and copy its access token.
3. Add the token as a repository secret named MASTODON_TOKEN.
4. Set mastodon: "@[email protected]" in data/site.yaml.

Try it without opening issues: MASTODON_TOKEN=... npm run mastodon, then read reports/mastodon.md.

.github/workflows/reminders.yml runs daily. On the first Sunday it posts one reminder in English and one in French, each tagged with its language so screen readers and filters handle it correctly. Every day it deletes reminders older than 30 days. It only deletes posts made by the "DI.DAY Canada reminders" application and never deletes pinned posts, so anything a person posts from the account is left alone.

It needs url set in data/site.yaml and a repository secret named MSTDN, holding a token with only the read:statuses and write:statuses scopes, which the workflow passes to scripts/reminders.js as MASTODON_POSTING_TOKEN. The text is in data/strings.yaml under reminder_post, with several variants so the wording isn't identical every month. Hashtags use CamelCase so screen readers read them as words.

Gander has no public posting interface, so the run summary includes the text for a person to post there by hand.

Try it: npm run reminders (dry run, writes reports/reminder.md).

Gander is listed as an alternative. It cannot yet be a reporting channel, because it does not connect to Mastodon and does not offer the same kind of access. Revisit once Gander connects to other networks.

The project's handle, diday.gander.social, resolves on the AT Protocol (the open standard Bluesky also uses): https://public.api.bsky.app/xrpc/com.atproto.identity.resolveHandle?handle=diday.gander.social returns a did:plc: identity. It is not yet visible through Bluesky's own app or API (app.bsky.actor.getProfile returns "Profile not found" as of 2026-09-29), matching Gander's FAQ: "Today, Gander gives users the option to view content from Bluesky," with full interoperability (posting that reaches Bluesky, and a public developer API) listed as a future goal, not a current feature. There is no public API sign-up; the only integration route mentioned on gandersocial.ca is a partnership inquiry ("Talk to us" on the Why Gander page).

1. Check each source still supports the claims listed under supports.
2. Check the cancellation link or recipe steps still work.
3. Set last_reviewed to today's date (YYYY-MM-DD) and verified: true.

Pages show the review date. Once a review expires, the page also says the information may be out of date, until someone reviews it again.

data/translations.lock.yaml records a fingerprint of each English and French pair when a fluent reviewer approves it. If either side changes later, the pair is flagged again.

npm run french                                   # what needs review, written to reports/french.md
npm run french -- approve alternatives.kobo.notes
npm run french -- approve --prefix recipes.ebooks-without-amazon
npm run french -- approve --all                  # only after reviewing everything listed

On French pages, items awaiting review show "Traduction pas encore révisée", and the footer notes when interface text is pending. English pages show nothing.

The output in _site/ is plain HTML and CSS. To move to Codeberg Pages, run the same build in Forgejo Actions or Woodpecker CI, or push _site/ to a pages branch.

• Cancellation URLs are the U.S. pages listed by Resist and Unsubscribe. Canadian (.ca, en-ca, fr-ca) pages still need to be found.
• Wikipedia sources are placeholders. Primary sources are preferred.
• French text needs review by a fluent francophone. All French texts are currently marked as not reviewed (run npm run french for the current count).
• URL slugs are English in both languages.
• Siteimprove Alfa is deferred. axe-core is in CI.
• The Firefox accessibility run has not yet been tested; it was built in an environment where only Chromium was available. Playwright's Firefox is a patched build, not the release version.
• The external link and Wikidata checks have unit tests but have not yet run against the live sites.
• Hushmail has no Wikidata item.
• No Mastodon account is set, so the Mastodon option is hidden and the daily inbox does nothing.
• The Mastodon inbox and reminders have been tested against a simulated server, not mstdn.ca.
• Gander reminders are posted by hand.
• Issue search can lag behind new issues, so a duplicate is possible if the inbox runs twice within minutes.
• The issue form applies the label out-of-date. Create that label in the repository, or GitHub will not apply it.
• report_url in data/site.yaml is a placeholder until the repository exists.
• The date is computed in UTC at build time.

Code: GNU AGPL v3 or later (see LICENSE). Content in data/: CC BY-SA 4.0.

AGPL, rather than MIT, so that anyone who runs a modified version of this site as a public service - not just anyone who redistributes the code - must also offer its source. A fork stays open the same way the original is.