Images can make a packet diagram, terminal result, or platform note easier to understand. This guide explains how to prepare useful media for Tping while keeping permissions, metadata, accessibility, and sensitive network details in view.
$ review-image --page "tcp-notes data: diagram.png alt: present scope: non-sensitive license: documented status: ready for review [note ] crop private hostnames [note ] include source details result useful, attributable media
Before uploading
A strong image supports a specific technical point. Prefer clear diagrams, carefully redacted captures, and platform illustrations over decorative media that adds visual weight without evidence.
Useful media is legible at documentation width and directly connected to the surrounding text.
Before submitting, check the image as carefully as you would check a command example.
Submission workflow
A consistent process keeps the archive understandable and reduces the chance that an image carries hidden operational or licensing risk.
Crop or redact credentials, addresses, hostnames, private diagrams, and anything not required to explain the technical point.
Choose a descriptive filename and concise alternative text. State what the image shows, not just what file type it is.
Record the source or license, link the image to the relevant page, and explain where it belongs before requesting review.
Practical specification
Use this checklist in the edit notes accompanying an image. It gives reviewers enough context to evaluate the contribution without requiring sensitive material.
Choose a common, lossless format for diagrams and a suitably compressed format for screenshots or photographs. Avoid oversized files and text that becomes unreadable when embedded.
Send the page context, a rights note, and a safe preview. Do not email private captures or confidential network information.