Fix for article rich metadata not being populated#118
Merged
0xZhangKe merged 1 commit intoMay 11, 2026
Conversation
Owner
|
Looks like you’ve contributed a lot of changes, really appreciate it. I’ve been pretty busy lately, but I’ll make some time to review and merge them. |
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
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.
sharedHttpClienthas noUser-Agentheader, fixed it, as well as fix for content-type. Use chrome user agent instead, as well as useAccept: text/htmlheader to get websites to send over the og:xxxxx tagshttps://cardyb.bsky.app/v1/extract?url=$websitereturns a JSON formatted response with the data, this is what bluesky-social uses. Failover to existing logic.Here is the app populating rich metadata previews after my fix is applied: