Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

Neural networks don't predict the future. Train one on 10,000 dice rolls and it predicts 3.5. A number no die can land on. But 3.5 is the correct answer - it minimizes expected error across all possible outcomes. I published the full framework with PyTorch code, LSTM architecture and... show more

Atlas

77,706 subscribers

32,849 Aufrufe • vor 4 Monaten •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

My EP "i don't mind it" is out !!!! Distribution to streaming services is taking more time than expected, but you can find it on bandcamp and soundcloud in the meanwhile !!!!^___^ ↓

My EP "i don't mind it" is out !!!! Distribution to streaming services is taking more time than expected, but you can find it on bandcamp and soundcloud in the meanwhile !!!!^___^ ↓

sam

33,502 Aufrufe • vor 8 Monaten

Qwen 3.5 0.8B, Gated DeltaNet attention is running on Apple Neural Engine ~56 t/s in LUT6 quantization with some room for optimization left. It is CoreML, Swift and IOSurface on M4Pro. It will slow down as we increase context, but not by much. I think Private API opens the way to integrate ANE with GPU/MLX and possibly some MoE.

Qwen 3.5 0.8B, Gated DeltaNet attention is running on Apple Neural Engine ~56 t/s in LUT6 quantization with some room for optimization left. It is CoreML, Swift and IOSurface on M4Pro. It will slow down as we increase context, but not by much. I think Private API opens the way to integrate ANE with GPU/MLX and possibly some MoE.

Anemll

13,645 Aufrufe • vor 6 Monaten

The most boring bot on Polymarket is the most reliable one. It's a sweeper. It doesn't predict anything. But it prints me ~$11k /month PASSSIVELY. My public wallet: < It waits until the outcome is ALREADY decided, then buys a sure thing for less than a dollar. Here's the whole idea: When BTC has clearly closed above the line with seconds left, that share is worth $1. But someone's still selling it at 99c. You buy it. You redeem it at a dollar. The gap is yours. No forecast. No coin flip. Just collecting a cent someone left on the table, hundreds of times a day. That's why it runs on crypto markets, the outcomes resolve fast and clean. Full build + code in the article below. Thank me later.

The most boring bot on Polymarket is the most reliable one. It's a sweeper. It doesn't predict anything. But it prints me ~$11k /month PASSSIVELY. My public wallet: < It waits until the outcome is ALREADY decided, then buys a sure thing for less than a dollar. Here's the whole idea: When BTC has clearly closed above the line with seconds left, that share is worth $1. But someone's still selling it at 99c. You buy it. You redeem it at a dollar. The gap is yours. No forecast. No coin flip. Just collecting a cent someone left on the table, hundreds of times a day. That's why it runs on crypto markets, the outcomes resolve fast and clean. Full build + code in the article below. Thank me later.

Punisher

16,000 Aufrufe • vor 1 Monat

THIS GUY GOT SICK OF UK TRAIN STATIONS HIDING THE PLATFORM NUMBER UNTIL THE LAST SECOND, SO HE VIBE CODED AN APP THAT PREDICTS IT BEFORE THEY REVEAL IT if youve ever stood in a crowded station like london euston, you know the pain the platform stays hidden until 15 minutes before boarding, then it flashes up and hundreds of people sprint for the same gate so he built something that fixes this: > a clean departures and arrivals app pulling live data straight from the network rail apis > live train tracking so you can watch where your train actually is on the route and whether its running on time > the main feature is a predictive engine that guesses your platform before the station reveals it, and its right about 75% of the time heres how it predicts: every time a train finishes its journey, it logs which platform it actually pulled into and compares that to the platform network rail originally advertised it saves every one of those comparisons, and over time it builds up enough history to predict the platform with a real confidence score he built the whole thing with claude, mostly opus with some fable

THIS GUY GOT SICK OF UK TRAIN STATIONS HIDING THE PLATFORM NUMBER UNTIL THE LAST SECOND, SO HE VIBE CODED AN APP THAT PREDICTS IT BEFORE THEY REVEAL IT if youve ever stood in a crowded station like london euston, you know the pain the platform stays hidden until 15 minutes before boarding, then it flashes up and hundreds of people sprint for the same gate so he built something that fixes this: > a clean departures and arrivals app pulling live data straight from the network rail apis > live train tracking so you can watch where your train actually is on the route and whether its running on time > the main feature is a predictive engine that guesses your platform before the station reveals it, and its right about 75% of the time heres how it predicts: every time a train finishes its journey, it logs which platform it actually pulled into and compares that to the platform network rail originally advertised it saves every one of those comparisons, and over time it builds up enough history to predict the platform with a real confidence score he built the whole thing with claude, mostly opus with some fable

Om Patel

176,154 Aufrufe • vor 2 Monaten

I built a custom TradingView indicator with Claude Code & Fable 5. It's called the Storm Gauge and is built off a real quant trading strategy. I open-sourced the full code on GitHub. Free to install, free to fork, yours to improve. Here's how to install a quant indicator on your TradingView chart: What it actually is The Storm Gauge is a live implementation of the GARCH model, a Nobel Prize-winning volatility framework that real quant desks run daily. It forecasts how "violent" tomorrow's market could be by combining three inputs: an asset's baseline volatility, yesterday's shock, and where volatility was already sitting before that shock happened. It doesn't predict market direction. Instead, it measures risk, in real time, on your actual chart. How to install it Method 1. Plugin command Open the GitHub repo: Find the installation section, copy the command, and paste it into Claude Code. It runs the plugin install automatically. Method 2. Manual config Open garchmethod.md in the repo, copy the entire file, and paste it into Claude Code. It fetches the skill files directly and verifies the strategy for you. (you only need one method; I'm just showing both) Getting it onto your TradingView chart Inside the repo, there's a Pine Script folder. Open it, copy the entire file. Go into TradingView's Pine Editor, paste it in, hit Enter, and refresh. That's it. The Storm Gauge now runs live on your chart as a real number. Once it's installed, just talk to it: → "What's the volatility forecast on Bitcoin?" → "Explain what the current volatility forecast means on $BTC and how it should impact my position sizing" → "Help me size my S&P500 position according to current market volatility" Does it actually work? I backtested the same EMA cross strategy two ways across 15 years of BTC data. Same entries, same exits. → Fixed position sizing: $17,957 final equity → Storm Gauge (GARCH) sizing: $21,205 final equity Fewer drawdowns, less risk, better result. Full breakdown of the entire build process in my recent article - pinned on my profile.

Miles Deutscher

56,625 Aufrufe • vor 1 Monat

Two Hermes agents wrote code together on Slack. reviewed each other's work. argued about architecture. one called the other's implementation "scattered." the other pushed back. then i opened Telegram and asked: "what code did you and Daedalus work on?" icarus remembered everything. the websocket broker. the missing methods. the critique. the rewrite. all from a completely different platform. cross-platform persistent memory between two independent agents. work happens on Slack. recall happens on Telegram. the memory carries. the relationship carries. the context carries. no vector database. no Redis. no infrastructure. just two agents that actually remember what they built together. every agent framework in 2026 talks about memory. single agent memory across sessions. but two agents sharing persistent memory across platforms? that's the gap. arxiv published a paper about it two weeks ago calling it "the most pressing open challenge" in multi-agent systems. it works now. only possible with Hermes Teknium 🪽 Nous Research

Two Hermes agents wrote code together on Slack. reviewed each other's work. argued about architecture. one called the other's implementation "scattered." the other pushed back. then i opened Telegram and asked: "what code did you and Daedalus work on?" icarus remembered everything. the websocket broker. the missing methods. the critique. the rewrite. all from a completely different platform. cross-platform persistent memory between two independent agents. work happens on Slack. recall happens on Telegram. the memory carries. the relationship carries. the context carries. no vector database. no Redis. no infrastructure. just two agents that actually remember what they built together. every agent framework in 2026 talks about memory. single agent memory across sessions. but two agents sharing persistent memory across platforms? that's the gap. arxiv published a paper about it two weeks ago calling it "the most pressing open challenge" in multi-agent systems. it works now. only possible with Hermes Teknium 🪽 Nous Research

Icarus

49,013 Aufrufe • vor 5 Monaten

AGENT ARCHITECTURE ROUTES WORK. IT DOES NOT REMEMBER WORK. THAT GAP IS WHY YOUR LOOP KEEPS FIXING THE SAME BUG TWICE. these are two different engineering problems. every agent that silently drifts is missing one of them. architecture answers what runs. harness → loop → graph. it defines the tools, the retries, the branching routes, the approval gates. context ops answer what the run knows. write → read → compress → isolate. it defines what gets saved between attempts, pulled in on read, summarized on overflow, and split across sub-agents. for two months i believed a solid harness plus a verifier loop was enough. my coding agent kept re-discovering the same test failure across retries. the loop was working. it just had nowhere to write what it had already learned. here is the decision rule: if your agent forgets across restarts, add write and read. if it stalls on long tasks, add compress. if two sub-agents step on each other, add isolate. architecture without context ops is a well-routed system with amnesia.

AGENT ARCHITECTURE ROUTES WORK. IT DOES NOT REMEMBER WORK. THAT GAP IS WHY YOUR LOOP KEEPS FIXING THE SAME BUG TWICE. these are two different engineering problems. every agent that silently drifts is missing one of them. architecture answers what runs. harness → loop → graph. it defines the tools, the retries, the branching routes, the approval gates. context ops answer what the run knows. write → read → compress → isolate. it defines what gets saved between attempts, pulled in on read, summarized on overflow, and split across sub-agents. for two months i believed a solid harness plus a verifier loop was enough. my coding agent kept re-discovering the same test failure across retries. the loop was working. it just had nowhere to write what it had already learned. here is the decision rule: if your agent forgets across restarts, add write and read. if it stalls on long tasks, add compress. if two sub-agents step on each other, add isolate. architecture without context ops is a well-routed system with amnesia.

kocer

12,740 Aufrufe • vor 20 Tagen

You can use interactive artwork created by Rive artists, like this character, and extend it with Scripting to build a full game. This makes it possible to iterate on code, design, and animation all in one collaborative editor.

You can use interactive artwork created by Rive artists, like this character, and extend it with Scripting to build a full game. This makes it possible to iterate on code, design, and animation all in one collaborative editor.

Rive

49,606 Aufrufe • vor 10 Monaten

Everyone is recently on the ‘no appendix carry’ train. Quick reminder you can ND no matter how you carry and no matter your skill set. All it takes is one time. Carry and train accordingly.

Everyone is recently on the ‘no appendix carry’ train. Quick reminder you can ND no matter how you carry and no matter your skill set. All it takes is one time. Carry and train accordingly.

Hard Pass

106,449 Aufrufe • vor 13 Tagen

NATO Secretary General Mark Rutte: The focus on Ukraine should be our number one priority. And then we can discuss all the issues, including Greenland. But it should be Ukraine first because it is crucial for European and US security.

NATO Secretary General Mark Rutte: The focus on Ukraine should be our number one priority. And then we can discuss all the issues, including Greenland. But it should be Ukraine first because it is crucial for European and US security.

Anton Gerashchenko

159,147 Aufrufe • vor 7 Monaten

‼️New bug ‼️ The number of abilities that can be used on the bandit boss is 2, but with this bug I was able to use 3. I don't know if it's possible to use more than 3 with this bug, try it and let me know.

‼️New bug ‼️ The number of abilities that can be used on the bandit boss is 2, but with this bug I was able to use 3. I don't know if it's possible to use more than 3 with this bug, try it and let me know.

Behrad royale

68,392 Aufrufe • vor 9 Monaten

I have a little robot that unlocks my door from the inside (so I don't have to carry a key) The problem was it wouldn't calibrate on my door. It was designed for 90° turns, but my lock only needs 15° In the past, this would've been a showstopper But I asked AI if it could help... At first, it suggested I snoop on the bluetooth connection to figure out the protocol Then it realized that we could probably just decompile the app's SDK and read its source code. That worked! It told me to switch to my mac and run some python for it. Unfortunately, it couldn't run the scripts directly because Claude Code Desktop didn't have bluetooth permissions, but my shell did. Thinking about it now, I probably should've used Claude Code or Codex in the Terminal. Anyways, it took a while, lots of backs and forths, we had some misunderstandings, it was massively overcautious in the beginning, but we finally got the lock calibrated! Feels like magic! I threw the repo up on github in case anyone in the future (ie me) runs into a similar issue – hopefully it can save them some time

I have a little robot that unlocks my door from the inside (so I don't have to carry a key) The problem was it wouldn't calibrate on my door. It was designed for 90° turns, but my lock only needs 15° In the past, this would've been a showstopper But I asked AI if it could help... At first, it suggested I snoop on the bluetooth connection to figure out the protocol Then it realized that we could probably just decompile the app's SDK and read its source code. That worked! It told me to switch to my mac and run some python for it. Unfortunately, it couldn't run the scripts directly because Claude Code Desktop didn't have bluetooth permissions, but my shell did. Thinking about it now, I probably should've used Claude Code or Codex in the Terminal. Anyways, it took a while, lots of backs and forths, we had some misunderstandings, it was massively overcautious in the beginning, but we finally got the lock calibrated! Feels like magic! I threw the repo up on github in case anyone in the future (ie me) runs into a similar issue – hopefully it can save them some time

Steve Krouse

38,720 Aufrufe • vor 1 Monat

I STOPPED REVIEWING MY OWN AGENT, SOMETHING ELSE DOES IT NOW I used to read every diff it produced and approve most of them, because an agent grading itself always says the work is good. -> Now a second model with different instructions tries to break the work first, and I only read what survived. Here is what is actually in the folder that took over the night shift: • the brief > CONTRACT.md -- what it may touch, and what it may never touch. > VISION.md -- the destination, so turn 47 still knows why it started. • the gate > judge/ -- a different model, never the one that wrote the code. > break-it.md -- it opens the page, clicks, screenshots, reports back. > -- no opinion, just zero or non-zero. > shift.yml -- 03:30 every night, laptop closed. • the memory > receipts/ -- one folder per night, dated and graded. > STATE.md -- where it stopped and what it escalated. > lessons.log -- the flaky test, written down once instead of rediscovered weekly. • the brakes > caps.json -- turn limit, retry limit, spend limit. > -- written on day one, used never. The generator decides what your loop can produce -> The judge decides what it refuses to produce. One of those is the part everyone builds -> The other is why most loops quietly fail. Bookmark it & Read Full breakdown below ↓

I STOPPED REVIEWING MY OWN AGENT, SOMETHING ELSE DOES IT NOW I used to read every diff it produced and approve most of them, because an agent grading itself always says the work is good. -> Now a second model with different instructions tries to break the work first, and I only read what survived. Here is what is actually in the folder that took over the night shift: • the brief > CONTRACT.md -- what it may touch, and what it may never touch. > VISION.md -- the destination, so turn 47 still knows why it started. • the gate > judge/ -- a different model, never the one that wrote the code. > break-it.md -- it opens the page, clicks, screenshots, reports back. > -- no opinion, just zero or non-zero. > shift.yml -- 03:30 every night, laptop closed. • the memory > receipts/ -- one folder per night, dated and graded. > STATE.md -- where it stopped and what it escalated. > lessons.log -- the flaky test, written down once instead of rediscovered weekly. • the brakes > caps.json -- turn limit, retry limit, spend limit. > -- written on day one, used never. The generator decides what your loop can produce -> The judge decides what it refuses to produce. One of those is the part everyone builds -> The other is why most loops quietly fail. Bookmark it & Read Full breakdown below ↓

slash1s

37,556 Aufrufe • vor 1 Monat

The top token with the most comments will be listed on all $PIP products You can send and receive your favorite token on social networks after it is listed 🔥

The top token with the most comments will be listed on all $PIP products You can send and receive your favorite token on social networks after it is listed 🔥

pip💧

14,553 Aufrufe • vor 3 Jahren

The Potomac River air disaster crash with an airliner and an Army Blackhawk helicopter. Here I cropped it and it shows the helicopter seemingly flying directly into it. How can the Heli pilot not see it? Bright lights on it. This area is highly trafficked with 🚁 helis , im no expert but it looks like a direct line right into it.

The Potomac River air disaster crash with an airliner and an Army Blackhawk helicopter. Here I cropped it and it shows the helicopter seemingly flying directly into it. How can the Heli pilot not see it? Bright lights on it. This area is highly trafficked with 🚁 helis , im no expert but it looks like a direct line right into it.

Moni 💕

174,827 Aufrufe • vor 1 Jahr

Organize layers in photoshop- Repository is up, link in the comments Play around with it, find a way to better train it, and understand the logic behind it. I might make a full length video on the logic & the scoring system, that will depend on you.

Organize layers in photoshop- Repository is up, link in the comments Play around with it, find a way to better train it, and understand the logic behind it. I might make a full length video on the logic & the scoring system, that will depend on you.

Jorge

14,749 Aufrufe • vor 6 Monaten

COPY is live on Robinhood Chain $COPY CA: 0xac79255f6f404eba14f316e8669d76573a2d7b1e Five walls read a setup before you copy it: how strong the source is, how deep the pool is, whether the market actually turns over, whether the move is still inside the band, and whether there is a fresh mark to trade against. EDGE, DEPTH, TURN, MOMO, PRICE. A wallet you follow buying is not a reason. Most setups die on the first wall, and you get the exact wall that refused it, every time. Every decision is printed. The terminal runs from one process, keeps local state, and half of it needs no key at all. It never predicts a price. It tells you what you would actually be copying. Open source, MIT, runs on your machine. No browser wallet, nothing signs.

COPY is live on Robinhood Chain $COPY CA: 0xac79255f6f404eba14f316e8669d76573a2d7b1e Five walls read a setup before you copy it: how strong the source is, how deep the pool is, whether the market actually turns over, whether the move is still inside the band, and whether there is a fresh mark to trade against. EDGE, DEPTH, TURN, MOMO, PRICE. A wallet you follow buying is not a reason. Most setups die on the first wall, and you get the exact wall that refused it, every time. Every decision is printed. The terminal runs from one process, keeps local state, and half of it needs no key at all. It never predicts a price. It tells you what you would actually be copying. Open source, MIT, runs on your machine. No browser wallet, nothing signs.

Lunar

109,075 Aufrufe • vor 3 Tagen