mirror of
https://github.com/Glitchy-Sheep/boosty-downloader.git
synced 2026-10-14 21:33:23 +00:00
[GH-ISSUE #61] Add missing "audio" for download (and create db migrations along the way) #8
Labels
No labels
api-drift
bug
ci
documentation
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Glitchy-Sheep/boosty-downloader#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @thug21 on GitHub (Aug 19, 2025).
Original GitHub issue: https://github.com/Glitchy-Sheep/boosty-downloader/issues/61
Originally assigned to: @Glitchy-Sheep on GitHub.
If the type type: "audio" is encountered, the download fails with an error. Please add this type for downloading
sample boosty response:
@Glitchy-Sheep commented on GitHub (Aug 26, 2025):
Oh, thanks for the report!
I haven't encountered audio fragments yet, so I may have occasionally overlooked that problem.
Was there any traceback from the app or specific exception information when that error occurred?
@Glitchy-Sheep commented on GitHub (Aug 26, 2025):
I don't really remember if there is any protection for unknown data chunks (like audio in your case), but I think they should be skipped and maybe logged as an unknown content type.
I think I should just create a content-creator account and test those cases to be sure.
In general, this looks critical. Thank you again!
@thug21 commented on GitHub (Aug 26, 2025):
Now the download stops because it does not find a suitable type. I just added post_data_types so that such messages are skipped when downloading
@DZamataev commented on GitHub (Oct 30, 2025):
Hi! Did you specify it in settings or make changes in the script? I now face total inability to download content even pointing to a post url without audio when audio is present on the first page in the feed.
@Glitchy-Sheep commented on GitHub (Nov 2, 2025):
@DZamataev
Yeah, I'm so sorry about that. I didn't know that Boosty had some of those content types back then.
The post URL doesn't work because the script still needs to iterate over pages in order to find a specific post. (Maybe there's a solution for targeted search, but I haven't found one yet.)
The audio chunks problem is quite urgent now, but it's hard to fix quickly because it will change the database schema, which would invalidate other users' caches. I'd really like to avoid that and include some sort of automatic migration system instead.
There is a hotfix, but it won't download any audio chunks, you can add them to the schema, specifically in the file:
github.com/Glitchy-Sheep/boosty-downloader@329506929e/boosty_downloader/src/infrastructure/boosty_api/models/post/base_post_data.py (L24-L36)So you can create such model in the boosty_downloader/src/infrastructure/boosty_api/models/post/post_data_types and include it, the downloader will just skip it during html generation.
I think I need to generally refactor some parts of code, because it's too coupled right now because of the HTML generation specifically...
@Rast1234 commented on GitHub (Dec 5, 2025):
Hi! Thanks for the tool and it's nice to have a workaround. If i may share another user perspective. Maybe it's worth fixing this issue without heavy refactoring? Just release as next major version with some note that old cache isn't compatible. IMO broken "download all" functionality for indefinite time out of the box, plus blocked implementation of audio downloads - is much worse user experience - than having to redownload cache...
Upgrading with cache reset is a thing user can do, and it's a choice. Broken "download all" and unsupported post types is not something a user can easily fix. And since it's already been like this for several months, keeping old caches becomes less and less important.
I know how demotivating it can be when you have to refactor a lot of code and keep backwards compatibility, been there with my pet project too. Not fun and takes a lot of effort. If it keeps you blocked from making a fix, maybe it's worth fixing without back compat and move on ;)
@Rast1234 commented on GitHub (Dec 5, 2025):
I got it to work, if anyone is interested you can update several files locally or clone a fork - see MR #77
@Glitchy-Sheep commented on GitHub (Dec 15, 2025):
Yeah, guys, I’m very sorry that I still haven’t fixed this.
The tool was probably really needed by some people during this time.
That’s definitely on me. I thought I could do the fix before December ><
I also really wanted to add audio support with caching (maybe with auto-migration), so users wouldn’t need to re-download many GiBs.
But judging by the stars, the project is clearly valuable to some people, and I really hope to release the fix soon.
@Rast1234 Thanks for your contribution, I'll see the changes soon ❤️
@Rast1234 commented on GitHub (Dec 17, 2025):
If you want, i can share my session with access to a page with a lot of heavy posts, it could help with testing. I discovered a lot of issues addressed in my MR trying to scrape it.