When you build something valuable, people will test it, challenge it, and look for weaknesses. Finding a flaw is easy to criticize, but true expertise lies in identifying the problem, understanding its cause, and improving the solution.
China is releasing open-source AI models at an incredible pace.
While the US dominates much of the AI conversation, Chinese companies are proving that cutting-edge AI doesn't have to be closed-source or prohibitively expensive.
If you rob a bank, you’re a criminal
If the bank robs you, it’s finance
If everyone robs each other, it’s crypto
Apple vs Samsung vs Google vs Huawei
If you had to choose just ONE ecosystem to use every day, which would it be — and why?
Starniq retweeted
Paste this into Claude Code.
It builds a 24/7 crypto research agent that watches the market, makes paper trades and logs its reasoning. Free data, no API keys, no real money.
The 3 repos you need:
1. DexPaprika MCP
Gives Claude live DEX data: tokens, pools, trades and price history across 36 chains, incl. Solana. Free tier, no API key.
github.com/coinpaprika/dexpa…
2. CCXT MCP Server
Gives Claude read-only exchange data: prices, candles and volume from Binance, Coinbase, Kraken, Hyperliquid, Bybit, OKX and more.
github.com/Nayshins/mcp-serv…
3. Crypto Claude Desk (optional shortcut)
A ready-made multi-agent trading desk for Claude Code: market monitor, technical analyst, risk manager and portfolio manager. Paper trading only, no API keys.
github.com/hugoguerrap/crypt…
Install 1 and 2 as MCP servers, then paste:
```
Build a crypto research + paper-trading agent in this repo.
Data: use only the dexpaprika and ccxt MCP tools (read-only). No exchange API keys, no wallets, no private keys anywhere in the code.
Loop every 15 minutes:
1. Pull price, volume and 1h/4h candles for a watchlist in watchlist.json
2. Compute trend, momentum and volatility; note liquidity and volume spikes
3. Decide BUY / SELL / HOLD per asset with a written reason
4. Execute PAPER trades only, recorded in a local SQLite ledger
Risk rules (hard):
- Start with $10,000 paper balance
- Max 5% of balance per position, max 3 open positions
- Stop-loss 3%, take-profit 6%, no leverage
- Skip any token with < $500k liquidity
Output:
- A daily markdown report: trades, P&L, win rate, max drawdown, and what the agent got wrong
- Never claim results are predictive. Never place real orders.
```
Run it for 2 weeks before you trust a single number. Paper results aren't live results.
Want it pre-built? Repo 3 does this out of the box.
Not financial advice.
Facebook = fake news
Instagram = fake life
WhatsApp =beggars
YouTube = ads
TikTok = under age kids
Telegram = scammers
Snapchat = prostitution
Twitter = legit and fast news
Starniq retweeted
Almost time! Windows laptops powered by @NVIDIARTXSpark arrive tomorrow.
The innovation is impressive, and a @Tesla , @SpaceX partnership could be the boost the automotive industry needs. But here’s the big question: Will EU regulations allow this innovation to thrive, or will they put the brakes on it?
The future of cars is getting wild.
Elon Musk has officially unveiled Tesla’s next-generation Roadster.
It is set to feature:
— An all-electric powertrain with rocket thrusters
— The ability to launch off a ramp and flip in midair
— Thrusters designed for brief lift-offs
— 0–60 mph in under 1 second (claimed)
— A top speed above 230 mph (claimed)
— Active aerodynamics
— A suction system for driving upside down
Starniq retweeted
send your landing page to claude with this prompt
ull get a video like this, made with code for free
thank me later ↓
Ask me for: my landing page link, my brand name and logo mark, a two-part closing line (a statement, then a short italic tail), and a 15 second track (optional).
A 14.5 second 3D fly-over of my landing page, 1440x1152 at 60fps. The page lies flat on a bright studio floor (#f9fbfb in the middle, #f2f3f6 in the corners) with a soft wide shadow around it and 24px rounded corners. One continuous camera, never a cut: it starts low over the hero and glides backwards down the page at one steady speed while looking up it, rises straight overhead to show the whole page as one strip, dives into the hero and lands it as a card under a two-line title. Focus is razor thin in front of the subject and almost none behind it, so everything near the lens melts. Cards float a little above the page with soft shadows; photos, chips and the testimonial lift off and stand up toward the lens as the camera passes them. Four small tiles of my logo lift off beside the hero button and stay with the film until the end card. The title is Geist 500, the italic tail Instrument Serif.
Banned: cuts, crossfades, stops or surges in the glide, the camera turning or swinging sideways, zooming in and back out, glows, any text laid over the page before the end card.
14.5 seconds: flight 0-8.2s, rise 7.75-9.25s, overhead 9.25-9.47s, dive 9.47-9.97s, title card 9.97-14.5s.
The camera 56° off straight-down and 1360px from the point it looks at, centred on the top half of the hero, the phone or product mockup sharp, four 32px logo tiles beside the button → 0-0.6: the glide eases in from rest → 0.1-1.35: the tiles lift, grow to 140-200px and hang just outside the page's top corners while the hero's chips rise to 60-80px and stand up 30° → 1.25-1.6: the glide doubles to cruising speed as the hero falls behind → 1.6: the second section's title passes the centre of the frame, its photos blurred near the lens → 1.35-2.7: that section's main photos lift to 100-130px and stand up 46°, two of its chips fly up to about 200px, stand up 54° and pass the left and right edges at 2.5 → 1.2-2.4: the tiles trail the camera 300px down the page, then drift out of the top → 3.0-7.3: every following section passes through at the same steady speed, each one sharp as it crosses the middle of the frame and soft below it; a logo tile drifts past the left edge close and blurred at 5.4 → 5.45-6.3: the testimonial card rises from 22 to 112px, stands up 30° and shows a 34px white edge → 7.3-8.2: the glide eases off as the footer arrives, the footer title sharp at 8.0 → 7.75-9.25: the rise, zooming out at an even rate while the tilt flattens (8.15-8.95) and the page's bottom edge settles 42px above the frame bottom → 9.25-9.47: the whole page as one centred strip, creeping 3.5% closer → 9.47-9.97: the dive, the page's top edge pinned to the frame top while it grows, everything below the hero fading out, then the top drops to y 283 so the hero lands as a 1018px wide card with 38px corners and a soft shadow; two logo tiles sit on its top corners, one crisp at the right edge, two huge soft blurs drift in at the bottom corners → 10.02: a white badge pill (logo + brand, 21px) fades in at y 44 → 10.12: line 1 at 74px, one word every 0.06s → 10.36: the italic tail at 82px in grey #8b8b92, one word every 0.05s, each word rising 16px out of a 12px blur in 0.34s → 10.6-14.5: hold, the card creeping 2% closer, the tiles drifting a few px.
1. Open my link in headless Chromium (Playwright) at 1440px wide, device scale 2, and scroll to the bottom once so lazy images and scroll animations finish. Mark the pieces that lift (cards, phone or product mockups, chips, feature photos, the testimonial, the hero button) with data-layer. Screenshot the full page with them hidden, then each piece alone on a transparent background with 28px padding, and save every piece's page position to a JSON.
2. One WebGL2 film page, 1440x1152, every frame computed from time inside seek(t): no timers, no CSS transitions. The page is a textured quad on the floor and each piece its own quad at its height, drawn lowest first with no depth buffer. Use mipmaps and 16x anisotropic filtering or the far text shimmers.
3. Drive the camera from one speed curve, never from a position key every half second. Focal length 1880px, 56° tilt, distance easing out from 1360 to 1700px and never back in, no turning. Speed down the page as a share of cruise (cruise is about 770 page px/s): 0 at 0s, 0.5 by 0.6s, held at 0.5 to 1.25s, 1.0 by 1.6s, held between 0.94 and 1.1 to 7.3s, then easing to 0.12 by 8.3s. Integrate it into the page position.
4. Depth of field per pixel: blur radius = 75 x (focus - depth) / depth in front of the focus and 6 x (depth - focus) / depth behind it, capped at 120px, 40 taps on a golden-angle disc, each tap read from a mip level matched to the blur. Keep the focus on whatever crosses the middle of the frame.
5. A lifted piece stands up by turning about its own middle, top edge rising toward the lens. Each casts a shadow on whatever is under it: the same picture in flat #1a2133, offset (0.10z, 4 + 0.36z), blurred 7 + 0.5z, 26% opacity.
6. Rise: zoom out in log scale with a smooth trapezoid speed (speeding up 7.75-8.35s, even 8.35-8.95s, slowing to a stop at 9.25s) and hand the glide over to a camera that holds the page's bottom edge at that 42px line from 8.3 to 8.65s. Dive: log scale on a quadratic ease in-out, then solve the look-at point from the pinned edge. A rounded-rect mask morphs from the full page to the hero, 24px to 38px corners.
7. Render with Playwright on the real GPU (--use-angle=d3d11 --enable-gpu --ignore-gpu-blocklist): 60fps, 16 subframes across 0.7 of a frame for motion blur, H.264 MP4. The track's hit goes on 9.97s, whooshes on 8.66 and 9.80.
If you can't run code on my computer, tell me straight away that you can only make a live preview here and that the MP4 needs Claude Code. Phones or cards that fade out with transparency show whatever is behind them, so fade them into the haze colour first and only cut to transparent at the very end. Keep most lifts tiny (20-40px) and lock the page before timing anything, because any change in a section's height shifts everything after it. Before the final render, measure a quick 30fps preview with optical flow: the speed down the page must never dip and the zoom must never turn into a zoom-in during the flight.
Ask me for the inputs, capture my page, then show me stills at 0, 1.6, 2.5, 5, 6.5, 9.3 and 11 seconds before you render.
When it comes to acquisitions, I think @finkd ,@Meta understands the long game.
Sometimes, you can’t fully appreciate the value of an acquisition at the time it happens. Years later, its impact becomes impossible to ignore.
Larry Ellison: “When WhatsApp sold for $19B, a lot of us were shocked… until we thought about it”
Back in 2014, Mark Zuckerberg paid $19 billion for WhatsApp and its 450 million monthly users.
A few months after the deal closed, the Oracle founder explained what Silicon Valley had missed at first:
“A lot of us [in Silicon Valley] were shocked — until we thought about it and understood the value of having access to that many consumers,”
His point: think about what traditional businesses, cable companies for example, spend to win each customer.
“This is not the place to debate how much you can get through WhatsApp — $1 per year per customer is not going to do it — but I believe there will be opportunity to sell these same customers other things as they join your ecosystem.”
And he added:
“There was quite a battle between Facebook and Google over that property. It wasn’t that one guy did something really silly with a lot of money. Mark Zuckerberg won an auction over Google and paid a high price but got a very valuable asset in the 21st century.”
By 2025, WhatsApp had roughly 3.1 billion monthly users worldwide.
If you're new here, @GeniusGTX is a gallery for the greatest minds in economics, psychology, and history. Follow along for more similar content.
That's the bigger picture of strategic acquisitions: you're not just investing in what a company is today; you're investing in what its people, technology, and resources could help you build tomorrow.
I see @alexandr_wang as the future meta boss
