slumberthud.com

What It Is

TAFT (Transport Agnostic File Transfer protocol) is a specification for remote file access and transfer. Its goal is to replace the complexity and long-standing issues of FTP with a simpler approach. TAFT itself is not a network protocol; instead, it defines how clients and servers upload, download, list directories, and manage files through messages, with the expectation that it will run over secure transports such as HTTPS.

Core Capabilities

TAFT is designed to be stateless, sessionless, and transport-agnostic. Messages consist of a required JSON header and an optional Base64-encoded file content body; requests are initiated by the client, and the server responds one-to-one. The protocol defines commands such as hello, list, download, upload, rename, move, delete, mkdir, and rmdir, and divides capabilities into levels 0 through 3. Public access requires no additional credentials, while private access relies on an accessKey. Path rules, version handling, error states, and timestamp formats are all clearly specified. The download command also supports offset and length, making it suitable for chunked reads of large files.

Pricing and Format

The main text does not provide any information about a commercial product, hosted service, or pricing, nor does it state whether the project is open source. It reads more like a protocol specification than a complete developer-tool platform. The text also does not mention ready-made client or server implementations, SDKs, package-manager installation methods, or deployment guides.

Pros and Cons

The strengths are that the specification has a clear goal, a small protocol surface, and is easy to understand thanks to its use of JSON and Base64. The HTTPS-based approach also reduces the complexity of implementing the underlying transport layer. It places detailed constraints on directory listings, file metadata, SHA-256 hashes, UTC timestamps, and access errors.

The drawbacks are also fairly clear: the upload section is still marked TBD, indicating that the specification is not yet fully finalized. The lifecycle, permission binding, storage, and management of access keys are all left to implementers, which increases the cost of building a secure production deployment. Transferring files with Base64 also increases payload size and encoding/decoding overhead, so it may not be ideal for high-performance large-file scenarios.

Who It’s For and Access from China

TAFT is suitable for protocol designers, internal-tool developers, and teams looking to replace FTP/SFTP/WebDAV with lightweight HTTP/HTTPS messages. If you need a mature ecosystem, client compatibility, or a production-grade permission system, you should still evaluate alternatives. The crawled text does not provide any information about site accessibility, so its access status from China is unknown.