SDRstore Community Rules: What Is Allowed?

[Pavel]

Short answer: Use the community for lawful SDR setup, reception, software, antennas, projects, product questions and authorized RF research. Do not post private order data, credentials, protected communications, instructions for interference or activity outside your authorization.

Before you start​

• Use the most specific forum and write a title that names the device, software, signal or exact error.
• Remove order numbers, addresses, phone numbers, tracking numbers, account details, credentials and precise private locations before posting.

Step-by-step method​

1. Step 1: Choose the most specific forum and write one descriptive thread title. Search for the exact device and error first to avoid splitting the same answer.
2. Step 2: For reception and decoding, follow local law and avoid publishing private or protected message content. Discuss signals technically without exposing people.
3. Step 3: For transmit or security research, state authorization and use conducted, attenuated or shielded methods. Jamming, unauthorized access and unsafe open-air tests are not acceptable.
4. Step 4: Redact screenshots, logs and captures before upload. Report problematic posts privately to moderators instead of reposting sensitive content.

Concrete example​

Allowed: troubleshooting a HackRF transmit flowgraph into a dummy load. Not allowed: asking how to disrupt a live service or replay a third party's credential. Allowed: a redacted USB error log. Not allowed: an invoice or tracking label.

How to judge the result​

A compliant thread has a clear technical purpose, enough nonprivate detail to help and no instruction or data that creates avoidable legal, safety or privacy risk.

What to record​

• A useful question lets another member reproduce the problem from the hardware, software version, settings and exact result supplied.
• Mark a verified fix as the solution so future readers can reach it directly.
• Edit the first post when a confirmed correction changes the instructions or compatibility information.

Common mistakes​

• Using a vague title or omitting the details another member needs to reproduce the question, guide or result.
• Posting private information first and expecting it to be removed later; public copies, notifications and downloads may already exist.
• Receiving a signal does not automatically grant permission to decode, publish or reuse its content.

Final check​

Read the post once as a stranger: its forum, title, prefix and evidence should be clear, while personal data, credentials, precise private locations and protected content are absent.