Closed rshipp closed 5 years ago
Putting this through production testing right now.
This is much stronger now. Going to close this issue in favor of #51, since there are some reliability changes coming along with that branch and I don't think we need to track this separately anymore.
There are some situations where unexpected input (like weirdly formed RSS content) causes the program to crash.
We should just do best-effort parsing in these cases. Unexpected input should never cause an uncaught exception; same with network errors/etc. If an input is bad, we can just log something and skip it.
This is a requirement for initial release.