Contact Us
Updated: September 7, 2026 · 中文
Contact email
Email [email protected] for editorial feedback, project suggestions, service inquiries, order support, partnerships, and privacy requests. We welcome messages in Chinese or English.
Use a descriptive subject such as “Correction | Article title,” “Deployment inquiry | Project name,” or “Order support | Order number.” We handle messages according to their nature and current workload. This is not a live-chat or round-the-clock emergency operations channel. Response arrangements for purchased services depend on the agreed order.
Corrections and project suggestions
For errors, broken links, outdated commands, licensing changes, or security concerns, include:
- The page URL, affected passage, and the change you believe is needed.
- Official documentation, an upstream issue, release notes, or other verifiable evidence.
- Software and operating system versions and redacted error details where reproduction is relevant.
For project suggestions, provide the official repository or website, license, main use case, audience, deployment requirements, and your relationship to the project. Suggestions do not guarantee inclusion or ranking. Please identify requests for paid placement as sponsorship inquiries.
Deployment and technical services
Describe the project, intended outcome, whether you already have a server and domain, your operating system and resources, migration needs, budget, and preferred timing. These details help establish feasibility, access requirements, deliverables, and maintenance responsibilities.
Do not attach server passwords, SSH private keys, API secrets, complete databases, or customer information to an initial inquiry. If remote access is necessary, agree on the work and a secure handover method before providing temporary access with minimum necessary permissions. For migrations, explain available backups and acceptable downtime.
Orders, payment, and support
Include your straw-dog order number, purchase, payment time, issue description, and a redacted payment receipt if relevant. If payment succeeded but the order page has not updated, ask us to investigate before making repeated payments.
For cancellation, refunds, delivery issues, or scope disputes, describe the resolution you seek. Handling depends on the order, work actually delivered, and applicable consumer rights, as explained in the Terms of Service. Do not send payment passwords, full card numbers, or banking verification codes.
Partnerships and sponsorship
We welcome relevant inquiries involving open source, self-hosting, developer tools, cloud services, and AI automation, including sponsored listings, promotional placements, Chinese-language tutorials, and content production. Include product links, the intended audience, format, budget range, timing, and disclosure expectations.
Paid relationships must be identified. We do not accept requests for invented tests, concealed risks, fabricated user reviews, or undisclosed promotion. Partners may verify factual descriptions of their products without controlling editorial conclusions.
Privacy, accounts, and intellectual property
Use “Privacy request” when seeking access, correction, deletion, account closure, or removal of a subscription registration. Where possible, write from your verified account email and describe the scope. Do not send passwords, verification codes, or a complete identity-document image. See our Privacy Policy.
For copyright, trademark, or other rights complaints, provide specific URLs, evidence of ownership or authority, the grounds for the complaint, and a reply address. After reviewing the information, we may correct content, add attribution, temporarily limit display, or remove material as appropriate. A complaint alone does not establish infringement.
Security reports
Use “Security report” for vulnerabilities, exposed data, or suspicious account activity. Include the affected URL, time, minimum necessary reproduction steps, and redacted evidence. Do not expand access, read other users' data, perform destructive actions, or publish active credentials. This contact channel does not authorize penetration testing of production systems or promise a bounty.
Related pages: About Us · Editorial Policy