Relays: what Sidecar knows about them, what it does when it cannot tell, and what it says when something fails.
Added
- Reply from the notifications list. Answer a note or a comment without leaving Sidecar. The composer opens with what you are answering shown above the editor, and it stays there through Preview and the review countdown. Replies to notes follow NIP-10 and replies to page comments follow NIP-22, which are not interchangeable.
- A web-of-trust filter for notifications. Reply spam from fresh keys cannot be muted, because a mute list is a denylist and a denylist cannot outrun key rotation. The bell now sorts by who your circle already vouches for, with everyone else collapsed into a counted group rather than hidden.
- Relay sign-in (NIP-42). Some relays gate reading behind a challenge, and Sidecar had no way to answer, so those relays served the panel nothing. Answering is limited to your own relays.
- Relay icons, read from each relay's NIP-11 document.
- Recent Activity can be verified. Each signature records its event id, and a row with one opens the signed event in your preferred client.
- A Reset connections button when the browser has run out of sockets.
Changed
- Zap notifications say how much, far more often. The amount was read only from a tag many wallets omit, and now falls back to the invoice. On a real inbox that took receipts showing an amount from 93 of 150 to all 150.
- Repost and reply marks are drawn, not emoji, so they follow the theme. A reaction keeps the sender's own emoji, which is content rather than decoration.
- The notifications header names an account only when there is more than one.
- The composer grows with the panel, and closing it accidentally no longer loses what you were writing.
Fixed
- Your relay list could be replaced with Sidecar's defaults. A timed-out lookup was indistinguishable from "this account has published nothing", so the app's shared defaults appeared labelled as your own, and publishing from that screen would have overwritten a real list.
- Posts could fail with "No relays configured" when your relays were configured perfectly well.
- Relay connections leaked until the browser ran dry. Every relay would report a timeout while those same relays answered normally from outside the browser, and only a restart helped. Reported upstream and fixed in nostr-tools 2.25.2.
- A signing request could hang with nothing on screen. No prompt, no error, no Recent Activity entry, and reactions or reposts that appeared to do nothing at all.
- Notification names showed as npubs.
- Sidecar blamed a relay when the browser had run out of sockets. A failed probe proves only that a connection could not be opened.
Install
Chrome: sidecar-1.12.0-chrome.zip. Firefox: sidecar-1.12.0-firefox.zip. Both are flat-root zips; the store versions follow.
sha256 134b6e0fc4e0118b163afbfd89663aea4938512ec18f8cce1f1d370fe7c85902 sidecar-1.12.0-chrome.zip
sha256 15831c8559006e51b05b4720d1f2479ce30ba4a773f0f5dd7560e39d3f141f7d sidecar-1.12.0-firefox.zip