Currently, we run scans every 8 hours. If we ran scans more often (say, every hour), then realtime consumers of our data, such as the @SecureTheNews Twitter bot, would be more useful as timely news sources.
Unfortunately, a consequence of the current database design is significant storage and query performance overhead for running scans so frequently (at least, I think--haven't actually measured this). Therefore, this issue probably depends on #84.
Currently, we run scans every 8 hours. If we ran scans more often (say, every hour), then realtime consumers of our data, such as the @SecureTheNews Twitter bot, would be more useful as timely news sources.
Unfortunately, a consequence of the current database design is significant storage and query performance overhead for running scans so frequently (at least, I think--haven't actually measured this). Therefore, this issue probably depends on #84.