Show HN — the security model, not the product #103

New issue

Closed

opened 2026-09-23 10:46:22 +01:00 by cruelacid · 1 comment

cruelacid commented

2026-09-23 10:46:22 +01:00

Owner

Why

One shot, and it is the best single opportunity this product has for reaching the
people who can evaluate its central claim.

What to do

Write it now, post it after the launch gates close.

Lead with the security model, not the product. "Another Obsidian plugin" is
not a story; "a collaborative editor where the relay holds ciphertext it has no
key for, and here is the reproducible build that proves the client you are
running is the source you read" is.

Link /security and the verification path. Be present in the thread for the
whole day — the comments are the point, and a security audience will probe.

Constraints

Do not post before the gates close. DRAFT terms and an unproven payment
path are the first things this audience checks, and the thread is unrepeatable.
Never "open source". This will be asked directly and the honest answer is
strong: the plugin is source-available under PolyForm Shield 1.0.0 so it stays
checkable without being free to resell, and the server is proprietary because
it holds the commercial value and relays only ciphertext.
Do not claim to be more open than Relay. We are not — their plugin and
server are MIT. Never compete on licence terms.
Never "audited" — designed to be audited. Never "zero knowledge". Never "we
store no metadata".
Expect "what can the server see?" and answer it completely: the membership
graph, account and device records, sizes, timings, IPs.
No claim of users, customers or revenue.

## Why One shot, and it is the best single opportunity this product has for reaching the people who can evaluate its central claim. ## What to do Write it now, post it after the launch gates close. **Lead with the security model, not the product.** "Another Obsidian plugin" is not a story; "a collaborative editor where the relay holds ciphertext it has no key for, and here is the reproducible build that proves the client you are running is the source you read" is. Link `/security` and the verification path. Be present in the thread for the whole day — the comments are the point, and a security audience will probe. ## Constraints - **Do not post before the gates close.** DRAFT terms and an unproven payment path are the first things this audience checks, and the thread is unrepeatable. - Never "open source". This will be asked directly and the honest answer is strong: the plugin is source-available under PolyForm Shield 1.0.0 so it stays checkable without being free to resell, and the server is proprietary because it holds the commercial value and relays only ciphertext. - **Do not claim to be more open than Relay.** We are not — their plugin *and* server are MIT. Never compete on licence terms. - Never "audited" — *designed to be audited*. Never "zero knowledge". Never "we store no metadata". - Expect "what can the server see?" and answer it completely: the membership graph, account and device records, sizes, timings, IPs. - No claim of users, customers or revenue.

cruelacid added this to the Backlog - unscheduled milestone

2026-09-23 10:46:22 +01:00

cruelacid added the

marketing

channel:press

gate:at-ga

labels

2026-09-23 10:46:22 +01:00

cruelacid referenced this issue

2026-09-23 10:46:56 +01:00

Go-to-market programme #110

cruelacid added this to the Marketing project