How we write — and what we refuse to.
Total honesty is the value Xseth is built on, in the product and on this blog. These are the rules we hold ourselves to when we publish. If we ever break one, hold us to it — the contact is at the bottom.
Observed, inferred, confirmed — never blurred
We say what we saw, then say what we concluded from it, and keep the two visibly apart. An open port is an observation; "the service is misconfigured" is an inference until a probe proves it. We label the difference every time.
No unproven claim wears a confident title
We do not write "Anonymous FTP enabled" or "Open DNS resolver" unless a non-destructive check actually confirmed it. Reachability is not exploitability, and we never imply we broke in when we did not.
Today and the roadmap stay separate
What ships today, what is already built, and what we are working toward are three different claims. We fence the future as the future and never sell it as the present.
No invented numbers
We do not publish benchmarks, accuracy figures, or customer counts we cannot stand behind. If we have not earned a number, we will not print one.
We correct in the open
When we get something wrong, we fix the post and say what changed. A correction in daylight is worth more than a quiet edit.