Clarify a protocol behavior
Identify the header, response, or operating-system difference that needs a more precise explanation.
Project desk / request review
Shape the next useful test.
The feature-request record helps Tping document practical improvements to packet testing, protocol references, scripting guidance, and platform compatibility. A clear request begins with a specific problem and a controlled use case.
$ tping-request --new \ --area platform-notes [scope] authorized lab workflow [need ] explain capture-driver setup [proof ] reproducible system details [state ] needs technical review next compare versions and document limits record: precise, testable, non-sensitive
Feature requests
Turn friction into documentation.
A request is most useful when it explains what someone is trying to understand, where the current reference falls short, and how the result could be checked without exposing private network information.
Good candidates for a request
Document an environment gap
Describe a reproducible compatibility issue involving a current platform, privilege model, driver, or capture component.
Improve a lab procedure
Suggest a smaller, safer sequence that helps readers validate routing, filtering, timing, or packet construction.
Review path
From question to clear note.
Feature requests become durable reference material only after the problem can be understood, checked, and explained for readers working in different environments.
Frame the problem
State the task, the relevant page or workflow, and the exact point where the current material becomes unclear.
Check the evidence
Repeat the smallest authorized test and record versions, permissions, inputs, outputs, and meaningful limitations.
Write the outcome
Prefer a focused correction, example, compatibility note, or new reference section over a broad unsupported promise.
FAQ
Before submitting an idea.
Use these checks to make a technical request actionable and safe to review.
What belongs in a feature request?
Describe a concrete documentation or tooling improvement, the problem it addresses, and enough non-sensitive context for another reader to understand the request.
Can I request support for a specific platform?
Yes. Include the platform, relevant version, permissions, supporting components, and a minimal authorized reproduction. Platform behavior may still vary by configuration.
Should a request include a complete packet capture?
No. Summarize the relevant observation and remove private network data. A request should not contain credentials, internal addresses, or confidential captures.
How should I describe a command problem?
Provide the command category, intended result, observed result, environment, and any safe test conditions. Avoid copying secrets or production identifiers.
Are all requests implemented?
No. Requests are considered against clarity, technical evidence, safety, maintenance cost, and usefulness to the wider reference.
Where can I send a request?
Use the contact page or the editorial mailbox. Include the relevant Tping page and a concise technical summary.
Have a precise improvement?
Send a focused request with safe, reproducible context. The strongest submissions help future readers solve the same problem.