[BUG]: Current style of GUID generation with repeat=false may cause notification failures #33
Labels
No labels
ASAP
bug
duplicate
enhancement
help wanted
important
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 20 minutes 58 seconds
Due date
Felisp
20 minutes 58 seconds
No due date set.
Dependencies
No dependencies set.
Reference: Treebrary.org/rss-thread-watcher#33
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If thread already was on some position before, feed reader may ignore future occurrings of thread on that position
tl;dr if thread was once on
96%
, the second time it gets there, feed item may be considered already read by RSS reader.Solution is to introduce some better identifier for
repeat=false
instead of thread number.This bug can be worked around by using
repeat=true
orrepeat=paranoid
Number of last post or time of last update will be used. Not sure which one makes more sense
last_modified
was used, fixed in20752a3b1c