The doesn't match any previous text operator can now be used to check if the new text change is distinct from any updates present in the change history. For instance, when monitoring a list of available jobs, if a job is added or removed intermittently then this operator can be used to suppress the noisy alerts.
ah! the firefox extension hasn’t been updated in while due to issues with mozilla store. you will need to use other browser extension of the desktop app to use this.
I have the same issue with the distill firefox extension.
Is it planned to implement the condition “doesn’t match any previous text” in the next update for the firefoxe extension and is there a date when it will be released?
that is a good idea. we will probably do that early this year.
“doesn’t match any previous text” has been implemented in an efficient way that involves fetching and comparing content’s hash. as a result, it adds very little overhead and is very fast. the flipside of using content’s hash is that it can’t be used for any other kind of comparison except equality checks.
@angus2064 The change history stores the 10 (20 in case of Professional and Flexi plan) most recent changes. The condition “doesn’t match any previous text” will apply to any of these changes displayed in the change history at any given time.
thanks for checking in. currently there is no eta. we are most likely to pick this up in later half of these year once the current milestones have been accomplished.