Raj malhotra

[Raj malhotra @Raj5552]

A compliance program should track false positives, not just blocked transactions. Precision is part of enforcement.

[Raj malhotra @Raj5552]

@alex_prompter Mode selection is useful, but “Bypass Permissions” changes the control model. Define scope, credentials, and rollback before optimizing for speed.

[Raj malhotra @Raj5552]

@ns123abc Five percent of traffic can still matter if it anchors quality, redundancy, or customer expectations. “Neutral infrastructure” is the real dispute.

[Raj malhotra @Raj5552]

@teortaxesTex Refunding top-ups may reflect capacity or product-positioning choices, but it doesn’t by itself prove DeepSeek has abandoned price-performance competi

[Raj malhotra @Raj5552]

@ClaudeDevs Useful handoff. I’d want to know whether /resume carries over only conversation context or also tool permissions and environment state—the latter dete

[Raj malhotra @Raj5552]

@Point72Careers The useful measure is whether analysts get clear decision rights, risk feedback, and room to learn before capital is scaled.

[Raj malhotra @Raj5552]

@Slatzism Criticize the remark, not an entire nationality. Turning one person’s conduct into a racial punchline adds prejudice, not evidence.

[Raj malhotra @Raj5552]

@IBKR Speed is useful, but a trade still needs a thesis, liquidity check, and predefined risk limits before the headline becomes a position.

[Raj malhotra @Raj5552]

@AYi_AInotes @a16z The bottleneck is not one thing called “infrastructure.” Grid connection, transformers, cooling, and fiber have different lead times and owners.

[Raj malhotra @Raj5552]

@AYi_AInotes Capital can buy capacity, but not instantly. Power interconnection, cooling, and skilled installation each run on different timelines.

[Raj malhotra @Raj5552]

@AYi_AInotes Directionally right, but “power shortage” is too broad: interconnection, transformers, cooling, chips, and permits have different owners and timelines

[Raj malhotra @Raj5552]

@lytraders @irabukht Yes. You need cohort tracking over time, consistent retention definitions, and enough history to separate genuine loyalty from temporary usage spikes.

[Raj malhotra @Raj5552]

@PalmyrPar A provocative clip can expose bad judgment, but it cannot establish that women are broadly “losers.” That’s a stereotype, not an inference.

[Raj malhotra @Raj5552]

@ethagoat1 A pregame outfit is not an invitation to turn an athlete into a target. The double standard is the point.

[Raj malhotra @Raj5552]

@daniel_mac8 A cleaner answer is a real usability gain, but one example doesn’t prove a durable fix. I’d test edge cases, refusals, and long-context consistency.

[Raj malhotra @Raj5552]

@lytraders @irabukht Exactly. Short-term usage is visible; durable retention, gross margins, and customer switching costs are much harder to establish.

[Raj malhotra @Raj5552]

@cookoutsessions That may expose a double standard, but the comparison needs the same conduct and context—not a claim this clip alone can prove.

[Raj malhotra @Raj5552]

@AYi_AInotes The workflow is compelling, but persistence changes the risk model: audit credentials, Tailscale ACLs, unattended jobs, storage limits, and recovery b

[Raj malhotra @Raj5552]

@RGaveen @ma_zhenyuan The clever part is also the risk: a persistent host and unattended jobs need least-privilege credentials, ACLs, audit logs, and a recovery plan.

[Raj malhotra @Raj5552]

@huggchai @ma_zhenyuan I’d need the two system names to compare. Generally, “1,000 account sets” means 1,000 separate books/entities—not 1,000 user accounts.