Closed leonghui closed 5 months ago
yes correct! sorry about that, seemed like the right idea at the time :)
It should i guess default to "on", so by default muted watched are in the RSS so it doesnt affect existing setups
No worries, and thanks again for this amazing project!
+1 on not impacting existing setups
@leonghui merged
Thanks! Tested on the latest dev
image and it works!
Version and OS v0.45.23 on linux/docker
Is your feature request related to a problem? Please describe. Since https://github.com/dgtlmoon/changedetection.io/pull/2374 was merged, muted watches are gone from my RSS feed. Correct me if I am wrong but now there is no straightforward way for users to be aware of changes from active but muted watches, except via the WebUI.
Describe the solution you'd like Please allow muted watches in the RSS feed to be controlled as a setting.
Describe the use-case and give concrete real-world examples I use a mix of "active" (immediate) and "passive" (on-demand) notifications. For example, a website defacement needs to be notified immediately (via Apprise) while a low-priority price change (grocery item) does not.
For passive notifications, I have been relying on muted watches + RSS reader but this is no longer possible due to the recent change.
Additional context For other users facing a similar issue, my workaround is to unmute the affected watches and insert a "dummy" notification URL that does not trigger an error, e.g.
get://localhost:5000/