QWKSync.NET is a small, dependency-free .NET library that exists for one reason only:
To safely and predictably move QWK and REP files between a local application and a remote endpoint.
It is a plumbing component, not a framework.
Getting Started Guide - Step-by-step introduction to using QWKSync.NET
GitHub Repository - Source code, issues, and contributions
QWKSync.NET serves developers and archivists working with historical BBS data:
QWKSync.NET operates strictly at the transport and orchestration level.
It:
It does not understand what those files mean.
QWKSync.NET is not:
If a feature requires knowing what is inside a packet, it does not belong here.
QWKSync.NET makes no assumptions about packet counts or relationships.
A sync session may:
There is no assumed pairing between QWK and REP files.
All such meaning belongs to the calling application.
All file movement happens via transport interfaces.
Never implements HTTP, HTTPS, FTP, SFTP, or similar protocols.
By default, QWKSync.NET is intentionally conservative.
Defaults include:
Any deviation must be explicitly configured.
Extensibility exists only at the transport layer.
If you need protocol knowledge, build a transport extension. Transport extensions add transport protocols only. Automation remains application-level.
If you need packet knowledge, use QWK.NET or application code.
If you are unsure whether something belongs in QWKSync.NET, ask this:
“Does this require understanding what a packet means?”
If the answer is yes, it does not belong here.
QWKSync.NET is intentionally narrow.
That narrowness is its value.