n/vps Node Community Rules and Tag Usage Guide

Internet services VPS
,
1

n/vps Node Community Rules and Tag Usage Guide

Effective date: September 8, 2026
Scope: All topics and replies under the n/vps node

Welcome to n/vps. This node is dedicated to building NodeLoc’s most technically in-depth VPS discussion community, focusing on cloud server selection, performance testing, network route analysis, system deployment, and hands-on operations and maintenance. To maintain a positive discussion environment and improve information retrieval efficiency, all members are asked to carefully read and follow the following community rules and tagging guidelines.

️ I. Red Lines and Prohibitions (Violations Will Result in Deletion or Mute)

The following behavior will incur severe penalties, including post deletion, muting, or permanent bans, depending on the severity:

  1. Meaningless spam posts are prohibited
    • Definition: Posts with empty content and no substantive discussion value.
    • Typical examples: Asking only for a provider’s purchase link without any other content (such as “Where can I buy the RackNerd special?”), clickbait titles, repeatedly asking questions that can be answered through search engines or the forum, and bumping posts with only emojis or symbols.
  2. Malicious provocation and personal attacks are prohibited
    • Insults, mockery, or personal attacks against providers or other users are strictly prohibited.
    • Spreading unfounded negative claims about specific providers or provoking regional/network-route conflicts is strictly prohibited (for example, “Provider XX is all garbage” without supporting data).
    • Rational discussion based on test data is encouraged instead of emotional venting.
  3. Improper promotion and traffic diversion are prohibited
    • Posting pure Affiliate promotional links (AFF links) as the primary content is strictly prohibited.
    • Advertising, gambling, illicit-industry, or other traffic-diversion content unrelated to VPS is strictly prohibited.
    • Official accounts of verified providers posting their own test results must use the [Verified] tag and include substantive configuration details.
  4. Plagiarism and content laundering are prohibited
    • Reposted reviews or tutorials must cite the source and author.
    • Directly reposting or rewriting content from other sources while passing it off as original is strictly prohibited.

️ II. Tagging Policy

To help everyone find content more efficiently and prevent misleading tags, please strictly follow the tagging rules below when posting. Incorrect tag usage may result in a post being moved or deleted.

1. Core Category Tags (Choose One)

Each post must select one primary category tag according to its content:

Tag Applicable scenarios Notes
Review Posts containing real-world test data such as benchmark results, streaming-service unlocking, or route tracing Purely subjective “hands-on” reviews are discouraged; UnixBench/Geekbench screenshots are encouraged
Tutorial Posts sharing deployment scripts, environment setup, software configuration, and other operating procedures Steps should be clear and code blocks properly formatted
Help Posts seeking assistance with technical problems Search first and clearly describe the error message
Deals Posts sharing provider promotions, discount codes, or special-price servers Include configuration details; link-only begging is prohibited
Chat Industry discussions and experience sharing without a specific technical topic Remain friendly; provoking conflicts is prohibited
Announcement Official notices posted only by administrators Regular users are strictly prohibited from using this tag
Group Buy Posts involving shared hosting or pooled machine resources High-risk activity; exercise caution and accept responsibility for the consequences

2. Technical/Topic Tags (Add as Needed)

When a post concerns a specific technical field, add the following tags for more precise searches:

  • Route Discussion: Discussions of the routing and quality of specific routes such as CN2 GIA, CU9929, 4837, and CMI.
  • Virtualization: Differences between technologies and architectures such as KVM, LXC, OpenVZ, and Docker.
  • Basic Operations: Everyday tasks such as common Linux commands, BaoTa Panel, and Nginx/Apache configuration.
  • Troubleshooting: Records of troubleshooting processes involving server outages, connection failures, error-log analysis, and so on.
  • Security Hardening: Firewall settings, SSH optimization, anti-attack strategies, WAF configuration, and so on.
  • Pitfalls: Negative experiences such as providers disappearing, severe overselling, or poor after-sales service (must be supported by facts; pure emotional venting is prohibited).
  • Chinese Cloud Provider Digest: A discussion area specifically for small and medium-sized Chinese providers and individual cloud hosts.

3. Provider-Specific Tags (Precise Matching)

Do not misuse provider tags to chase popularity. A corresponding tag may be used only when the post is primarily about that provider:

  • Major International Providers: aws digitalocean linode hetzner oracle
  • Popular/High-Value Providers: racknerd colocrossing cloudcone netcup digitalvirt
  • Other Common Providers: dedirock desivps justhost digitalcloud digitalgleam raksmart akile 搬瓦工

III. Posting and Content Standards

To help everyone obtain information more efficiently, please follow these posting standards:

  1. “Let the data speak”
    • When publishing a review-style topic, please include UnixBench/Geekbench benchmark results, iperf3 speed-test results, MTR route graphs, or streaming-service unlocking test screenshots whenever possible (preferably test results from NodeLoc’s one-click script).
    • Purely subjective “hands-on” reviews are discouraged; long-term stability reports are encouraged.
  2. Ask questions properly
    • When publishing a [Help] post, clearly describe your use case (website hosting/proxy/benchmarking), budget, target region, and network requirements (such as a mandatory CN2 GIA connection).
    • Use the search function before asking questions to avoid duplicates.
  3. Focus on technical depth
    • Sharing advanced operations and maintenance experience involving Docker orchestration, Shell scripts, network optimization (BBR/锐速), security hardening, and other topics is encouraged.
    • Moderators will award additional points or pin high-quality tutorials and script-sharing posts.

IV. Quality Content Incentive Program

To encourage original, high-quality content, this node operates a long-term incentive program:

  1. Pinned display: High-quality topics may be pinned for 7–14 days, giving more members the opportunity to see your contribution.
  2. Energy rewards: Each month, the “Best Technical Post of the Month” (Top 1) will be selected, with the node owner personally providing 500–1000 Energy or an even better prize.
    • Reference criteria: Technical depth (30%) + data thoroughness (25%) + practical value (15%) + bonus points; result × 70% + community voting.

️ V. Violation Handling Process

  1. First violation: Delete the violating content and issue a warning via private message or reply.
  2. Repeated violations: Depending on the severity, impose a 1-day / 7-day / 30-day mute or account suspension.
  3. Serious violations: Malicious attacks, illegal information, or repeated offenses despite warnings will result in a direct permanent ban.

Special note:
The final right of interpretation of these community rules belongs to the n/vps node moderators and the NodeLoc management team. If you have objections or better suggestions regarding the rules, you are welcome to post under the [Moderation] tag for discussion. We will continue improving the community environment.

Let’s work together to make n/vps the most valuable VPS technology community!

3 Likes
2

The new badge is too conspicuous.

1 Like