search

mbruel / ngPost

Command Line (or minimalist GUI) usenet poster for binaries developped in C++/QT designed to be as fast as possible and offer all the main features to post data easily and safely. Releases for Linux, Windows and MacOS are available.
GNU General Public License v3.0
179 stars 34 forks source link

Question about automated posting #200

Open IndustrialOne opened 7 months ago

IndustrialOne commented 7 months ago

Hey mbruel, great program, I love it, but I need a way to resume my uploading after closing the program.

I noticed that drag-dropping all my files with the quick post method will automatically create subject lines 1/50 2/50 etc. but the problem is I can only upload about 10 of these due to bandwidth restrictions. I plan to upload a terabyte of stuff across many months. So if I close the app and add another 10 RAR partials, they won't be uploaded as 11/50, 12/50 but will start back from 1.

The automated posting method gives me the impression that it will just upload every individual RAR as subject 1/1. The goal is to have the entire collection in one NZB file that will be easy to navigate. My bad if my question is answered in the documentation but I didn't see it.

Btw, I don't need any help from ngpost raring or paring, I have already taken care of that. I just need the subject line numbering to continue as I add more files. A way to save the session would be useful, or a way to tell ngpost not to start from 1.

Zach99f commented 1 month ago

What you're describing is a method to handle incomplete or interrupted uploads when posting content to Usenet. Here's a breakdown of the process:

  1. Upload to a Well-Known Group:

    • You upload your files (usually split into smaller parts) to a well-known Usenet newsgroup. This is typically done using a Usenet posting tool like ngpost.
    • The newsgroup should be one that is commonly used for the type of content you're uploading, making it easier for others to find.

  2. Use an Indexer:

    • An NZB indexer tracks the files posted to Usenet and creates NZB files, which are like pointers to the specific parts of the files on Usenet.
    • After uploading, you use an NZB indexer to grab the NZB file associated with your upload. This NZB file can then be shared or used to download the content via a newsreader.

  3. Resuming Interrupted Uploads:

    • If your upload via ngpost is interrupted, instead of waiting for ngpost to resume, you can simply re-upload the incomplete parts to the same newsgroup.
    • By uploading to the same group, you make it easier to manage and find the parts of your upload, ensuring they are all indexed together.

  4. Handling Incomplete Uploads:

    • If you've uploaded to the same group and the parts are indexed together, you can download the complete file using the NZB. If the upload is still incomplete, a good newsreader will try to download whatever parts are available and may use PAR2 files (if included) to repair the missing parts.

This approach ensures that your upload is managed effectively, even if there are interruptions, and that others can easily find and download the content using the generated NZB file.