King

MiniMax-M2.7 woww

It is crazy to me that in this day and age you can create enterprise value just by having impeccable tastes in design and implementation and having the ability to articulate these tastes. Implementation risk is now a function of eloquence.

Want to see if people are panic selling Dubai real estate? I built a site that tracks every price drop across 16,000+ luxury listings in real-time. ➡️ panicselling.xyz

It was funny to watch Claude Cowork scroll the Twitter feed up and down and try to figure out how the website works: x.com/moo9000/status… However when the task in the hand can be converted to a repeatable skill and when the skill can be made to rely on APIs (even if automatically reverse engineered by LLM), then it works much better.

GPT-5.2 > Opus-4.5 > GPT-5.1 > Sonnet-4.5 > GLM-4.7 > Kimi-2.5 GPT-5.2 is the best as main brain of @openclaw since that model can fix code right away, without needing to call another coding agent. Opus make many "quick win" mistakes when working alone. Usually it needs to pair with Sonnet (for context exploring) and another Opus (For code review + audit) as a coding team.

I’m looking for a crypto card. Which one is the best one?

@LucaNetz It’s between Coinbase ans Gemini - Coinbase rewards you more for holding more funds on their platform. Gemini rewards more for gas/dining purchases.

@LucaNetz Personally I’ve tried @ether_fi and @KASTxyz, both are great. Also heard @AviciMoney is good but I can’t register one 🥲

So you can clone any voice 100% locally using this new open source model?! Alibaba has released Qwen3-TTS on Hugging Face. You can easily: - Create custom voices - Clone any voice from a VERY short audio - Generate speech with style instructions Only 0.6B & 1.8B! Sound on🔊

Remotion now has Agent Skills - make videos just with Claude Code! $ npx skills add remotion-dev/skills This animation was created just by prompting 👇

@Wajahat Pretty cool stuff!

@king_man5548 Just used Claude code via my terminal

First time using Claude to make a video - Using remotion, simple but clear prompts and screenshots is all you need with scene by scene edits - Rendering was quick, 30 seconds tops - Just add any logos, designs, screenshots, music files and it'll put it together Just the first time I used it, think on the 50th time, these can eventually be some pretty high quality videos

@nns_w3 @Cbb0fe Access code?

@Cbb0fe have you tried Tria ser? with their premium card you have 6% cash-back and 0 fees, and also every 1$ spent means 1 XP TGE is set for this year, so might worth it

Etherfi is the best product I ever used in crypto and this is not even close I used to have anxiety when having to off-ramp crypto Etherfi makes my stables accessible at a fingerprint Yesterday it took 6 hours only to off-ramp USDC from Etherfi to IBKR Big W (no I'm not paid)

@safetyth1rd Which model is the best now?

Claude won not becuase it has the best coding skills It doesn’t anymore But its the best to use: You code with it like you talk to a human, not a machine.

@bcherny Is it better than Opus 4.5?

Introducing Sonnet 3.7 and Claude Code, Anthropic’s new agentic coding assistant. The team and I have been hacking on Code for a while — can’t wait to hear what everyone thinks. anthropic.com/news/claude-3-…

got a DM from a guy who said he made $1.2M trading last year looked at his profile. 847 followers. no course. no discord. posts maybe twice a week. thought it was cap asked him to prove it he sent broker statements. verified. real. so I asked him one question: "what's your strategy?" his answer changed how I think about trading forever. "I trade one pattern. literally one. for 9 years." "just one?" "just one. bullish engulfing at daily support. that's it." "you made $1.2M from bullish engulfings?" "I made $1.2M from being the most patient motherfucker on planet earth." he explained: when he started, he was like everyone else. 47 indicators. 12 strategies. telegram signals. news trading. scalping. swing. everything. blew $340k in 4 years. his wife told him he was done. trading was over. get a real job. "that's when I got serious." he spent 6 months backtesting ONE setup. bullish engulfing at daily support. over 3 years of data. (i don't even know how the fuck support/resistance work lmao) found it hit 61% of the time with average 2.8R when traded correctly. "that was enough. I didn't need anything else." now he wakes up. checks daily charts for 15 minutes. if the setup is there, he takes it. if not, he plays golf. "some weeks I take zero trades." "doesn't that drive you crazy?" "it drove me crazy for the first 6 months. now I don't even think about it. no setup = no trade. the market owes me nothing." I asked about his typical month: - trades: 8-12 - winners: 5-7 - losers: 3-5 - average month: $70-120k "you make six figures taking 10 trades a month?" "bro most months I make more than I made the entire year when I was taking 10 trades a day." this broke something in my brain. we've been told MORE effort = MORE results but trading is inverted LESS effort = MORE results because effort in trading usually means: - more trades (more mistakes) - more screen time (more emotional decisions) - more analysis (more paralysis) - more indicators (more confusion) he told me his screen time went from 8 hours per day to 45 minutes per week. his income went from -$80k/year to +$1.2M/year. inverse correlation I asked for his advice to new traders: "pick one setup. test it. prove it works. then do ONLY that setup for 3 years. you'll be rich and everyone will think you're a genius. you're not. you're just patient." before I ended the call: "one more thing. everyone who tells you trading is hard is right. but not because the market is hard. because DOING NOTHING is hard. that's the actual skill. doing nothing while everyone else is busy losing money." he hung up. probably went to go do nothing.

You don’t know it but gpt5.2-xhigh is better than opus 4.5 The problem is that it’s too slow for most folks But if you plan with gpt5.2-xhigh and then execute with opus 4.5 you’ll have the best output

what are the exact steps to clone any SaaS? most people overcomplicate this. here's the exact playbook I'd use with Claude Opus 4.5 + Factory AI to reverse engineer and rebuild any SaaS in weeks, not months: step 1: deep product archaeology before writing a single line of code, you need to understand what you're cloning at a forensic level. - sign up for the target SaaS (free trial, paid, whatever) - screen record yourself using every single feature - document every UI state, error message, edge case - export any data they let you export (reveals data models) - check their docs, API references, changelog feed all of this into Claude Opus 4.5. upload screenshots, paste documentation, describe workflows. ask it to reverse engineer the likely database schema, identify core entities, map user flows. step 2: technical reconnaissance - check their job postings (reveals tech stack) - Wappalyzer / BuiltWith for frontend frameworks - check network tab for API structure and naming conventions - look at their public GitHub if they have one - read their engineering blog posts paste all findings into Claude. ask: "based on this evidence, what's the likely architecture? what are they probably using for auth, payments, background jobs, file storage?" step 3: scope ruthlessly this is where most people fail. they try to clone 100% of features. use Claude to categorize every feature you documented into: core (MVP): the 3-5 features that deliver 80% of the value important: nice to have, build in month 2-3 bloat: features you'll never build (or build last) be honest. most SaaS products have years of feature creep. you're building the lean version that solves the same core problem. step 4: architecture design with Claude now you prompt Claude Opus 4.5 with everything you've gathered: "I'm building a clone of [X]. here's what I know about their product: [paste everything]. here's my MVP scope: [paste features]. design me a complete technical architecture including: - database schema with all tables and relationships - API endpoint structure - auth flow - file storage approach - background job requirements - third party integrations needed - suggested tech stack optimized for solo dev speed" Claude will give you a comprehensive architecture doc. iterate on it. ask follow-up questions. poke holes in it. step 5: Factory AI for accelerated build this is where Factory AI comes in. Factory is built for autonomous software development at scale. set up your repo. connect Factory. feed it the architecture Claude designed. use Factory to: - scaffold the entire project structure - generate database migrations from your schema - build out API endpoints with proper validation - create UI components from your screenshots write tests as you go Factory's agents work continuously. you review PRs, provide feedback, they iterate. step 6: the "screenshot to code" workflow for UI, the fastest path: screenshot every page of the target SaaS feed to Claude: "recreate this UI in React/Next.js + Tailwind. make it pixel-close but don't infringe on their specific brand assets. use placeholder copy." Claude outputs component code Factory agents refine and integrate into your codebase repeat for every screen you can rebuild entire dashboards in hours, not days. step 7: data model validation before going deep on build, validate your data model: - create seed data scripts - simulate real user workflows in your local env - ask Claude: "here's my schema, here are the user workflows. what edge cases am I missing? what will break at scale?" fix issues now, not after you have users. step 8: auth, payments, core infra don't reinvent these. use boring, reliable tools: - auth: Clerk, Supabase Auth, or NextAuth - payments: Stripe (just use Stripe) - email: Resend or Postmark - file storage: S3 / Cloudflare R2 - database: Postgres (Supabase, Neon, or Railway) - hosting: Vercel for frontend, Railway/Render for backend prompt Claude: "generate the complete integration code for [Stripe/Clerk/etc] in my [framework]. include webhook handlers, error handling, and TypeScript types." step 9: rapid iteration cycles your daily workflow: morning: - review Factory AI's overnight PRs - merge what's good, comment on what needs changes - add new tasks to the queue afternoon: - work on complex features manually with Claude as copilot - screen share with Claude (via screenshots) when stuck - let Factory handle the more routine build-out evening: - test the day's work - document bugs and edge cases - queue up tomorrow's Factory tasks step 10: the 80% product in 2-3 weeks if you're disciplined, you'll have a functional clone of the core product in 2-3 weeks. it won't have every feature. it doesn't need to. what you'll have: - working auth and user management - core product functionality (the main 3-5 features) - payments and billing - basic admin/dashboard - deployable to production step 11: differentiate or die here's the truth: a pure clone is a commodity race to the bottom. once you have the base, you need your angle: - price: can you be 50% cheaper? - niche: can you serve one segment 10x better? - speed: can your UX be dramatically faster? - integration: can you plug into a workflow they ignore? - model: can you flip the business model (one-time vs subscription, usage-based, etc)? use Claude to brainstorm differentiation: "I cloned [X]. here's what they do. what are their biggest customer complaints (search Reddit, Twitter, G2 reviews)? where could a competitor win?" step 12: launch and iterate ship to a small group. friends, Twitter followers, a Discord community. get feedback fast. use Claude to: - analyze feedback patterns - prioritize feature requests - draft changelog and marketing copy - debug issues in production the meta-lesson the tools have changed everything. what used to take a funded team 6-12 months, a single operator with Claude Opus 4.5 + Factory AI can do in weeks. but the leverage only works if you: - scope ruthlessly (most important skill) - move fast and iterate - use AI for acceleration, not as a crutch - actually understand what you're building the people who win are the ones who treat AI as a 10x multiplier on their existing skills, not a replacement for thinking. now go clone something and undercut an incumbent.

@shrimalmadhur Using this gave me a nice improvement but still not perfect github.com/anthropics/cla…