twitter2rss-fetch.js identifies duplicates only if they're part of the same results after calling a Twitter API. There is no check for duplicates with content that is already in the archive. Perhaps both functionality should be either:
moved or at least duplicated to twitter2rss-render.js
implemented as a check on the archive rather than the API results
twitter2rss-fetch.jsidentifies duplicates only if they're part of the same results after calling a Twitter API. There is no check for duplicates with content that is already in the archive. Perhaps both functionality should be either:twitter2rss-render.js