Wonders of Work Review hub

Open changes waiting for a look, and what shipped recently. Anyone can open a preview below and leave feedback on GitLab.

Open for review

🌱 Nothing is waiting for review right now. Want to help shape what comes next? Read CONTRIBUTING →

Recently shipped to production (main) wondersofwork.nl 🎉

  • MR !115 by Jurjen de Vries ·
    Fix
    don't remove published stories when their draft is deleted
    What this changes, and why

    Stories disappeared from overviews and profile pages. Victor Evink's profile shows none of his 5 stories, and /verhalen shows 19 instead of 25.

    Publishing a story deletes its draft (kind 30024) with an a tag, and the draft has the same d-tag as the published story (kind 30023). removeDeletedCard in deletion-cache.js removed cards by d-tag alone. So each draft deletion that arrived after the cards rendered removed the published story too. It also removed cards that an author had republished after an older deletion.

    This bug was always there, but stayed hidden while recordDeletion misread a tags. Fixing that read in !113 made it show up.

    Cards are now matched on the event they show:

    • for an a tag: the full coordinate (kind, pubkey, d-tag), and only versions the deletion is at least as new as;
    • for an e tag: exactly that event id.
    What this affects

    Only public/scripts/deletion-cache.js: removing cards for deletions that arrive after the cards are shown, on overviews, profile pages and CardGrid blocks. Whether an item counts as deleted (isEventDeleted) does not change.

    How to try it

    Tested on the live site, with production code against this branch's script swapped in:

    • Victor Evink's profile: 0 → 5 stories.
    • /verhalen: 19 → 25 cards.
    • /agenda (12) and the home page (6) are unchanged.

    A unit check with a simulated grid covers four cases:

    • deleting a draft keeps the published story;
    • an a-tag deletion of the published story removes it;
    • a deletion older than a republished version keeps the card;
    • an e tag removes exactly that event.

    On the preview, open https://wondersofwork.nl/nl/profile-preview/?key=npub1n47ad7tcu5vcztp48e43mn5vvqgct05r4mts0txe9cpx5gw9vytsz0jc7m on the preview domain. The stories should stay after ~10 s.

    Before you ask for review
    • [x] Branch named feat/…, fix/…, chore/…, docs/… or hotfix/…
    • [x] Commit messages follow Conventional Commits
    • [x] pnpm format has been run and the checks are green
    • [ ] Tried it on the preview link
    • [x] Rebased on the latest main
  • MR !114 by M Maaz ·
    Fix
    return to the page sign-in started from and build without a spotlight shape

    What this changes, and why<br>Three fixes on one branch. (1) The login page kept its "Getting your info..." overlay up forever when the account already had a profile: checkUserMetadataAndRedirect only navigated for the empty-profile case, so a finished sign-in never left the page until a manual reload. (2) Sign-in started from a reaction, a comment or the navbar never returned to where it started, so the pending action was lost: the return target those flows store in localStorage.returnUrl was never read. It is now used, same-origin only. (3) The static build died on a spotlight block saved without its shape image; it now renders unclipped, and the clip definition is only emitted when a shape exists. The dead relay.nsec.app fallback relay is dropped too (re-probed 2026-10-26: it times out before the WebSocket upgrade).<br><br>What this affects<br>Login: check-user-metadata.js gains an opt-in redirectOnComplete and a return target that resolves the query param first, then the stored value, refuses cross-origin and /login targets (by path segment, case-insensitive, decoded), and removes the stored key only when it is the one used; the target is carried through edit-profile for new accounts. login-page.js passes the opt-in at both entry points, and the extension button now matches the email path for accounts without a name. login.js sends the navbar login with ?returnUrl=, while the navbar quick-login still stays on the page. OpenBunker: DEFAULT_OPENBUNKER_RELAYS keeps only the two relays that answer. Rendering: blocks/Spotlight.astro skips both the clip-path and the clip definition when a block has no shape; two shaped blocks on one page still share one id, which is pre-existing and unchanged here.<br><br>How to try it<br>1. /nl/login, email OTP on an account with a profile: the spinner leaves on its own and you land where you came from (or the locale home page).<br>2. Logged out, open a story, click a reaction, choose "Continue with Email", finish the OTP: you return to that story and the reaction is published.<br>3. Logged out, type a comment on a story, submit, sign in: you return to that story with the draft restored.<br>4. Logged out on any page, use the navbar profile button: you land on the login form and come back to that page afterwards.<br>5. A brand-new address: it goes to edit-profile?source=openbunker-new&returnUrl=..., and after saving you return to the origin page.<br>6. /nl/ and /en/: the winter spotlight renders (unclipped until a shape is chosen in the CMS).<br><br>No tests were added or changed; the existing login test still passes.

  • MR !113 by Jurjen de Vries ·
    Fix
    make deleting stories and events stick
    What this changes, and why

    Deleted calendar events kept coming back. "Rise To Get There" (Irene) was deleted twice and is still shown. Four bugs worked together:

    1. Only one version was deleted. Deletions of calendar events had only an e tag (the version on screen), no a tag. relay.ditto.pub keeps older versions, and serves those after the newest one is deleted. deletionTags() now adds the a tag for every addressable kind (30000–39999). 2. The menu deleted the wrong version. The preview menu was set up once, with the first version rendered: the browser's cached copy, if there was one. Delete therefore kept targeting an old, already-deleted edit. Edit, copy ID and delete now act on the version on screen. 3. The deleted item stayed in the author's browser. The local cache copy never expired. It is now removed after a delete. A cached copy that no relay serves any more is also dropped, unless it is less than 10 minutes old. 4. The site ignored a-tag deletions. recordDeletion cut the d-tag at its first colon (event:…), so coordinates never matched.

    On top of this, six events whose authors deleted the newest version are treated as deleted (INFERRED_COORDINATE_DELETIONS). Each one was checked against the author's signed deletion and the Strapi index.

    What this affects

    The delete, edit and copy-ID menu on story and event pages. The local cache. Which items the overviews and detail pages hide as deleted.

    How to try it
    • Agenda: "Rise To Get There" is gone (15 → 14 events locally). Its page shows "deleted". /verhalen is unchanged (25 stories).
    • Throwaway-key test (event with 3 versions, one cached), production vs this branch:
    • Delete in production targets the cached, already-deleted version and nothing changes.
    • This branch deletes the version on screen with an a tag, and all relays serve nothing.
    • On the preview: create an event, edit it, delete it. It stays gone after reload, including on the event page.

    After the merge, the six authors can delete their event once more. Their entries in INFERRED_COORDINATE_DELETIONS can then be removed.

    Before you ask for review
    • [x] Branch named feat/…, fix/…, chore/…, docs/… or hotfix/…
    • [x] Commit messages follow Conventional Commits
    • [x] pnpm format has been run and the checks are green
    • [ ] Tried it on the preview link
    • [x] Rebased on the latest main
  • MR !112 by Jurjen de Vries ·
    Fix
    reconnect to relays whose connection failed or dropped
    What this changes, and why

    If a relay's first connection attempt failed, or its connection dropped later, the site never tried that relay again during the visit, as long as another relay was up. relay.nostr.net fails its first handshake fairly often, and it is our most complete relay.

    The reconnect code in connect-relays.js never ran. onclose removed the relay from wsConnections and then checked wsConnections.has(url), which is always false. Now:

    • A failed or dropped connection is retried with the existing backoff (3 s, 6 s), up to 3 attempts. Relays that were removed from the list on purpose are not retried.
    • A stale onclose from an old socket no longer removes a newer, working connection.
    • The 60 s maintenance pass also retries relays that are down, once their attempt counter resets (every 5 min). Before, it only did this when no relay at all was working.

    When a relay connects late, it still receives the requests that are already running, through the late-relay watcher in nostr-queue.js.

    What this affects

    This touches every page that uses Nostr, but only the relay connection handling. Nothing else changes.

    How to try it

    On the preview, open /nl/verhalen with DevTools open.

    • Console: when a relay's first connection fails you should see Reconnecting to wss://… in 3 seconds..., followed by a new attempt.
    • To force it, in Network → WS, block relay.nostr.net for the first load (request blocking), then unblock it. The relay should come back within a few seconds.

    In a test with a simulated failing first handshake, production never reconnected. This branch reconnected on attempt 3 and relay.nostr.net still delivered 15 events for requests already in progress.

    Before you ask for review
    • [x] Branch named feat/…, fix/…, chore/…, docs/… or hotfix/…
    • [x] Commit messages follow Conventional Commits
    • [x] pnpm format has been run and the checks are green
    • [ ] Tried it on the preview link
    • [x] Rebased on the latest main
  • MR !111 by Jurjen de Vries ·
    Fix
    read Nostr content from relays that still hold it
    What this changes, and why

    Most stories, calendar events and profiles stopped showing. The site read from four relays, and on 2026-09-30 none of them still had the content: relay.nsec.app is unreachable, nos.lol and relay.primal.net keep our events for only about a day, and relay.damus.io accepts connections but mostly never answers. The content still exists on other relays.

    • New relay list: relay.nostr.net, relay.ditto.pub, nostr.oxtr.dev, nostr.mom, nostr.data.haus. Each was measured to hold our content and to answer.
    • purplepag.es is added for profiles only (kinds 0/3/10002). Other queries and posts skip it (window.relaysFor).
    • Subscriptions stay open 6 s after the first relay answers instead of 2.5 s, so slower relays are no longer cut off.
    • The relay hints in "copy ID" (naddr) now point to relays that actually hold the events.
    • Event detail showed "not found" at random: it stopped waiting while a relay was still connecting, and a duplicate load could leave the page hidden. RSVP links ("Meet <name> at") now pass the author, so events made in other Nostr calendar apps (no WoW tag) open too.
    What this affects

    These changes touch every Nostr read and publish (stories, events, profiles, reactions, deletions), so posting and deleting also go to the new relays. Not changed: the OpenBunker login relays. The OpenBunker API still returns relay.nsec.app, but that is a separate change. The "empty" or "loaded" state can now appear up to 6 s after the first relay answers, but only when a relay is slow.

    How to try it

    On the preview link:

    • /nl/verhalen and /nl/agenda should show all stories and events (in local tests: 22 stories and 11 events, where production showed 0–1).
    • /nl/wonderful-people should show all profiles with names and avatars (39 of 39, where production showed 1).
    • Open a profile with RSVPs and click the events under "Meet <name> at". Each should open every time.
    • In DevTools > Network > WS: purplepag.es should only get kinds:[0] REQs.
    • While logged in: post and delete a test story. Publishing and deleting have not been tested.
    Before you ask for review
    • [x] Branch named feat/…, fix/…, chore/…, docs/… or hotfix/…
    • [x] Commit messages follow Conventional Commits
    • [x] pnpm format has been run and the checks are green
    • [ ] Tried it on the preview link
    • [x] Rebased on the latest main
  • Fix
    default location room selector visibility
    What this changes, and why

    Fixed create an event default location room selector visibility

    What this affects

    src/pages/[...locale]/create-event.astro

    How to try it

    go to create event page and select the default location

  • Feature
    add sml-spaces variant to cardGrid to generate random S M L spaces
    What this changes, and why

    Add sml-spaces variants to CardGrid to generate 3 random spaces by serialy small, medium, large spaces

    What this affects

    src/components/blocks/CardGrid.astro

    How to try it

    go to homepage after Discover section you will find the section. you can regenerate or create from strapi using CardGrid page component and selecting sml-spaces from variants selector

  • MR !108 by Jurjen de Vries ·
    Chore
    rename default-* UI fallbacks to fallback-*
    What this changes, and why

    Renames the UI fallback assets from default-* to fallback-* so they are clearly not editorial media, and so the upcoming hardcoded/i18n lint can exclude fallback-* by convention.

    • public/images/default-avatar.svg -> fallback-avatar.svg
    • public/images/default-placeholder.svg -> fallback-placeholder.svg
    • public/images/loader.svg -> fallback-loader.svg
    • all references updated across .astro and public/scripts (24+ refs), zero old refs left.

    og-default.jpg is left as-is (Open Graph share image, different purpose).

    What this affects

    Image file names under public/images and every reference to them. No behaviour change — same images, new names. No editorial content.

    How to try it

    Open a preview: avatars, placeholders and the loader still render (they now load from /images/fallback-*.svg).

  • Fix
    hardcoded text replace with cms
    What this changes, and why

    Completes the hardcoded-copy → Strapi migration so every user-facing string is content-managed (editable and translatable in Strapi instead of baked into code). This covers the bulk of the hardcoded-copy backlog, including copy hidden in client scripts that the grep-based lint:hardcoded could not see.

    English is preserved verbatim in the EN locale; the frontend now reads whatever Strapi serves per locale (nl-NL is populated), with an English fallback kept as the safety net.

    What this affects
    • public/scripts/* — all client libs: raw literals → window.__texts / window.profileUi / window.eventUi lookups; two dead files removed (user-metadata.js, profile.js), superseded by check-user-metadata.js
    • src/components/* — form fields, editor, navbar, pagination, reactions, room/tag selectors, loading, and blocks (audio/card/categories/newsletter/offer/quote/richtext), plus ExportKeySection
    • src/pages/[...locale]/* — agenda details, create-event, edit-profile, login, and event/story/profile previews
    • src/layouts/Layout.astro — injects window.__texts for client scripts
    • src/utils/getGlobals.ts + get{Login,Profile,Event}UiConfig.ts — expose the per-feature config shapes

    No Strapi schema changes in this MR — schema and content already live in production.

    How to try it

    On the preview link, switch locale (nl / en) and confirm the strings follow:

    • Newsletter status messages, event/story preview copy, profile export-key labels
    • Form field labels/placeholders, editor toolbar options, loading and error states
    Before you ask for review
    • [x] Branch named fix/…
    • [x] Commit messages follow Conventional Commits
    • [x] pnpm format run, checks green
    • [x] Tried it on the preview link
    • [x] Rebased on the latest main
  • Fix
    replace newsletter custom icon with image media
    What this changes, and why

    update newsletter icon logic

    What this affects

    src/components/blocks/Newsletter.astro

    How to try it

    go to coworking page

See all merged changes on GitLab →