Enable tracking of errors with syndicatation account update
Short, concise description of the idea
Allow users to subscribe and receive a notification when an error occurs on updating a syndication account.
Full description of the idea
Currently, if an error occurs on updating a syndication account, the only way to be aware of it is to notice that there have been no recent updates and then check the syndication account profile.
This behaviour makes sense for most users, as most do not want regular posts interrupting their Friends page to inform them that one of their chosen feeds isn't working. However, many users would like additional information and to be made aware when there is a repeated problem with a syndicated account, and for irregularly updated feeds, relying on noticing regular posts is not practical.
Adding the ability to track when an error occurs on updating a syndicated account would allow the interested users to opt-in to this notification and would give it informational only placement.
The rate at which LiveJournal checks a feed for updates depends on a number of factors, including whether or not the feed worked on the last check. So it is hopefully possible to send out notifications based on that: Either send out one the first time it can't update but had updated on the last time so that only one notification is sent out. Or send out one only if it also couldn't update the last time, so that a one-time glitch doesn't trigger notifications, but with the knowledge that this may result in multiple notifications per day per user.
- Users who care to be made aware of these problems have an easy and unobtrusive way to do so.
- A notification might allow for more room to explain why the feed isn't working than what is provided on the profile page and can point to FAQ #151 for further information.
An ordered list of problems/issues involved
- It may not be clear to users that this is a method of tracking the errors and not the actual account. (As there is no way to track the actual account.)
- May increase the number of requests to Support to fix a syndicated account when the error lies with the originating website or without further information such as a new feed URL.
An organized list, or a few short paragraphs detailing suggestions for implementation
- As checking the feed is an event I assume it can trigger a notification. etc, etc. Preferably either triggered when the error appears and didn't on the last check, or when the error appears and did on the last check, both of which have their advantages.