# Linux.do Application Rules & Signals

Comprehensive rule set for crafting high-pass-rate Linux.do registration applications.
Sources: official announcements, FAQ, and public community experience posts.

## Hard Rules (Official — Pass/Fail)

### 1. Read FAQ/Guidelines First
Applicants must read the FAQ before registering. The registration page requires checking "已读".
Reviewers specifically flag applications that show the applicant didn't read the rules.

### 2. Self-Written Application
The application must be a ~50-character self-written text covering your background and why you want to join.
"Randomly filled" or "AI-generated" applications will not pass in principle.

### 3. Invited Users Are Also Reviewed
Even with an invitation link, the same application content is required and reviewed by admins.

### 4. Content Is Archived
Application content is not publicly displayed but is archived for future reference.
This means: don't treat it as throwaway text.

## Content Characteristics That Increase Pass Rate

### 1. Specificity > Enthusiasm
Easy-pass applications are concrete: what you tinker with, how you found Linux.do,
which topics you browsed, why you need an account, what you plan to participate in.
Facts + path + scenario = looks like a real person.

### 2. Site-Aligned Motivation
Generic phrases like "want to learn", "want to meet experts", "want to grow together"
carry zero information. Users report failing twice before rewriting with specific
site-related reasons and use cases.

### 3. Show You Know What the Site Is
If the application reveals you don't know what's discussed on Linux.do, or you treat it
as a generic "resource group / tech group / beginner site", pass rate drops.
This aligns with the official emphasis on "read the intro and rules first".

### 4. "How I'll Participate" Is a Bonus
Common pattern in successful applications: not just "I want to look around" but
"I've encountered similar problems", "I've seen solutions on the site",
"I want to reply, document, discuss X topic". This reads like a long-term user.

## Required Information Blocks (4 Blocks)

Every application should contain these 4 pieces:

| Block | What to Include |
|-------|----------------|
| **Real Background** | What you do, what fields you follow. Doesn't need to be complete. |
| **Discovery Path** | How you found Linux.do — search, friend, specific post, long-time lurker. |
| **Why Register Now** | Not abstract "want to join" but concrete: participate in X, reply to Y, follow Z. |
| **Account Usage Plan** | Read-only? Occasional replies? Follow specific topics? Be real and specific. |

## High-Risk Patterns (Likely Rejection)

| Pattern | Why It Fails |
|---------|-------------|
| No background/experience mentioned | Missing required info block |
| No explanation of how you found the site | Looks random |
| No reason for joining | Missing required info block |
| All fluff, no concrete facts | Template-like |
| Overly neat, uniform tone | Looks batch-generated |
| Clearly didn't read rules | Explicitly flagged by reviewers |

## Medium-Risk Patterns (Weak Signal)

| Pattern | Why It's Weak |
|---------|--------------|
| Only admiration/thanks/praise | Zero information density |
| Only listing your skills/contributions | Missing motivation |
| Only learning intent, no use case | Too vague |
| Barely over 50 chars, extremely low info density | Looks like minimum effort |

## Bonus Signals (Increase Pass Rate)

| Signal | Why It Helps |
|--------|-------------|
| Can describe how you encountered site content | Proves real exposure |
| Mentions real topics or participation plans | Shows genuine interest |
| Shows awareness of community rules and positioning | Aligned with official requirement |
| Natural, non-template expression | Passes the "human" smell test |

## Target Specs

- Length: 80-150 Chinese characters (sweet spot: enough detail, not rambling)
- Tone: casual, natural, like telling a friend why you signed up
- Language: Chinese (Simplified)
- Format: plain text, no markdown, no formatting