4
3
Fork
You've already forked PipePipeExtractor
3

Bilibili: auto retry when requesting UserSpace response if blocked by risk control #12

Closed
chr_56 wants to merge 2 commits from chr_56:user_space into main
pull from: chr_56:user_space
merge into: NullPointerException:main
NullPointerException:main
Contributor
Copy link
  • Automatic retry for 10 times when requesting BiliBili User Space response if blocked by risk control.
  • Update forged devices list

Suggestions from NullPointerException/PipePipe#122

- Automatic retry for 10 times when requesting BiliBili User Space response if blocked by risk control. - Update forged devices list Suggestions from NullPointerException/PipePipe#122

Seems we still being blocked even after many retries. We might have to update our anti-riskcontrol codes - see NullPointerException/PipePipe#120

Seems we still being blocked even after many retries. We might have to update our anti-riskcontrol codes - see https://codeberg.org/NullPointerException/PipePipe/issues/120

Also please always consider use wildcard importing when there are 3+ imports from the same package.

Also please always consider use wildcard importing when there are 3+ imports from the same package.
Author
Contributor
Copy link

Seems we still being blocked even after many retries. We might have to update our anti-riskcontrol codes - see NullPointerException/PipePipe#120

See bilibili-API-collect#951:

  • dm_img_list: user actions (mousemove, click etc.)
    I tried to implement the simulation earlier last month, but maybe because of "not real concrete" simulation , server blocked me without mercy no matter how many tries. We may still use empty list.
  • dm_img_inter: rendered information
    Hard, very hard to implement the simulation. This contains rendered results for a browser, like certain html elements (searchbox and entire content "showcase" windows) positions. Maybe we can only hardcoded several.

As community complains, sometimes it's not working even if you forge them, or you get bypassed even if you hardcode it.

> Seems we still being blocked even after many retries. We might have to update our anti-riskcontrol codes - see https://codeberg.org/NullPointerException/PipePipe/issues/120 See [bilibili-API-collect#951](https://github.com/SocialSisterYi/bilibili-API-collect/issues/951): - `dm_img_list`: user actions (mousemove, click etc.) I tried to implement the simulation earlier last month, but maybe because of "not real concrete" simulation , server blocked me without mercy no matter how many tries. We may still use empty list. - `dm_img_inter`: rendered information Hard, very hard to implement the simulation. This contains rendered results for a browser, like certain html elements (searchbox and entire content "showcase" windows) positions. Maybe we can only hardcoded several. As community complains, sometimes it's not working even if you forge them, or you get bypassed even if you hardcode it.
Author
Contributor
Copy link

Also please always consider use wildcard importing when there are 3+ imports from the same package.

Excuse me, so can you export your Jetbrain IDEA / Android Studio codestyle setting to repo and added to git.
Or we can use codestyle from checkstyle and ktlint.

And after doing the said above, could you please execute code formatting for entire repo (or added files which are distinct from original upstream one).

So, there would not be much trouble in imports and misformatted code which are unrelated from topic.

Besides, have you ever considered to split utils.java? Many PRs may change this file and cause merging conflictions.

> Also please always consider use wildcard importing when there are 3+ imports from the same package. Excuse me, so can you export your Jetbrain IDEA / Android Studio **codestyle setting** to repo and added to git. Or we can use codestyle from checkstyle and ktlint. And after doing the said above, could you please execute **code formatting** for entire repo (or added files which are distinct from original upstream one). So, there would not be much trouble in _imports_ and misformatted code which are unrelated from topic. Besides, have you ever considered to **split** utils.java? Many PRs may change this file and cause merging conflictions.

The code formatting check intentionally remains disabled. Focusing on code formatting only wastes the limited development time of developers. I don't care about code formatting - I can even tolerate "bad smell" code as long as it works properly and facilitates rapid iteration of functionality. I'm making this suggestion because you've intentionally turned the original wildcard matching into a dozen lines of subpackage imports, but I haven't forced you to modify before submit it.

Apart from the result, I've NEVER expressed ANY opinions about your code. This has been the development philosophy of PipePipe from the beginning. If you prefer, NewPipe has everything - style checks, unit tests, CI/CD pipelines, and rigorous code reviews that can take several months. You will never find them here.

Besides, have you ever considered to split utils.java? Many PRs may change this file and cause merging conflictions.

As long as it works properly, I will merge it locally, so it's okay.

The code formatting check intentionally remains disabled. Focusing on code formatting only wastes the limited development time of developers. I don't care about code formatting - I can even tolerate "bad smell" code as long as it works properly and facilitates rapid iteration of functionality. I'm making this suggestion because you've intentionally turned the original wildcard matching into a dozen lines of subpackage imports, but I haven't forced you to modify before submit it. Apart from the result, I've **NEVER** expressed **ANY** opinions about your code. This has been the development philosophy of PipePipe from the beginning. If you prefer, NewPipe has everything - style checks, unit tests, CI/CD pipelines, and rigorous code reviews that can take several months. You will never find them here. > Besides, have you ever considered to split utils.java? Many PRs may change this file and cause merging conflictions. As long as it works properly, I will merge it locally, so it's okay.

Seems we still being blocked even after many retries. We might have to update our anti-riskcontrol codes - see NullPointerException/PipePipe#120

See bilibili-API-collect#951:

  • dm_img_list: user actions (mousemove, click etc.)
    I tried to implement the simulation earlier last month, but maybe because of "not real concrete" simulation , server blocked me without mercy no matter how many tries. We may still use empty list.
  • dm_img_inter: rendered information
    Hard, very hard to implement the simulation. This contains rendered results for a browser, like certain html elements (searchbox and entire content "showcase" windows) positions. Maybe we can only hardcoded several.

As community complains, sometimes it's not working even if you forge them, or you get bypassed even if you hardcode it.

I don't know if hardcoded dm_img_inter works but at least attempts should be made as the current version keeps being blocked.

> > Seems we still being blocked even after many retries. We might have to update our anti-riskcontrol codes - see https://codeberg.org/NullPointerException/PipePipe/issues/120 > > See [bilibili-API-collect#951](https://github.com/SocialSisterYi/bilibili-API-collect/issues/951): > > - `dm_img_list`: user actions (mousemove, click etc.) > I tried to implement the simulation earlier last month, but maybe because of "not real concrete" simulation , server blocked me without mercy no matter how many tries. We may still use empty list. > - `dm_img_inter`: rendered information > Hard, very hard to implement the simulation. This contains rendered results for a browser, like certain html elements (searchbox and entire content "showcase" windows) positions. Maybe we can only hardcoded several. > > As community complains, sometimes it's not working even if you forge them, or you get bypassed even if you hardcode it. I don't know if hardcoded `dm_img_inter` works but at least attempts should be made as the current version keeps being blocked.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
NullPointerException/PipePipeExtractor!12
Reference in a new issue
NullPointerException/PipePipeExtractor
No description provided.
Delete branch "chr_56:user_space"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?