forked from disinclination/ngPost
-
Notifications
You must be signed in to change notification settings - Fork 0
Features
Hydro74000 edited this page May 31, 2026
·
6 revisions
Languages: English | Français
This page is a feature overview. For setup-oriented pages, use Configuration, History and resume, or VPN support.
Feature areas:
- Security and privacy
- Posting workflow
- Automation and packaging
- History and recovery
- Performance and reliability
- Isolated Tunneling: Only ngPost traffic is routed through the VPN, leaving the rest of the system unaffected.
- OpenVPN & WireGuard: Native support for both backends.
- Per-Server Routing: Enable VPN on a per-server basis.
- Auto-Connect/Disconnect: Automatic VPN management based on queue activity.
- Available since v5.3.0. See the VPN Support page for more details.
- Full obfuscation using UUIDs for the subject and message ID, with a random poster.
- Note: If the NZB file is lost, the post cannot be found on Usenet or indexers.
- Secure method with no need for file obfuscation or passwords.
- Keep NFO Visible: Option to keep the .nfo extension visible even when using filename obfuscation. This allows indexers to identify the content more easily while keeping the main data secure.
- Copy NFO with NZB: Automatically copy the original .nfo file next to the generated NZB file, facilitating manual uploads to indexers.
- Prepare multiple posts while others are uploading.
- Ability to cancel pending posts.
- Scan a folder and automatically post each file/folder after compression.
- Accessible via the
--autocommand-line option or the "Auto Posting" tab in the GUI.
- Compress using RAR or 7zip with random name obfuscation and password protection.
- Generate par2 files before posting.
-
Auto-detection: For AppImage and Windows, the application automatically detects embedded
rarandpar2binaries.
-
SQLite database: posts are recorded in a structured database with full traceability down to the individual article (replaces the old CSV
POST_HISTORYfile). - Article-level resume: re-post only the articles that failed or were lost, with a fresh Message-ID — no need to re-upload the whole archive.
- NZB regeneration: rebuild a complete NZB file from the history at any time, including from the CLI.
-
History GUI tab: browse posts, view statistics charts, and manage resumes; multi-selection and the
Delkey remove entries. -
Full CLI control: list, inspect, regenerate and resume from the command line (
--history,--history_show,--regenerate_nzb,--resume_list,--resume_post, …, plus--jsonfor scripting). See the History and resume page. -
Legacy CSV import: existing CSV history is imported automatically on first launch (original file preserved); a manual
--history_import_csvis also available. -
Archive passwords: stored in the history by default, masked in the UI/CLI/exports, and included in regenerated NZBs only on explicit request (
--include_password).
- Bundled with ParPar as the default redundancy engine (on Windows,
par2cmdlineand MultiPar are shipped as fallbacks); users can also point to another tool such as MultiPar. - Configure using the
PAR2_PATH/PAR2_ARGSkeywords in the config file (or--par2_path/--par2_pcton the command line).
- Supports posting of multiple files and folders.
- Multiple server connections supported, configurable via the config file or HMI.
- SSL support for connections (OpenSSL 3.x supported).
- Distribute connections across several threads.
- Default thread count based on system cores, customizable by the user.
- Articles are prepared on the main thread using yEnc encoding.
- Upload threads are optimized with two articles ready in advance per connection.
- Utilizes asynchronous sockets within upload threads.
- Files are opened once in the main thread and processed sequentially.
- Articles are distributed across all connections to avoid multiple files being open simultaneously.
- Generate a random poster or use a fixed one if desired.
- Generate NZB file after preparing posts.
- Add metadata, such as a password, to the NZB header.
- Retry posting articles with a different UUID in case of errors.
- Reconnection attempts made on socket errors using retry parameters.
- Handle interruptions by generating an NZB file with posted files.
- Unposted files are listed for easy reposting and manual NZB file concatenation.
- Proper closure of the application in CMD during interruptions.
Start
Use ngPost
Project
Démarrer
Utiliser ngPost
Projet