Most developers have done this at least once:
- Sent a password over Slack
- Shared credentials in email
- Copied secrets into a notes app and forgot about them
It works — until it doesn’t.
That’s where the idea for 1Note came from. It is a simple tool:
Share a secret → view it once → it disappears
What is 1Note?
1Note is a secure, ephemeral note-sharing tool designed for both quick use and developer workflows. You create a note, get a link, share it — and:
- It can expire after one view
- It can have a view limit
- It can expire after time
- It can be password-protected
No accounts. No friction.
The Problem I Wanted to Solve
We all share sensitive data in unsafe ways:
- API keys
- Database passwords
- Tokens
- Temporary credentials
Most tools don’t enforce ephemeral access. Once shared, the data lives forever. That’s the real problem.
Core Idea
Make secrets temporary by default instead of permanent unless deleted. That single shift changes how you think about sharing data.
How It Works (High Level)
-
Create Note
- User sends content
- Backend stores it securely
- Returns a unique link
-
Access Note
- User opens link
- System validates: Not expired, Not deleted, Within view limits
-
Consumption
- View count increments atomically
- If limit reached → note is destroyed
Security Model
1Note uses:
- HTTPS (encryption in transit)
- Encryption at rest (server-side)
- Optional password protection
- Rate limiting
[!IMPORTANT]
The current version uses server-side encryption, not zero-knowledge encryption. This was a conscious tradeoff to keep the system simple and usable.
The Hardest Part: Concurrency
One of the most interesting challenges was: How do you ensure a note is only consumed once?
Imagine two users opening the same link at the same time. To solve this, we use an atomic database operation:
sql
UPDATE SecureNote
SET viewCount = viewCount + 1
WHERE slug = $slug
AND (maxViews IS NULL OR viewCount < maxViews)
AND isDeleted = false
AND (expiresAt IS NULL OR expiresAt > now())
RETURNING *
Top comments (0)