Add BrazzersVR Scraper Fixes #1860 #1852
Merged
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
Appears to currently work. More wide spread testing needed. Had some randomness to what scenes were being shown on the index page. The current set of URLs appears to return the correct scenes. The next index page does not appear to show up in the colly request only on a working browser. Had to resort to checking if any scene links where available and advancing if true.
Collaborator
|
The scraper works fine for me. However I think the numerical ID from the scene URL would be a better fit for the scene ID than the title slug, since it is less likely to change. |
Contributor
Author
|
Yeah. I put in a comment in to code for the date to be watched. As bazzers redid their website so who knows if the new scenes will be posted and if date is correct as the variable name I pull from is It does grab the scene ID from the home page url. I tried grabbing everything I could from the json script block as I am indeed worried the class ids will change cause it looks randomized/minifed |
Abandoned the OG BazzersVR scraper in favor of the backend API call. Which shares the same API and JSON structure as VirtualPorn. All seems to be in working order. Some of the code for VirtualPorn may still need to be stripped or adjusted based on differing sites. Current things that need be check or adjusted Filenames and Member Link
Contributor
Author
|
Update: Moved the bazzers scraper into virtualporn. It shares the same backend API and JSON structure. Everything seems to return correctly. Made adjustments or passed through strings where needed for the differences between sites. Things below are behind the paywall that should be checked
|
The Origin and Refer are important. It should prevent the collisions in the API call when both scrapers are ran at the same time. AKA VirtualPorn returning scene data for Brazzers Also updated for parallel scraper optimization
Change from one run on function input to use a type struct. Makes the code cleaner and easer to read. Another attempt at squashing the API returning results not belong to the correct studio. This should work has the code now checks to ensure the result belongs to the correct scraper. And ignores the rest. Also changed the scraperID to a code used in the API result
balckpixie
pushed a commit
to balckpixie/xbvr
that referenced
this pull request
Aug 9, 2025
* Add BrazzersVR Scraper Appears to currently work. More wide spread testing needed. Had some randomness to what scenes were being shown on the index page. The current set of URLs appears to return the correct scenes. The next index page does not appear to show up in the colly request only on a working browser. Had to resort to checking if any scene links where available and advancing if true. * Go fmt & Cleanup * BazzersVR v2 Abandoned the OG BazzersVR scraper in favor of the backend API call. Which shares the same API and JSON structure as VirtualPorn. All seems to be in working order. Some of the code for VirtualPorn may still need to be stripped or adjusted based on differing sites. Current things that need be check or adjusted Filenames and Member Link * Remove Debugging Prompt * Go fmt fixes * Code Optimizations & Bug Fix The Origin and Refer are important. It should prevent the collisions in the API call when both scrapers are ran at the same time. AKA VirtualPorn returning scene data for Brazzers Also updated for parallel scraper optimization * Bug Fix & Code Optimatzions Change from one run on function input to use a type struct. Makes the code cleaner and easer to read. Another attempt at squashing the API returning results not belong to the correct studio. This should work has the code now checks to ensure the result belongs to the correct scraper. And ignores the rest. Also changed the scraperID to a code used in the API result * Comment cleanup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Appears to currently work. More wide spread testing needed. Had some randomness if valid scene were shown on the index page. The current set of URLs appears to return the correct scenes.
The next index page does not appear to show up in the colly request only on a working browser. Had to resort to checking if any scene links where available and advancing if true.