Skip the doc, the wiki, and the email thread. Drop your notes into a Markdown paste and send a link your team can open in any browser.
Open textdrop.sh, switch the format to Markdown, paste your notes (use the template below), pick an expiry, hit Share. Drop the link in the channel.
# Weekly sync, {date}
**Attendees:** Alex, Priya, Tom, Jordan
**Facilitator:** Priya
## Agenda
1. Last week's action items
2. Roadmap check-in
3. Blockers
4. Open floor
## Decisions
- Ship the search rewrite behind a flag this Friday.
- Defer the billing migration until after the Q3 review.
## Action items
- [ ] @alex: draft the launch comms
- [ ] @jordan: file the migration risk doc
- [ ] @tom: update the dashboard with new metrics
- [x] @priya: book the retro room
## Notes
> The new onboarding flow is testing 14% better on activation.
> We need to talk about the on-call rotation next week.
Paste the template above (or your own notes), then hit Share.
Most meeting notes don't need to live forever, they need to be read this week. A doc-with-permissions is overkill, and a wall-of-text Slack message gets lost in scrollback by Friday.
A Markdown paste is the lightest possible delivery: nothing to install, nothing to sign into, renders instantly, expires when it stops being useful. If something from the meeting matters long-term, that's when it earns a spot in the wiki.
Both work, but they require the reader to have an account, accept a share invite, and load a heavy app. A textdrop.sh link is a public URL anyone can open in any browser. No signup, no app, no permissions dance.
Set an expiry when you create the paste. After it lapses, the paste is deleted automatically. Useful for retros, 1:1 notes, or anything you don't want indexed forever.
Yes. Headings, lists, checkboxes, code blocks, blockquotes, links, tables. The rendered view is server-rendered, so it loads instantly with no JavaScript bloat.
Add a password. The notes get end-to-end encrypted. The password never reaches our server, so even we can't read the contents.
No. Pastes are immutable once created. If you need to update, paste a new version and share the new link. This is intentional, it stops collaborative-editing chaos.
You shouldn't share SSH private keys, but sometimes you have to. Here is how to do it without leaving a copy in chat, email, or a co-worker's Downloads folder.
AES-256-GCM, PBKDF2 key wrapping, and what zero-knowledge actually means here.