Repository navigation
RSS Workshop v1.2.0
Notifications to ntfy or a JSON webhook when a feed keeps failing or the database fails, a library you can search, filter and sort, which points out feeds that have gone quiet, a Duplicate action, and a User-Agent you can set for the server or for one feed. Story dates are read in the zone they name and with English month names, static mode reads pages in legacy encodings, FlareSolverr feeds that fall due together no longer fail, nor do refreshes cut short by stopping the app, and Pause and Resume no longer reset a feed. Sources see a new User-Agent, and some feeds change once.
Upgrading from v1.1.1
- The database is unchanged. This version keeps schema 5 and opens a v1.1.0 or v1.1.1 database as it is: SQLite saves no pre-upgrade copy and PostgreSQL logs no migration. To roll back, set
RSS_IMAGE=ghcr.io/ldogg123/rss-workshop:v1.1.1-browser, orghcr.io/ldogg123/rss-workshop:v1.1.1-staticwithcompose.static.yaml, or the image digest you saved; nothing needs restoring, but see the last item below for what v1.1.x does not keep. From v1.1.0, also follow Upgrading from v1.1.0, and from v1.0.0 Upgrading from v1.0.0 as well. - Update your checkout (
git pull) before recreating the container. Only the currentcompose.yamlpasses the newFETCH_USER_AGENTand the notification settingsNOTIFY_URL,NOTIFY_FORMAT,NOTIFY_TOKENandNOTIFY_AFTER_FAILURESinto the container; with an older one, Docker ignores them even when.envsets them. The Compose overrides andscripts/backup.pyare unchanged. - Notifications stay off until you set
NOTIFY_URL. The newNOTIFY_URL,NOTIFY_FORMAT,NOTIFY_TOKENandNOTIFY_AFTER_FAILURESare optional and default to off, the JSON format and 3 failures in a row, so upgrading sends nothing and adds no table. A feed that has already failedNOTIFY_AFTER_FAILUREStimes or more in a row when you turn them on is not reported as failing, since that alert goes out only as the count reaches the number, but its recovery is, so look for Needs attention in the library once they are on. Even whileNOTIFY_URLis blank, startup refuses aNOTIFY_FORMATother thanjsonorntfy, aNOTIFY_AFTER_FAILURESoutside 1–100, or aNOTIFY_TOKENwithout a URL. To turn them on with Compose, update your checkout as above, set them in.envand recreate the container withdocker compose up -d; a native executable needs them exported. TreatNOTIFY_URLandNOTIFY_TOKENas passwords, because a topic on a public ntfy server works as one and webhook URLs often embed a token. The app keeps both out of its logs, errors, metrics and dashboard, and they never reach the database or its backups, butdocker compose configprints them. See notifications. - Sources see a new User-Agent. Static requests, for list pages, article pages and the visual selector, now send
RSS-Workshop (+https://github.com/Ldogg123/rss-workshop)instead ofGoRSS/0.1 (+self-hosted feed builder). If a source starts refusing requests or serving different pages, setFETCH_USER_AGENT=GoRSS/0.1 (+self-hosted feed builder)in.envand recreate the container, or, for a native executable, which does not read.env, runexport FETCH_USER_AGENT='GoRSS/0.1 (+self-hosted feed builder)'and start it again. A single feed can instead set its own User-Agent. Pages that Chromium renders or FlareSolverr loads are unaffected, but the article pages of those feeds are fetched as static HTML unless the feed renders them, so they send the new name. A source that varies its pages by User-Agent may answer the first conditional request with a full page instead of 304; feeds change only if their stories did. See identifying requests. - Some feeds change once. A story still on its source's list page changes if its description already showed the story's image, which is no longer added above it a second time, or if its source is read in static mode, declares an encoding other than UTF-8, such as windows-1252 or Shift_JIS, and the story has non-ASCII text, which was saved as
�and is now correct. Those feeds change their bytes andLast-Modifiedonce, so readers download them once; older stored stories keep what they have. On those non-UTF-8 sites:- Stories whose identity has non-ASCII text get a new one once, and so appear in readers a second time: the title, for a recipe without a Link selector, or a link with unencoded non-ASCII characters, which is now encoded differently.
- A feed with Full article content keeps the article bodies it already fetched,
�included, because a body is fetched once and then kept. The same holds on such sites for feeds in Chromium or FlareSolverr mode, or Auto when it renders, that do not render their article pages, which is the default: those pages were fetched as plain HTML and read as UTF-8 too, though their list pages and story identities are unaffected. To fetch them again, save the feed once with its article selector cleared, then again with it restored; later refreshes fetch 10 per refresh for stories still on the list page, and stories no longer listed show their list-page description. See full article content. - Keyword filters with non-ASCII keywords start matching the text, so a feed can include a story it used to leave out, or the reverse. Saved stories stay unless you save the feed with the option to remove nonmatching stories.
- Stories first saved after upgrading may be dated differently. A date that names its zone, such as
Thu, 05 Nov 2026 10:00:00 EST, now uses that zone instead of UTC, and a date with an English month name, such asNov 6, 2026, gives the site's date instead of the time the story was first seen. A zone name that neither the recipe's time zone nor RFC 5322 defines, such asCETwith a blank time zone, or an hour written as a name that the recipe's time zone does not use, such as+03or+00, now leaves the date unrecognized, with adate not recognizedwarning and the first-seen time; v1.1.1 read all of these as UTC, which was right only for+00. Set Date settings → Time zone to the site's zone, such asEurope/Paris, to have it read, or, for an hour such as+00, a Go date layout that reads it as an offset, such asMon, 02 Jan 2006 15:04:05 -07. Stories already saved keep their dates and identities, so this changes no published feed. See time zones. - Pause and Resume keep a feed's state. They now change only whether the feed refreshes: a failing feed keeps its error, failure count and the source's conditional-request validators, so after Resume it still shows Needs attention until a refresh succeeds, and a renewed failure continues its backoff instead of restarting at 2 minutes. For the same reason, pausing a failing feed no longer silences an alert on it: the feed stays counted in
rss_workshop_feeds_failingand keeps itsrss_workshop_feed_failureswhile paused. To leave paused feeds out of a per-feed alert, addand on (id) rss_workshop_feed_enabled == 1; for the library total, alert oncount(rss_workshop_feed_failures > 0 and on (id) rss_workshop_feed_enabled == 1)instead. Saving the feed in the editor still clears its error, failure count and validators, as any edit does. See pausing and resuming. - Refresh releases a feed waiting after a failed database write. Once the database accepts writes again, Refresh, an editor save or Resume tries such a feed at once instead of leaving it to wait out its hold of up to about 17 hours. See waiting to retry after a failed save.
- FlareSolverr messages change. Feed errors, Diagnostics and log lines for FlareSolverr failures use new messages from the next failed refresh, so update any alert that matches the old
FlareSolverr request failed,FlareSolverr service returned HTTP n; check its service logs,FlareSolverr returned an invalid JSON response,could not read the FlareSolverr responseorFlareSolverr is unavailable, which now readsFlareSolverr is not configured on this server. On a FlareSolverr feed,context deadline exceededis replaced by messages that say what timed out: the wait for a free slot, the connection or FlareSolverr's reply. FlareSolverr troubleshooting lists the new messages. WithFLARESOLVERR_SLOTSabove 1, a feed that renders its article pages through FlareSolverr now fetches them one at a time, so a long backlog may take more refreshes to fill in. - Expect some Quiet badges at first. Feeds of sites that publish less often than every two weeks are marked Quiet once their output has been unchanged that long. Lengthen their refresh interval to raise the threshold.
- Going back to v1.1.x. v1.1.0 and v1.1.1 refuse a recipe file in which any feed has its own User-Agent (
json: unknown field "user_agent") and import none of its feeds, so clear the field before exporting recipes for an older server. After a rollback they ignore a stored one and send their own User-Agent for that feed, and saving the feed in their editor, or pausing or resuming it from its card, removes it. Feeds left alone keep it for the next upgrade. Rolling back also undoes this release's output fixes for stories still on their source's list page, from the first refresh that reads the page. A description that shows the story's image gets it a second time, and on non-UTF-8 sites read in static mode the text of a story whose identity this release kept shows�again. Those feeds change their bytes andLast-Modifiedonce more, and again after the next upgrade. Stories first saved after the rollback are dated by v1.1.x's rules.
New
- Search, filter and sort the feed library. A toolbar above the cards finds feeds by name or website, shows only the feeds with one status (Active, Quiet, Needs attention, Waiting to retry, Pending or Paused), and sorts them by name, next refresh, last success, last change or failures in a row. It works on the library the page already loads, so it adds no requests. The 10-second reload keeps the search, the selections and the keyboard focus, and the browser remembers the status and sort for the next visit. Cards also show when the feed's output last changed and how many refreshes in a row have failed. See the library dashboard.
- Point out feeds that have gone quiet. A refresh that finds nothing new succeeds, so a feed could stop delivering stories without ever showing a problem. A feed that keeps refreshing successfully but whose published output has not changed for 14 days, or 10 refresh intervals if that is longer, now shows a Quiet badge saying how long it has been unchanged. Any change to a story counts, so this is not the same as "no new stories", and a longer refresh interval raises the threshold for a site that publishes rarely.
GET /api/feedsreports each feed'slast_changedtime andquietflag, and saves accept and ignore both. Metrics addrss_workshop_feeds_quietand the per-feedrss_workshop_feed_last_changed_timestamp_seconds, within the existing 1,000-feed bound. See quiet feeds. - Duplicate a feed from its card. The editor opens a copy with every setting, its own story filters and the same library filters, linked rather than copied, named
Copy ofand the original name shortened to fit. Nothing is saved until you save it, and the copy starts paused, with its own RSS and Atom links and no saved stories. Before, the only way was to export and import a recipe, which also turned library filters into private copies. - Set a User-Agent for one feed under Request settings in its editor. It replaces
FETCH_USER_AGENTand the built-in name for that feed's static requests: its list page in Static HTTP mode and in Auto before any render, article pages fetched as plain HTML, previews, and the visual selector's Static HTML page. Surrounding spaces are trimmed, and a value longer than 256 characters or with anything but printable ASCII is refused when saving, previewing, loading the visual selector's page or importing. Blank uses the server's default, and recipes without one are stored and exported byte for byte as before. Changing it drops the source's conditional-request validators like any recipe edit, and changes no published feed. See browser rendering and recipe export and import. - Recognize English dates with a month name in element text and explicitly selected values, without a Go date layout:
5 November 2026,Nov 6, 2026,May. 5, 2026,Thursday, 5th November 2026 at 3:04 pmor5 Nov 2026 10:00 EST. The whole value must be the date, the year must have four digits, and a weekday must match the date. A date without a time is local midnight in the recipe's time zone. Automatically detecteddatetimeattributes still use only the standard formats, so they keep precedence over the element's text as before. See month names. - Get a message when something breaks, without Prometheus. Set
NOTIFY_URLto an ntfy topic withNOTIFY_FORMAT=ntfy, or to any webhook that accepts a JSONPOSTwith the defaultNOTIFY_FORMAT=json; an optionalNOTIFY_TOKENis sent as a bearer token. A feed is reported when its refreshes have failedNOTIFY_AFTER_FAILUREStimes in a row, and again when it recovers. Both follow the failure count stored with each feed, so a restart neither repeats an alert nor misses a recovery; a feed repaired in the editor, whose save resets that count, still reports its recovery unless the app has restarted since the alert. The database is reported when it refuses a refresh's results or the library cannot be read, at most once an hour while that lasts, and once more when the library can be read again. Events are collected for 60 seconds into one message that lists at most 20 of them, database events first, and counts the rest, so an outage that fails every feed at once sends one notification. The dashboard's status line says which format is on and, while one is, offers Send test notification. Messages carry feed titles, failure counts, the error a card shows with URLs removed,PUBLIC_BASE_URLas the link to the library and, in JSON, feed IDs, but never source URLs, reader links or story text. The address is trusted configuration likeFLARESOLVERR_URL, so it may be on your own network, where behind Gluetun it needs a firewall exception; environment proxies are ignored and a redirect counts as a failure./metricsaddsrss_workshop_notifications_totalandrss_workshop_notification_events_dropped_total. See notifications.
Changes
- Name the project in the static fetcher's User-Agent:
RSS-Workshop (+https://github.com/Ldogg123/rss-workshop), replacing the prototype'sGoRSS/0.1 (+self-hosted feed builder). It carries no version, so later upgrades never change what sources see, and it does not reveal which release an instance runs. The new optionalFETCH_USER_AGENTreplaces it for list pages, article pages and the visual selector's static snapshot; startup refuses a value longer than 256 characters or containing anything but printable ASCII, such as a line break, and the startup log reports only whether one is set. Chromium and FlareSolverr keep their own User-Agents for the pages they load. See identifying requests. make release-test, and somake checkand CI, now fails when the dependency table ordocs/licenses/falls out of step with the Go modules the app links: a linked module without a row, a row pinning a version the module graph no longer selects, a missing, misnamed or leftover notice, or a copied notice that differs from its upstream file. Release source collection takes each Debian source version still listed by the current suites from Debian's regular archive, checked against the suite'sSourcesindex, and falls back to Snapshot for older versions and files the archive cannot serve, so a Snapshot outage no longer blocks a release whose packages are current.
Fixes
- Pause and Resume on a feed card no longer send the card's whole copy of the feed. A card drawn before an edit in another tab could undo that edit; if the edit corrected an article selector, the article bodies fetched with the corrected selector were deleted, and a reverted title or interval rewrote the published feed. Every pause and resume also threw away a refresh in progress. They now use their own request,
POST /api/feeds/{id}/enabled, which changes nothing readers see. Older clients and scripts that pause by saving the feed, including ones that send back a feed object fromGET /api/feeds, keep working. - An editor left open no longer re-enables a feed paused from its card. A save keeps the feed's current setting unless Refresh automatically was changed.
- Refresh, saving a feed in the editor, and resuming it now retry a feed held after the database refused a refresh, for example on a full disk. Such a feed used to wait out its hold, up to about 17 hours, while Refresh reported it as queued and the dashboard showed it as due and healthy. A retry that fails again waits twice as long as the last one. The card now says Waiting to retry, feed listings report
"held": true, and the newrss_workshop_feeds_heldmetric counts these feeds;rss_workshop_feeds_duekeeps its meaning and still includes them. - A refresh thrown away because its feed was edited while it ran is now logged as
refresh discardedat info level, instead ofrefresh finishedwith an item count orrefresh failedwith a failure count, although nothing from it was stored. A feed deleted during its refresh is logged the same way and is no longer held; before, it was logged at error level as if the database had refused the write. - A refresh cut short by stopping or restarting the app is no longer stored as a failure. A restart that cut a refresh short before its stories were extracted gave a healthy feed an error such as
context canceledon its card, a failure in a row and a backoff. Such a refresh is now discarded, logged asrefresh discardedwithreason="server stopping", and leaves no run in Diagnostics, so the feed is still due and refreshes when the app starts again. A refresh that runs out of its own time still counts as a failure, and one that had already succeeded is still stored. - Refresh answers 500 when the database cannot be read, and Reset feed links when it cannot be written, instead of 404 as if the feed did not exist.
- Read the time zone a date names. An RFC 1123 date such as
Thu, 05 Nov 2026 10:00:00 ESTwas stored as 10:00 UTC, five hours early, because a zone name the recipe's time zone does not define was given a zero offset: with a blank time zone every US zone name was hours off, any made-up name was accepted as UTC, andGMT+3was read as UTC. A zone name now takes the meaning the recipe's time zone gives it, soCSTstays China Standard Time underAsia/Shanghai, and otherwise the meaning RFC 5322 gives it (UT,GMT,EST,EDT,CST,CDT,MST,MDT,PST,PDT).GMT+3is read as +03:00 andGMT+0as UTC, and any other name leaves the date unrecognized rather than guessing. The same rules apply to a Go date layout containingMST. RFC 1123 dates may also have a one-digit day and leave out the seconds. See time zones. - Decode pages in static mode the way browsers do. A site served in windows-1252, ISO-8859-x, Shift_JIS, EUC-KR, windows-1251, UTF-16 or another encoding browsers support was read as UTF-8, so static mode, and Auto when it did not render, published its accented and CJK characters as
�, while Chromium mode showed its list pages correctly. The encoding now comes from a byte order mark, theContent-Typecharset or a<meta>charset in the first 1,024 bytes, for list pages, article pages and the visual selector's static snapshot alike. A page that declares nothing or an encoding browsers do not support is read as UTF-8 as before, and so is a page that declares a legacy encoding but whose text is mostly valid UTF-8, the usual sign of a site that moved to UTF-8 and kept its old declaration. The 4 MiB page limit now also applies after decoding, as it already did in Chromium mode, so a page close to that size in an encoding whose characters take more bytes in UTF-8, such as Shift_JIS, can now be refused. See fetch modes. - Stop showing a story's image twice when its list-page description already shows it, as happens when the Description selector covers the whole card. The image is now left out when the description has an image with exactly that address; a link to the image, as lightboxes use, or a different size of it still gets the image shown above. RSS
media:contentand the Atom enclosure are unchanged. - Stop failing FlareSolverr feeds that fall due together. The scheduler started every due feed at once, up to
STATIC_WORKERS, against FlareSolverr's single default slot, and each refresh waited for that slot inside its own deadline, so after a restart, an outage or an import the later feeds failed withcontext deadline exceededand backed off. RSS Workshop now starts only as many FlareSolverr refreshes as there are free slots, counting slots still held after an interrupted request. The rest stay due and start oldest first as slots free up, with no failure recorded, and feeds in other fetch modes are not held back. A refresh hands its slot on once its list page is solved, unless it renders its article pages through FlareSolverr, which it then fetches one by one. A FlareSolverr preview or visual-selector page load that finds every slot in use answersFlareSolverr is busyat once instead of waiting out its deadline. It has no claim on the next free slot: while FlareSolverr feeds are due, as after a restart, an outage or an import, each freed slot goes to them first, so previews and page loads can stay busy until those feeds have refreshed. See FlareSolverr capacity. - Name what failed when FlareSolverr cannot be reached. Every connection problem used to read
FlareSolverr request failed; check the service address, connection, and timeout, and any other service's reply onlyFlareSolverr service returned HTTP n. Previews, the visual selector, feed cards, Diagnostics and the log now name the step: a DNS lookup, a refused or timed-out connection, no network route, a connection that failed before the request was sent (usually TLS), an address that is not the FlareSolverr/v1API, a reply from something other than FlareSolverr, a dropped connection, no reply before the deadline, or a wait for a free slot. The messages are fixed text and never include the service address, the source URL or the reply. A request that never connected now frees its slot at once instead of holding it for the whole solver timeout. FlareSolverr troubleshooting says what to check for each message. - Point the editor's "FlareSolverr is not configured" hints to the setup guide. The advice now holds for Docker Compose, where the container must be recreated with
docker compose up -dbecausedocker compose restartkeeps its old environment, for native executables, which do not read.env, and for installs sharing Gluetun's network, where127.0.0.1is the right address. - Stop a feed refreshing twice in a row when its refresh ended while the scheduler was reading the feed list. That list still showed the feed due, so it started again at once, which with FlareSolverr spent a solve ahead of feeds waiting their turn.
Browser image
The browser image carries Debian's Chromium 156.0.8078.79-1~deb13u1 from trixie-security (DSA-6605-1), the newest Debian package when this release was built. Google published further Chromium security fixes on 2026-11-03 (Extended Stable 156.0.8078.88 and Stable 157) that Debian has not packaged yet; a patch release will follow once Debian ships them. Rendered pages stay sandboxed and confined to the outbound proxy's validated destinations. The static image contains no browser.
Verifying a download
Native archives ship with a .sha256 sidecar:
sha256sum -c rss-workshop-v1.2.0-linux-amd64.tar.gz.sha256Corresponding Debian source archives for both image architectures are attached to this release. If an archive is split into parts, reassemble it before verifying:
cat debian-sources-v1.2.0-linux-amd64.tar.gz.part-* > debian-sources-v1.2.0-linux-amd64.tar.gz
sha256sum -c debian-sources-v1.2.0-linux-amd64.tar.gz.sha256Images
| Variant | Tag |
|---|---|
| Browser (default) | ghcr.io/ldogg123/rss-workshop:v1.2.0-browser |
| Static | ghcr.io/ldogg123/rss-workshop:v1.2.0-static |
The latest, latest-browser and latest-static aliases advance to this release. Compose installs that follow latest pick it up the next time they pull and recreate the app; read Upgrading from v1.1.1 first, and update your checkout to get the new Compose settings. Pin a version tag or digest with RSS_IMAGE to stay put.