You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 24, 2022. It is now read-only.
I have a few feeds that started 404ing (cool uris never change, in reality though...) and a few 403s (mostly due to using OrBot as a proxy, but still), but there seems to be no indication of that inside SpaRSS. I only noticed when switching off OrBot and suddenly a few feeds were massively populated that I hadn't seen in ages...
I suggest giving the user some indication which feeds could not be loaded (status codes, malformed xml, ideally with technical details), so there is a chance to notice, diagnose and fix the problem instead of failing silently ;-)
The text was updated successfully, but these errors were encountered:
I am aware that at least some.information is visible in the feed list when un-hiding all feeds, but by definition that information only shows up when one is explicitly looking for it (I at least default to only seeing feeds with new content, which error'd feed can't have). I'm thinking an actual android notification or a fake/system/SpaRSS "item" with such information or even a dedicated icon with separate view would be much better in order to actually notice a problem ;-)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'd almost consider this a bug.
I have a few feeds that started 404ing (cool uris never change, in reality though...) and a few 403s (mostly due to using OrBot as a proxy, but still), but there seems to be no indication of that inside SpaRSS. I only noticed when switching off OrBot and suddenly a few feeds were massively populated that I hadn't seen in ages...
I suggest giving the user some indication which feeds could not be loaded (status codes, malformed xml, ideally with technical details), so there is a chance to notice, diagnose and fix the problem instead of failing silently ;-)
The text was updated successfully, but these errors were encountered: