Skip to content

fix: update Bilibili user and followings APIs - #35

Open
coni233 wants to merge 2 commits into
noneplugin:mainfrom
coni233:fix/bilibili-user-api
Open

fix: update Bilibili user and followings APIs#35
coni233 wants to merge 2 commits into
noneplugin:mainfrom
coni233:fix/bilibili-user-api

Conversation

@coni233

@coni233 coni233 commented Aug 16, 2026

Copy link
Copy Markdown

Summary

  • Replace the retired Bilibili user-card API.
  • Handle private following lists with a clear message.
  • Show an in-image warning when Bilibili only exposes a partial following list.
  • Accept Bilibili mobile copied UID formats such as UID:123456.

Testing

Tested manually with:

  • public users with different UIDs, confirming results no longer reuse the same following list;
  • users with private following lists;
  • users whose followings are only partially exposed by Bilibili;
  • plain UID and UID:-prefixed UID input.

Notes

Bilibili's current followings API may expose only part of a target user's following list. The rendered result image now displays this limitation.

Future work

This is not part of the current PR. We may explore whether third-party data-recording services such as Danmakus can provide public live-room-entry events as an additional signal for composition checks when Bilibili does not expose a complete following list.

Replace retired user-card followings data with the current Bilibili APIs.

The new followings API may expose only part of a target user's follow list; render this limitation in the result image and report private follow lists clearly.
Normalize copied UID: and UID: prefixes before resolving a Bilibili user.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant