Reqest: Technical Details of FileData_V4 Blob Format for NZB

[danneauxs]

Hello,
This might not be something I should be asking but I'm just experimenting with vide coding and this project just seemed to pop up. Basically, I just wanted to see if I could write a program that searched the db3 files and retured a search result. That worked, then I figured why not have it create an nzbd. Having issues. (I just wanted to play with accessing a search through a web server hosted on my site without having to use newbinpro via vnc which is pain on my phone - I'm old that the damn screen is small. It's just an exercise so you can tell me to smeg off with no worries.
The quesiton is AI generated so I didn't mess it up. - Thanks in Advance

I am trying to programmatically parse the NN_FileData blobs from the FileData_V4 table in Storage.db3 to extract message IDs and part numbers for the purpose of rebuilding NZB files.

I've successfully extracted the raw blobs and my analysis shows the following:

1. Gzip Header: Every blob consistently begins with the gzip magic number (1f 8b), indicating compression.
2. Decompression Failures: Despite the gzip header, all my attempts to decompress the blobs have failed. I have tried:
* Standard gzip and zlib libraries (in Python), which result in errors like "incorrect length check" or "compressed file ended before the end-of-stream marker".
* The command-line gunzip tool.
* Trimming trailing null bytes and other data found at the end of the blobs.
3. Possible Obfuscation: Suspecting the data might be obfuscated, I ran a single-byte XOR key bruteforce on the data following the gzip header, which did not yield a valid result.

This suggests the blob is not a standard gzip stream but has a proprietary modification.

Could a developer or an experienced user shed some light on the FileData_V4 blob format?

Specifically:

* Is there an additional layer of obfuscation or encryption (e.g., a multi-byte XOR key) applied to the compressed data?
* Is there a custom header or structure prepended or appended to the standard gzip stream that I need to account for?
* Are there any open-source implementations or documentation that detail this format?

Any technical guidance would be extremely helpful and appreciated. Thank you ( and yes I am clueless but I'm trying to learn)