[BlueskyBridge] Periodic errors in feed due to Bluesky downtime.

@mruac Periodically the BlueskyBridge will return errors in the feed due to timing out. This most always coincides with brief periods of downtime on Bluesky's servers, which I've confirmed at the time of the error using DownDetector.

When these errors happen, the feed will display with a single item, and its content_html field will be full of errors, including a variation on this line:

cURL error Operation timed out after 5002 milliseconds with 0 bytes received: 28 (https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://public.api.bsky.app/xrpc.bsky.feed.getAuthorFeed?actor=did%3{REDACTED]&filter=posts_no_replies&limit=30

The feed in question is set to display only posts from the user, no replies, and have a cache timeout of 10 minutes.

Not sure if it's possible to implement this, but would there be a way to have the bridge error out without actually updating the feed? In other words, it would stop trying sometime before 5000ms and would leave the feed as-is until the next scheduled check?

Start at the BlueskyBridge entry point and follow how a timed-out Bluesky request updates the feed and its cache. Reproduce a timeout around the reported 5002-millisecond failure and inspect the existing feed output. Done means a failed request leaves the previous feed unchanged and does not publish error text as its only item.