Stock Scalping Community

Journal timestamps, screenshot filenames, and "I entered at the breakout" arguments all collapse if your clock drifts.

I once spent twenty minutes arguing with myself about a fill that "couldn't be right" — two machines, ninety seconds apart, same "09:31." One had drifted after a snapshot restore. Felt stupid. Fixed the process.

Why scalpers care

Aligning tape events to chart prints. Comparing VPS vs home logs. Auditing a bad fill: platform lag vs "I clicked late." Without synced clocks you're debating ghosts.

Windows (practical)

1. Time zone: trade US RTH → run Eastern, or keep local but label every log with ET. Pick one and stop mixing.
2. Automatic time sync on.
3. Stubborn drift: admin prompt → `w32tm /resync`, then `w32tm /query /status`.

Linux
VPS rule

After every rebuild or snapshot restore: verify sync before the open. Snapshot restore loves to hand you a stale clock and a false sense of security.

Logging convention for this board

Write times as `HH:MM:SS ET`. If it matters, note the machine (`HOME` / `VPS-NJ`). If two machines disagree by more than a second, fix sync before you debate entries.

Sticky this until people stop posting screenshots with phone time and chart time living in different universes.

What do you run for sync on Windows — default, chrony elsewhere, or something else?
Anyone caught a snapshot restore with a bad clock before the open?
How do you label multi-machine journals so HOME vs VPS doesn't get muddy?
Phone screenshot times — do you trust them at all, or always defer to the chart machine?

On **NTP Clock Sync — Stop Trusting Your Laptop Clock**, the desk standard stays practical. Stop trusting your laptop clock for anything that touches order timestamps, journal TOD tags, or latency notes. NTP sync is boring infrastructure — which is exactly why scalp desks skip it until a dispute or a mis-tagged review wastes an evening.

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

Infrastructure is risk management. ISP, VPS, NTP, flatten hotkeys, and update quarantine only count when drilled and dated.

## Rails that stay on the sheet
- Stop trusting laptop clock for orders/journals.
- Drift corrupts reviews and latency notes.
- Invalidation written in cents or an auditable structure break before entry.

## Why clock drift matters on a stock desk
- Journal time-of-day expectancy becomes garbage if tags are shifted by minutes.
- Latency bake-offs are meaningless when the measurement host is wrong.
- Cross-checking broker fill times vs local logs turns into an argument with your own machine.
- Replay review aligned to "09:30 ET" is wrong if the box thinks it is 09:32.

## Worked example — Journal TOD tags drift
Laptop clock off 3 minutes; TOD buckets mis-tag open vs mid. Latency notes useless. NTP sync on VPS and desktop; verify before RTH; refuse to trust GUI clock alone.

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 **NTP Clock Sync — Stop Trusting Your Laptop Clock** and substituting confidence.
- Adding size after adverse selection because the story still feels right.
- Paying open microstructure tax that midday memory never modeled.

## 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 **NTP Clock Sync — Stop Trusting Your Laptop Clock**, 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.