-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
broken feed #4
Comments
ah yep - i've noticed this (& even read the same rachelbythebay post!) but i haven't had the time to implement ETag support. bubbling fetch failures up to users is another feature that i've long wanted to add, but haven't had the time. i think your intuition is spot on - i invited you to be a collaborator on this repo btw, in case you have the motivation to implement these features yourself / help guide other people. i may not have time for it for a few months, given that it's summer & my day job is picking up steam. fetch failures is higher priority imho. i think the implementation should probably be something like:
i was also thinking about adding an |
Thanks for the invitation, I'll consider it. But also, a few thoughts:
|
i added a migration system in 8f3db73
good call. for now, i've exposed fetch failures to users, implemented in dff68a9
agreed, but there needs to be a way to tell the difference between an actively dead feed and a feed that failed a fetch at some point in the past. |
So, rachelbythebay's feed broke for me.
So, first off, a small feature request - it'd be nice to be able to see the last error (if any), and the last status code. Without that, I have to diagnose the problem blind, but I think the issue is not supporting Last-Modified/ETag (note that the former can be tricky).
Apart from fixing this particular feed, this will reduce your bandwidth usage, and lessen the load on people's servers, which is a win-win.
The text was updated successfully, but these errors were encountered: