[BlueskyBridge] prevent 408 request timeout by implementing cache #4666
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…/mruac-rss-bridge into 20250810-bluesky-httpcache
Pull request artifacts
last change: Monday 2025-08-11 12:50:51 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR implements a cache on the user handle to DID resolution for up to a week to prevent the resolution being performed each time the feed is generated. Could be permanent, but I don't like it sitting around in the cache permanently. Also added to user profiles (custom name, avatar and description) to the cache for up to the defaulted day.
In the future, I would like the bridge to resolve the user handle to its DID and redirect to itself with the DID as the
user_idif a handle is provided (handles can be changed, DIDs cannot), and in turn automatically correct any currently subscribed feed urls that is using the user handle as theuser_idparameter. This will require implementing a HTTP 301 redirect. Please see #4663 for a discussion on this.Also added more semantics.