BiliBili: fix user space videos Client API & add new user space videos Search API #17

chr_56 commented 2025年10月12日 13:53:30 +02:00

I understand that PipePipe 5 is coming soon, and this repo would be deprecated.

However, until the stable PipePipe 5 is released, which appears to be quite some time away, maintaining legacy version may be unavoidable.

So here is a bug(s) fix for maintenance.

In this PR:

• Fix a defect in requestUserSpaceResponse(), causing infinite trying instead of switching API when meeting a unknown error code;
• Fix user space videos (BiliBili channel videos) Client API returning -400¹ , since it requires AppSign² query parameter signature validation now;
• Add user space videos Search API³ , which has less rick controls;
• Clean up code.

<h3><b>I understand that PipePipe 5 is coming soon, and this repo would be deprecated. </b></h3> However, until the stable PipePipe 5 is released, which appears to be _quite some time away_, **maintaining legacy version _may_ be unavoidable**. So here is a bug(s) fix for **maintenance**. In this PR: - Fix a defect in `requestUserSpaceResponse()`, causing **infinite trying** instead of switching API when meeting a unknown error code; - Fix user space videos (BiliBili channel videos) **Client API** returning -400[^issue], since it requires AppSign[^as] query parameter signature validation now; - Add user space videos **Search API**[^sapi], which has less rick controls; - Clean up code. [^issue]: See [bilibili-API-collect#1410](https://github.com/SocialSisterYi/bilibili-API-collect/issues/1410) [^as]: See document [AppSign](https://github.com/SocialSisterYi/bilibili-API-collect/blob/60a0c5d1a2f44fe61335da04571305fa7727a968/docs/misc/sign/APP.md) [^sapi]: See document [SearchAPI](https://github.com/SocialSisterYi/bilibili-API-collect/blob/60a0c5d1a2f44fe61335da04571305fa7727a968/docs/video/collection.md#%E6%A0%B9%E6%8D%AE%E5%85%B3%E9%94%AE%E8%AF%8D%E6%9F%A5%E6%89%BE%E8%A7%86%E9%A2%91)

NullPointerException commented 2025年10月12日 14:21:55 +02:00

Yeah you are right, my plan is to still maintain the legacy version for about 6 months - the main reason is the minSdk is raise from 21 to 26.

Yeah you are right, my plan is to still maintain the legacy version for about 6 months - the main reason is the minSdk is raise from 21 to 26.

chr_56 commented 2025年10月12日 15:05:31 +02:00

Thanks. I would consider to migrate it to new Extractor. (it looks that channel-related development is in very early stage now, in alpha2.)

Thanks. I would consider to migrate it to new Extractor. (it looks that channel-related development is in very early stage now, in alpha2.)

NullPointerException commented 2025年10月13日 23:36:51 +02:00

Thanks. I would consider to migrate it to new Extractor. (it looks that channel-related development is in very early stage now, in alpha2.)

not really - in my test the extraction is already stable enough, haven't met any failure during the last week. The only issue is only video tab is done for now.

If we still need API flipping, we would need to cache the state in response.

> Thanks. I would consider to migrate it to new Extractor. (it looks that channel-related development is in very early stage now, in alpha2.) not really - in my test the extraction is already stable enough, haven't met any failure during the last week. The only issue is only video tab is done for now. If we still need API flipping, we would need to cache the state in response.

chr_56 commented 2025年10月14日 04:09:13 +02:00

1. I am kind of busy recently; I didn't dig deep into source code.
2. Rick Control failures are more likely to be relative with your Internet environment especially when you are logged out, basing on my experience; In BiliBili Web (PC, logged out e.g. in browser private mode), you may even meet Rick Controls - you need pass a Captcha to proceed, this is a phenomenon of Rick Controls.
3. For planning/implementation of API flipping, I may be free in lately November or December to get started. Thank you.

1. I am kind of **busy recently**; I didn't dig deep into source code. 2. Rick Control failures are more likely to be relative with **your Internet environment** especially when you are **logged out**, basing on my experience; In BiliBili Web (PC, logged out e.g. in browser private mode), you may even meet Rick Controls - you need pass a Captcha to proceed, this is a phenomenon of Rick Controls. 3. For planning/implementation of API flipping, I may be free **in lately November or December** to get started. Thank you.

NullPointerException commented 2025年10月14日 04:49:05 +02:00

Thanks for the update. For now, since the extraction seems stable in my tests from several different IPs, I think it's fine to leave it as-is. We can revisit it once we really run into issues - no rush.

Thanks for the update. For now, since the extraction seems stable in my tests from several different IPs, I think it's fine to leave it as-is. We can revisit it once we really run into issues - no rush.

NullPointerException commented 2026年01月25日 23:24:45 +01:00

I finally found you are right. It's much better to develop 5.0 in a new repo and release it as a new app.

It's now https://github.com/InfinityLoop1308/PipePipe-X . 1.0 just released.

Classic version will still be maintained.

I finally found you are right. It's much better to develop 5.0 in a new repo and release it as a new app. It's now https://github.com/InfinityLoop1308/PipePipe-X . 1.0 just released. Classic version will still be maintained.