{"slug": "show-hn-silver-music-notifier-get-notified-about-your-artists-new-releases", "title": "Show HN: Silver Music Notifier – get notified about your artists' new releases", "summary": "Silver Music Notifier, a new open-source tool, lets users track artists and receive notifications of new music releases via terminal or local web UI. The tool integrates with MusicBrainz and supports email alerts, requiring Node 22+.", "body_md": "Track a list of artists and get notified of their new music releases from\n[MusicBrainz](https://musicbrainz.org). Use it from the terminal, or launch a\nlocal web UI (built with [silver-ui](https://silver-ui.com)).\n\n```\nnpm install -g silver-music-notifier\n```\n\nRequires Node 22+.\n\n```\nsilver-music-notifier web            # starts on http://localhost:3001 and opens a browser\nsilver-music-notifier web --port 8080 --no-open\n```\n\nThe UI has three views:\n\n**Releases**— a feed of every known release-group, newest first, with a** Refresh**button and a \"New\" badge on releases discovered in the last refresh.** Artists**— search MusicBrainz and add/remove the artists you follow.** Settings**— set the MusicBrainz contact (required), choose notification methods, and configure SMTP for email.\n\n```\nsilver-music-notifier add \"Radiohead\"          # search MusicBrainz, pick a match\nsilver-music-notifier add \"Boards of Canada\" -y  # add the top match, no prompt\nsilver-music-notifier add \"X\" --mbid <mbid>    # add an exact MBID\nsilver-music-notifier list                     # list tracked artists\nsilver-music-notifier remove \"Radiohead\"       # stop tracking (by name or MBID)\nsilver-music-notifier refresh                  # fetch releases + notify on new ones\nsilver-music-notifier refresh --no-notify      # fetch without sending email\nsilver-music-notifier releases --new --limit 20\nsilver-music-notifier dismiss <release-mbid>   # hide a release's New badge\nsilver-music-notifier config get               # show settings\nsilver-music-notifier config set notify.email true\nsilver-music-notifier clear-data               # delete artists/releases, keep settings\n```\n\nMusicBrainz requires every API client to identify a contact (an email or URL) in\nits User-Agent, and throttles or blocks requests without one. The first time you\nrun most CLI commands, the CLI **prompts you for a contact** and saves it.\nNon-network setup commands such as `config set`\n\n, `clear-data`\n\n, and `dismiss`\n\ncan run before the contact is configured. You can also set it ahead of time:\n\n```\nsilver-music-notifier config set musicbrainz.contact you@example.com\n```\n\nor in the web UI's **Settings** view after the app has launched. In a\nnon-interactive context (no TTY), commands that require the contact error with\nthis guidance instead of prompting.\n\nWhen `refresh`\n\nfinds releases it has never seen before, it can notify you two ways:\n\n**In-page badges**— \"New\" badges in the web UI (always available).** Email**— one HTML email per new release, sent once SMTP is configured and the email toggle is on. Configure it in the** Settings**view or via`config set smtp.host`\n\n,`smtp.port`\n\n,`smtp.secure`\n\n,`smtp.user`\n\n,`smtp.pass`\n\n,`smtp.from`\n\n, and`smtp.to`\n\n.\n\nAdding a new artist refreshes that artist immediately, but treats the existing catalog as your starting baseline: it does not send email for those releases or mark them with \"New\" badges.\n\n`refresh`\n\nis manual — run it from the CLI, the web button, or your own scheduler\n(cron, systemd timer, etc.).\n\nTo check for new releases on a schedule, first make sure the CLI has the required MusicBrainz contact and any notification settings configured:\n\n```\nsilver-music-notifier config set musicbrainz.contact you@example.com\nsilver-music-notifier config set notify.email true   # optional, if SMTP is configured\n```\n\nThen add a cron entry. This example refreshes every day at 9:00 AM:\n\n```\n0 9 * * * /usr/bin/env silver-music-notifier refresh >> \"$HOME/.local/share/silver-music-notifier/cron.log\" 2>&1\n```\n\nIf cron cannot find the command, use the full path from\n`command -v silver-music-notifier`\n\n. To use a custom database location, set\n`SILVER_MUSIC_NOTIFIER_DATA_DIR`\n\nin the cron line:\n\n```\n0 9 * * *\nSILVER_MUSIC_NOTIFIER_DATA_DIR=\"$HOME/.local/share/silver-music-notifier\" /usr/bin/env silver-music-notifier refresh >> \"$HOME/.local/share/silver-music-notifier/cron.log\" 2>&1\n```\n\nState lives in a single SQLite file (`data.db`\n\n) in your per-user data directory:\n\n**Linux:**`$XDG_DATA_HOME/silver-music-notifier`\n\n(usually`~/.local/share/silver-music-notifier`\n\n)**macOS:**`~/Library/Application Support/silver-music-notifier`\n\n**Windows:**`%LOCALAPPDATA%\\silver-music-notifier\\Data`\n\nOverride the location with the `SILVER_MUSIC_NOTIFIER_DATA_DIR`\n\nenvironment\nvariable.\n\nNote:SMTP credentials (including the password) are stored in plaintext in that local SQLite file. This is a single-user local tool; treat the data directory accordingly.\n\nNotification methods (in-page / email) and the MusicBrainz contact are\nconfigured in the web UI's **Settings** view or via `silver-music-notifier config set …`\n\n— not through environment variables.", "url": "https://wpnews.pro/news/show-hn-silver-music-notifier-get-notified-about-your-artists-new-releases", "canonical_source": "https://github.com/czarandy/silver-music-notifier", "published_at": "2026-06-16 17:09:17+00:00", "updated_at": "2026-06-16 17:25:30.968209+00:00", "lang": "en", "topics": ["developer-tools"], "entities": ["MusicBrainz", "silver-ui", "Node"], "alternates": {"html": "https://wpnews.pro/news/show-hn-silver-music-notifier-get-notified-about-your-artists-new-releases", "markdown": "https://wpnews.pro/news/show-hn-silver-music-notifier-get-notified-about-your-artists-new-releases.md", "text": "https://wpnews.pro/news/show-hn-silver-music-notifier-get-notified-about-your-artists-new-releases.txt", "jsonld": "https://wpnews.pro/news/show-hn-silver-music-notifier-get-notified-about-your-artists-new-releases.jsonld"}}