Screenshot Etiquette (So Threads Stay Useful)

[NYC88]

Bad screenshots create bad advice. Then people argue about ghosts.

I've been asked "what would you do?" on a crop with no ticker, no time, no timeframe, and a bag already attached. That's not a review request. That's a hostage situation.

Required on every chart shot

Code: Select all

- Ticker
- Timezone label (ET)
- Timestamp visible
- Timeframe
- What you want reviewed (1–2 sentences)

Nice to have

Entry / invalidation marked. Whether you're already flat. Platform + whether it's replay.

Don't

Crop out the axis times. Post 12 unmarked charts. Ask "what would you do?" with no plan of your own. Hide that you're already bagholding — say it. We can smell it anyway.

Mods: remove or ask for redo. Culture is curated or it becomes noise. Prefer curation.

What's the #1 thing you refuse to review a chart without?
Do you mark invalidation on the image, or only in text?
Replay vs live — do you disclose it when asking for feedback?
Anyone have a template overlay they paste onto every review shot?

[Fairman]

On **Screenshot Etiquette (So Threads Stay Useful)**, the desk standard stays practical. Screenshot etiquette — threads stay useful when images teach. A clean one-minute chart with marked invalidation beats a twelve-monitor wallpaper every time on this board. I treat screenshots as part of the educational product, not as proof that I own hardware.

Replying in-thread with operable constraints — not forum combat. If these rails disagree with your framing, treat it as a checklist offer.

Prep earns rent when it finishes before the bell: A-list, spread notes, news windows, and one sentence for stand-down. Unfinished sheets become open improvisation.

## Prep that survives the bell
A-list discipline means max loss and size are written before 09:30 ET. Catalysts are graded confirmed/rumor/recycled. Index context is on the card. Open-window behavior is constrained on purpose. If prep is incomplete at 09:20, the professional move is observe — not speed-run a fantasy sheet while SPY is already moving.


## When to skip
Skipping is a first-class decision — even when the chart still looks persuasive:
- Checklist incomplete at 09:20 ET — observe or one pre-written A+ only.
- Live spread outside max for that symbol and session bucket.
- Index violently disagrees with a single-name thesis and no reduced-size RS plan is on the sheet.
- Platform, hotkeys, locate, or flatten path unverified after reconnect/update.
- Daily loss, PDT slot, or prop buffer tripwire already touched.
- News/FOMC/CPI window where the size-cut card says stand down.

## Closing
For **Screenshot Etiquette (So Threads Stay Useful)**, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.

Diagram still attached as the visual checklist. Status remains awaiting approval; nothing here is a live post.
Diagram: screenshot etiquette — teach with one annotated idea.

## Worked example — Screenshot without invalidation mark
Posted 1-minute chart with arrows everywhere, no invalidation, no spread note, no TOD. Thread debates art. Useful shot: one timeframe, marked invalidation, entry intent, spread at decision.

I keep examples in cents and clock time so Sunday review can tag the behavior — not rewrite it as a mood.

## Failure modes
- Ignoring the rails above on **Screenshot Etiquette (So Threads Stay Useful)** and substituting confidence.
- Adding size after adverse selection because the story still feels right.
- Paying open microstructure tax that midday memory never modeled.

## Rails that stay on the sheet
- Images teach or they decorate.
- Mark invalidation or do not post as a lesson.
- Invalidation written in cents or an auditable structure break before entry.