Frequently Asked Questions
Straight answers about JavaEye: what it covers, how the content is made and corrected, how to reach the person behind it, and how to cite or republish it. If your question is not here, the contact page explains what to include so you get a useful reply.
What this site covers
What is JavaEye?
JavaEye is the personal blog of Nan Liang, an independent developer who builds and operates a fleet of small free web tools, each hosted on Cloudflare and run without signups or paywalls.
Who runs JavaEye?
One person: Nan Liang. Every tool, post, and page on this site is designed, built, shipped, and maintained by the same person, and the support inbox reaches him directly.
What topics does the blog cover?
Four pillars: build logs of real projects, product notes on what shipped and why, operations and growth experiments run on the author's own sites, and transparency reports with real numbers.
Where can I find the tools themselves?
The tools page lists the whole fleet with a one-line description of each tool and a direct link, so you can jump from a build log straight to the working product it describes. See the tools page.
Is JavaEye a company or a team?
No. It is a one-person operation. There is no company behind it, no investors, and no team, which is why the build log can be unusually specific about what works and what breaks.
How the content is made
Who writes the posts on JavaEye?
Nan Liang writes every post from firsthand material — notes taken while actually building and operating the tool fleet, not aggregated summaries of other people's articles.
Are the numbers in the posts real?
Yes. Traffic, indexing, and quota figures come from the author's own operations, and the measured-data pages state exactly how each number was counted so it can be rechecked.
How is AI used on this site?
AI assists only with translation and grammar checking of material the author wrote. It never picks topics, invents facts, or writes content, and the full two-sentence disclosure lives on the editorial policy page. See the editorial policy.
How often is the blog updated?
The cadence is one long-form post per week, with a second post in some weeks. Pages are updated when underlying facts change, and a date moves only when content materially changes.
What happens when a post turns out to be wrong?
Confirmed errors are fixed promptly and noted on the page. If a correction changes a conclusion rather than a typo, the post says so explicitly instead of silently editing.
Contact and feedback
How do I report a bug in one of the tools?
Email support@javaeye.dev with the page URL, what you did, what you expected, and what actually happened. Reports that unambiguously describe a real bug get fixed rather than debated. See the contact page.
How long does a reply take?
Every message is read, and replies typically arrive within a few days, often faster. During heavy build weeks it can take a little longer, but nothing is filtered by a bot.
Can I suggest a new tool or a feature?
Yes — the same inbox takes tool ideas, and suggestions that describe a real, recurring problem are the most likely to get built, because every existing tool started exactly that way.
Does JavaEye accept guest posts or sponsorships?
No. Guest posts, link inserts, sponsored content, and partnership pitches are not accepted and will not receive a reply, which is how the blog stays firsthand.
Citing and republishing
Can I quote or cite a JavaEye post?
Yes, with attribution: name the author, Nan Liang, link back to the original URL, and keep the quote in context. Short quotes with a source link are always fine.
Can I republish a post in full on my own site?
No full republication, please. Quote a short excerpt with a link instead — this keeps the canonical version in one place and the numbers attached to their methodology.
Is there an RSS feed?
Yes — the feed carries every post, and the footer of every page links to it, so you can follow the build log in any reader. See the RSS feed.