Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

we sped up distributed inference by up to 5x with decentralized speculative decoding. many don't realize that AI models normally generate text one single word at a time, waiting for the network after every word. speculative decoding changes this by using a "guess & confirm" system, similar to autocomplete.... how it's done: 1. draft locally (the guess) instead of waiting for the network, a tiny, fast model on your device guesses the next few words instantly, without waiting for the network. 2. confirm remotely (the check) the massive remote model doesn't generate from scratch; it just checks the draft. it looks at the guesses in a batch and says "yes, yes, no." you get multiple words in the time it usually takes to get one. 3. adaptive logic dsd is smart. if the topic is creative, it lets the draft flow loose. if the topic is math or code, it checks more strictly. it balances speed and precision automatically so your inference almost feel instant. find out more: paper: blog:show more

Parallax

1,536 subscribers

45,584 просмотров • 8 месяцев назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

I told you to claim your free 16GB NVIDIA GPU for learning Local LLMs. Now I’m going to show you how to double its inference speed without touching the hardware. Google Colab gives you an enterprise grade NVIDIA Tesla T4 GPU for free, roughly 4 hours every single day. It is the absolute perfect sandbox for learning AI engineering, testing inference flags, and pushing massive context windows. The local AI timeline is moving way too fast. If you aren't using Multi Token Prediction (MTP) yet, you are leaving massive performance on the table. I just pushed DeepMind’s Gemma 4 26B to 64.9 t/s on this exact free tier. Let's look at the raw benchmark data running on an Ubuntu Linux environment with the latest compiled llama.cpp binaries and quantized GGUFs from Unsloth via HuggingFace: # Qwen 3.5 9B (Dense): Base: [ Prompt: 626.7 t/s | Generation: 21.0 t/s ] With MTP: [ Prompt: 539.1 t/s | Generation: 24.8 t/s ] # Gemma 4 26B QAT (MoE): Base: [ Prompt: 634.2 t/s | Generation: 48.3 t/s ] With MTP: [ Prompt: 572.1 t/s | Generation: 64.9 t/s ] If you are paying attention, this single Colab notebook reveals 3 massive observations about the current state of local LLMs: # 1. The MTP Speedup (Software Overclocking) Standard autoregressive decoding guesses one token at a time. MTP acts like a highly optimized, built in speculative decoder. It predicts multiple future tokens at once and the main model verifies them in parallel. The result? Zero accuracy loss and a massive throughput increase. Gemma jumped from 48 to 65 t/s just by flipping a flag. # 2. The MoE Paradox (Bigger is Faster) How does a 26B parameter model absolutely destroy a 9B model in raw speed on the exact same hardware? Architecture. Qwen 3.5 9B is a dense model. it activates all 9 billion parameters for every single token. Gemma 4 26B is a Mixture of Experts (MoE) model. It routes data efficiently, activating only 4B parameters per token. You get the reasoning capabilities of a 26B model with the compute cost of a 4B model. 3. Thinking Efficiency When I ran the exact same complex prompt on both models, the larger MoE spent significantly fewer "thinking" tokens to arrive at the correct answer. A smarter model doesn't just give better answers; it gets to the point faster, saving you compute cycles and preserving your context window. # Want to run this yourself? Here are the exact llama.cpp CLI commands. For Qwen (MTP is baked into the main model): ./llama-cli -m Qwen3.5-9B-UD-Q4_K_XL.gguf -p "Explain quantum computing." -n 2000 -c 8000 -ngl 99 -fa on --spec-type draft-mtp --spec-draft-n-max 4 --spec-draft-p-min 0.7 For Gemma (Using a separate lightweight draft model): ./llama-cli -m gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf --model-draft mtp-gemma-4-26B-A4B-it.gguf -p "Explain quantum computing." -n 2000 -c 8000 -ngl 99 -fa on --spec-type draft-mtp --spec-draft-n-max 4 --spec-draft-p-min 0.7 Stop waiting for a $3,000 rig. Boot up Colab, pull these models, and start building your stack. I’ve put together a completely free, cell by cell Google Colab notebook that automates this entire workflow so you can test it yourself in 5 minutes and learn. Link to the notebook is in the comments below. Experiemt with different MTP parameters, context windows and post your results in the comments.

I told you to claim your free 16GB NVIDIA GPU for learning Local LLMs. Now I’m going to show you how to double its inference speed without touching the hardware. Google Colab gives you an enterprise grade NVIDIA Tesla T4 GPU for free, roughly 4 hours every single day. It is the absolute perfect sandbox for learning AI engineering, testing inference flags, and pushing massive context windows. The local AI timeline is moving way too fast. If you aren't using Multi Token Prediction (MTP) yet, you are leaving massive performance on the table. I just pushed DeepMind’s Gemma 4 26B to 64.9 t/s on this exact free tier. Let's look at the raw benchmark data running on an Ubuntu Linux environment with the latest compiled llama.cpp binaries and quantized GGUFs from Unsloth via HuggingFace: # Qwen 3.5 9B (Dense): Base: [ Prompt: 626.7 t/s | Generation: 21.0 t/s ] With MTP: [ Prompt: 539.1 t/s | Generation: 24.8 t/s ] # Gemma 4 26B QAT (MoE): Base: [ Prompt: 634.2 t/s | Generation: 48.3 t/s ] With MTP: [ Prompt: 572.1 t/s | Generation: 64.9 t/s ] If you are paying attention, this single Colab notebook reveals 3 massive observations about the current state of local LLMs: # 1. The MTP Speedup (Software Overclocking) Standard autoregressive decoding guesses one token at a time. MTP acts like a highly optimized, built in speculative decoder. It predicts multiple future tokens at once and the main model verifies them in parallel. The result? Zero accuracy loss and a massive throughput increase. Gemma jumped from 48 to 65 t/s just by flipping a flag. # 2. The MoE Paradox (Bigger is Faster) How does a 26B parameter model absolutely destroy a 9B model in raw speed on the exact same hardware? Architecture. Qwen 3.5 9B is a dense model. it activates all 9 billion parameters for every single token. Gemma 4 26B is a Mixture of Experts (MoE) model. It routes data efficiently, activating only 4B parameters per token. You get the reasoning capabilities of a 26B model with the compute cost of a 4B model. 3. Thinking Efficiency When I ran the exact same complex prompt on both models, the larger MoE spent significantly fewer "thinking" tokens to arrive at the correct answer. A smarter model doesn't just give better answers; it gets to the point faster, saving you compute cycles and preserving your context window. # Want to run this yourself? Here are the exact llama.cpp CLI commands. For Qwen (MTP is baked into the main model): ./llama-cli -m Qwen3.5-9B-UD-Q4_K_XL.gguf -p "Explain quantum computing." -n 2000 -c 8000 -ngl 99 -fa on --spec-type draft-mtp --spec-draft-n-max 4 --spec-draft-p-min 0.7 For Gemma (Using a separate lightweight draft model): ./llama-cli -m gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf --model-draft mtp-gemma-4-26B-A4B-it.gguf -p "Explain quantum computing." -n 2000 -c 8000 -ngl 99 -fa on --spec-type draft-mtp --spec-draft-n-max 4 --spec-draft-p-min 0.7 Stop waiting for a $3,000 rig. Boot up Colab, pull these models, and start building your stack. I’ve put together a completely free, cell by cell Google Colab notebook that automates this entire workflow so you can test it yourself in 5 minutes and learn. Link to the notebook is in the comments below. Experiemt with different MTP parameters, context windows and post your results in the comments.

Alok

170,442 просмотров • 2 месяцев назад

My dual RTX PRO 6000 setup is currently training a Draft model for Qwen 3.6 27B! 🔥 I'm taking the paper DeepSeek dropped on 6/26 and going for a super ambitious application to the 27B scale. Thanks to my homelab, I was able to dive straight in — I read the paper and immediately started experimenting. The amount I've learned has been insane: - How memory bandwidth bottlenecks speed and clever ways to hack around it - Methods to train the draft model and boost its accuracy - Mechanisms to reference tokens all the way back to the previous one to skyrocket draft acceptance rates - The impact of Attention vs. GateDeltaNet on speculative decoding performance and how to handle those differences - The unique approaches and trade-offs of MTP, Dflash, JetSpec, and DSpark I could go on forever, but just from speculative decoding alone I've learned so much. The 27B architecture feels way more DSpark-native than JetSpec, so once draft training finishes, I'm going all-in with DSpark! My goal is to beat existing speculative decoding speeds outright — no task-specific shortcuts or cheating, pure general improvement. If you're into this kind of research, I'd love to hear your thoughts, impressions, and any suggestions — please reply! 🚀

My dual RTX PRO 6000 setup is currently training a Draft model for Qwen 3.6 27B! 🔥 I'm taking the paper DeepSeek dropped on 6/26 and going for a super ambitious application to the 27B scale. Thanks to my homelab, I was able to dive straight in — I read the paper and immediately started experimenting. The amount I've learned has been insane: - How memory bandwidth bottlenecks speed and clever ways to hack around it - Methods to train the draft model and boost its accuracy - Mechanisms to reference tokens all the way back to the previous one to skyrocket draft acceptance rates - The impact of Attention vs. GateDeltaNet on speculative decoding performance and how to handle those differences - The unique approaches and trade-offs of MTP, Dflash, JetSpec, and DSpark I could go on forever, but just from speculative decoding alone I've learned so much. The 27B architecture feels way more DSpark-native than JetSpec, so once draft training finishes, I'm going all-in with DSpark! My goal is to beat existing speculative decoding speeds outright — no task-specific shortcuts or cheating, pure general improvement. If you're into this kind of research, I'd love to hear your thoughts, impressions, and any suggestions — please reply! 🚀

Hikari∣LocalLLM⚡

56,870 просмотров • 2 месяцев назад

Everlyn isn’t just a video model. It’s a system you can trust. 🌀 At its core is the Lyn Protocol, the onchain layer that gives AI video permanence, provenance, and ownership. Here’s what it means: 🔹Decentralized inference: Videos are not generated by a single company’s servers. They run across a distributed network of nodes. 🔹Agent ownership: When you summon your agent, it is minted onchain. It belongs to you, not to a platform. 🔹Video provenance: Every render carries a timestamp and fingerprint written to the ledger. No one can fake or steal it. The Lyn Protocol transforms AI video from content into verifiable digital memory.

Everlyn isn’t just a video model. It’s a system you can trust. 🌀 At its core is the Lyn Protocol, the onchain layer that gives AI video permanence, provenance, and ownership. Here’s what it means: 🔹Decentralized inference: Videos are not generated by a single company’s servers. They run across a distributed network of nodes. 🔹Agent ownership: When you summon your agent, it is minted onchain. It belongs to you, not to a platform. 🔹Video provenance: Every render carries a timestamp and fingerprint written to the ledger. No one can fake or steal it. The Lyn Protocol transforms AI video from content into verifiable digital memory.

Everlyn

93,078 просмотров • 1 год назад

Holy sh!t ! OpenAI will have their custom inference chips ready in just a few months and deployed at scale by the end of the year! 🤯 Training chip = The heavy lifters that require massive amounts of data and power to build and teach the AI models from scratch. Inference chip = The specialized, highly efficient chips that actually run the AI and generate the answers in real-time when you use it. This is going to help OpenAI drastically cut down their massive compute costs, speed up model reasoning times, and finally break free from relying entirely on Nvidia to scale their operations.

Holy sh!t ! OpenAI will have their custom inference chips ready in just a few months and deployed at scale by the end of the year! 🤯 Training chip = The heavy lifters that require massive amounts of data and power to build and teach the AI models from scratch. Inference chip = The specialized, highly efficient chips that actually run the AI and generate the answers in real-time when you use it. This is going to help OpenAI drastically cut down their massive compute costs, speed up model reasoning times, and finally break free from relying entirely on Nvidia to scale their operations.

Chris

60,278 просмотров • 6 месяцев назад

PAYING PER MODEL IS THE DUMBEST THING IN TECH RIGHT NOW i was paying 3x what i needed to for AI inference the grid lets you buy a quality spec instead of a specific model.. it routes every request in real time to the cheapest option that qualifies swap one url and your code keeps working exactly the same openai-compatible, one line to switch, 200M free tokens to start

PAYING PER MODEL IS THE DUMBEST THING IN TECH RIGHT NOW i was paying 3x what i needed to for AI inference the grid lets you buy a quality spec instead of a specific model.. it routes every request in real time to the cheapest option that qualifies swap one url and your code keeps working exactly the same openai-compatible, one line to switch, 200M free tokens to start

Robin Delta

15,729 просмотров • 3 месяцев назад

HydraFusion Explained. Part I: How does the Copilot engine know what to optimize for? Your prompt is evaluated across 4 dimensions: ➡ Does it require deep reasoning? (aka. reasoning depth) ➡ Is it a sophisticated problem? (aka. code generation complexity) ➡ Is it untangling a complicated mess? (aka. debugging difficulty) ➡ Is it dominated by tool-use? (aka. tool orchestration needs) Based on this evaluation, a HyDRA score is assigned to determine the capability profile your task needs the most and to establish a quality bar. Part II: How does it choose a model? Note: It doesn' t pick one model to handle the entire job e2e, (that's Auto mode). Instead, it selects 1 of 3 execution workflows and assigns the best model at different stages based on the HyDRA score: 1️⃣ Single ⚙️ How it works: A single model completes the task from start to finish. ⚖️ Rationale: The task comfortably meets the quality bar with one model. Multi-model orchestration would add latency and cost with no meaningful quality gain. 2️⃣ Cascade ⚙️ How it works: A lightweight, cost-efficient model generates the solution. This draft is evaluated against a quality gate and if it falls short of the quality bar, the entire task escalates to a stronger, frontier model. ⚖️ Rationale: Only bring in the big guns when there is concrete evidence that a lightweight model won't meet the quality threshold. 3️⃣ Critique ⚙️ How it works: A lightweight model drafts the initial code and tool interactions. An independent, read-only frontier model reviews that draft and provides feedback. The original lightweight model then performs any targeted revision(s) before the final response is sent to the user. ⚖️ Rationale: Writing code (output tokens) is expensive while reviewing code (input tokens) is cheap. Instead of incurring the cost of a powerhouse writing hundreds of lines from scratch, a cost-efficient model writes the first draft, and the frontier model just reviews it and points out fixes. HydraFusion is available in experimental preview on the GitHub Copilot CLI: /experimental on, /model and select Hydrafusion (Research Preview)

Julia Muiruri

12,687 просмотров • 11 дней назад

we made distributed inference verifiable with <1% overhead. verification is critical for any distributed system. in a trustless network, actors may swap your 70B model for a cheaper 8B one to cut costs. until now, maintaining inference integrity meant either doubling your cost (redundancy) or exploding your latency (zkp). we created veri: an on-chain verification layer light enough for high-throughput frameworks like Parallax. it hits the economic sweet spot through architectural elegance: 1. commit-sample-verify we don't prove every step; we check a random slice using game theory. workers commit to their work before the audit. cheating becomes statistically irrational, allowing a 1% sample to secure the entire sequence. 2. simultaneous execution inference and verification happen simultaneously on the same worker pool. we don't need a separate "verifier set", so compute utilization stays high. find out more about the architecture and benchmarks: paper: blog:

we made distributed inference verifiable with <1% overhead. verification is critical for any distributed system. in a trustless network, actors may swap your 70B model for a cheaper 8B one to cut costs. until now, maintaining inference integrity meant either doubling your cost (redundancy) or exploding your latency (zkp). we created veri: an on-chain verification layer light enough for high-throughput frameworks like Parallax. it hits the economic sweet spot through architectural elegance: 1. commit-sample-verify we don't prove every step; we check a random slice using game theory. workers commit to their work before the audit. cheating becomes statistically irrational, allowing a 1% sample to secure the entire sequence. 2. simultaneous execution inference and verification happen simultaneously on the same worker pool. we don't need a separate "verifier set", so compute utilization stays high. find out more about the architecture and benchmarks: paper: blog:

Parallax

28,496 просмотров • 8 месяцев назад

I MADE MY AI AGENT 10X FASTER WITHOUT CHANGING THE MODEL not a smarter model, not a bigger context window, not another clever prompt the same kind of AI that designs vaccines for viruses we have not even met yet was spending two minutes opening the wrong files just to hand me a brief from three months ago the problem was never capability, it was the scaffolding that piled up around my agent by accident, folder by folder an agent does not think in your categories, it searches from scratch every single time, and your tidy human folders are a maze to it the fix was almost stupidly small, one index file at the root of each big folder and a few numbers in front of the folder names slowest task dropped from 2 minutes to 26 seconds, fastest ones hit 10, zero model changes capability is cheap when the scaffolding around it is broken the article breaks down the whole system in 15 minutes ↓

I MADE MY AI AGENT 10X FASTER WITHOUT CHANGING THE MODEL not a smarter model, not a bigger context window, not another clever prompt the same kind of AI that designs vaccines for viruses we have not even met yet was spending two minutes opening the wrong files just to hand me a brief from three months ago the problem was never capability, it was the scaffolding that piled up around my agent by accident, folder by folder an agent does not think in your categories, it searches from scratch every single time, and your tidy human folders are a maze to it the fix was almost stupidly small, one index file at the root of each big folder and a few numbers in front of the folder names slowest task dropped from 2 minutes to 26 seconds, fastest ones hit 10, zero model changes capability is cheap when the scaffolding around it is broken the article breaks down the whole system in 15 minutes ↓

shmidt

36,479 просмотров • 2 месяцев назад

"In the beginning was the Word, and the Word was with God, and the Word was God." -John 1:1 God does not separate Himself from His Word. That means every time you open that Bible- you are not just reading ink on a page. You are in the presence of God. His voice. His nature. His covenant. All of it is there, waiting for you. The enemy knows this. That's why he works so hard to keep you out of the Word. Pick it up today. 📖 💬 Share it with someone who needs to fall back in love with the Word.

"In the beginning was the Word, and the Word was with God, and the Word was God." -John 1:1 God does not separate Himself from His Word. That means every time you open that Bible- you are not just reading ink on a page. You are in the presence of God. His voice. His nature. His covenant. All of it is there, waiting for you. The enemy knows this. That's why he works so hard to keep you out of the Word. Pick it up today. 📖 💬 Share it with someone who needs to fall back in love with the Word.

Paula White-Cain

19,872 просмотров • 1 месяц назад

Today, we’re excited to announce a partnership with Mind Network. Both Nesa and Mind Network specialize in decentralized security, and we share a mission to bring this tech to crypto AI. Together we will explore a close technological collaboration, sharing components of our stacks with one another. Mind Network will also be using Nesa for its AI inference. Mind Network is the first FHE Restaking Layer for AI, focused on enhancing security at the consensus and validator levels of AI networks. Nesa is the Layer-1 blockchain for AI, specializing in private inference and building infrastructure to make it easy for any application, protocol, and smart contract to fuse with AI. Look out for our AMA together and other activations soon.

Today, we’re excited to announce a partnership with Mind Network. Both Nesa and Mind Network specialize in decentralized security, and we share a mission to bring this tech to crypto AI. Together we will explore a close technological collaboration, sharing components of our stacks with one another. Mind Network will also be using Nesa for its AI inference. Mind Network is the first FHE Restaking Layer for AI, focused on enhancing security at the consensus and validator levels of AI networks. Nesa is the Layer-1 blockchain for AI, specializing in private inference and building infrastructure to make it easy for any application, protocol, and smart contract to fuse with AI. Look out for our AMA together and other activations soon.

Nesa

102,011 просмотров • 2 лет назад

If you ever get the chance to go to Normandy, take it. Don't just visit it-take your time and let it sink in, because it is one of the most humbling experiences I've ever had. Standing there, looking out across those beaches, you can almost feel the weight of what happened there. It's hard to fully understand what those soldiers went through until you're standing in that place, realizing the courage it took just to run toward that shore. The beauty of Normandy is quiet and powerful, but so is the sacrifice it represents. The rows of white crosses, the history in the ground, the silence in the air-it all reminds you that freedom came at a tremendous cost. It's the kind of place that stays with you long after you leave. It makes you grateful, reflective, and a little more aware of how much was given for the life we live today. Normandy is more than a battlefield. It is a lesson in sacrifice, bravery, and remembrance. 🙏🇺🇸🙏

If you ever get the chance to go to Normandy, take it. Don't just visit it-take your time and let it sink in, because it is one of the most humbling experiences I've ever had. Standing there, looking out across those beaches, you can almost feel the weight of what happened there. It's hard to fully understand what those soldiers went through until you're standing in that place, realizing the courage it took just to run toward that shore. The beauty of Normandy is quiet and powerful, but so is the sacrifice it represents. The rows of white crosses, the history in the ground, the silence in the air-it all reminds you that freedom came at a tremendous cost. It's the kind of place that stays with you long after you leave. It makes you grateful, reflective, and a little more aware of how much was given for the life we live today. Normandy is more than a battlefield. It is a lesson in sacrifice, bravery, and remembrance. 🙏🇺🇸🙏

G-PA

178,923 просмотров • 3 месяцев назад

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 просмотров • 2 месяцев назад

Many $IREN investors are waiting for an announcement from the company, to remove any doubts around Sweetwater 2 being included in batch zero baseload. At OnlyFrans, we prefer to follow the development facts, and as you can see in the time-lapse from the past 3 weeks, the progress is undeniable. Matching the rendering, the top-view from the satellite shows that the bulk substation earthworks are showing the typical IREN proportions. Roughly 2/3 of the footprint for the 345kV network, and the 1/3 smaller footprint above for the 138kV network. Further to the left, near the top of the image, we can see that the first signs for the two 300MW Primary substations are taking shape. I expect civil works to start in Q4, and after the stormwater works at Sweetwater 1 are done, I expect the main focus of the work to be stormwater management, in parallel with building out the bulk, and primary substations. Needless to say, Sweetwater 2 is batch zero baseload. Sweetwater 2 is an early example of the market moving before the rulebook did. In March 2025, IREN committed roughly $31m to secure 600MW with AEP — ~$51.7k/MW. Nearly a year later, Texas settled on a $50k/MW financial-security benchmark (under CIAC) for large loads entering Batch Zero. This means $IREN and AEP (the interconnecting TDSP for SW2) were already operating with the kind of financial commitment Texas would later require to separate real projects from speculative load requests. In other words: IREN was positioning its projects as real/financially committed rather than speculative well before Batch Zero forced everyone to do it. Think about it, if anyone would be compliant to the batch zero baseload requirements, wouldn't it be the company that had completed CIAC (Contribution in Aid of Construction) a year before it became mandatory for everyone else? I see a site progressing as if it's approved, and a connection progress that was completed before it became common knowledge. And somehow there are people that doubt that IREN will add 600MW of power next year? Now if you are interested to find out what else there is in batch zero baseload from IREN, you know where to go. Long $IREN

Many $IREN investors are waiting for an announcement from the company, to remove any doubts around Sweetwater 2 being included in batch zero baseload. At OnlyFrans, we prefer to follow the development facts, and as you can see in the time-lapse from the past 3 weeks, the progress is undeniable. Matching the rendering, the top-view from the satellite shows that the bulk substation earthworks are showing the typical IREN proportions. Roughly 2/3 of the footprint for the 345kV network, and the 1/3 smaller footprint above for the 138kV network. Further to the left, near the top of the image, we can see that the first signs for the two 300MW Primary substations are taking shape. I expect civil works to start in Q4, and after the stormwater works at Sweetwater 1 are done, I expect the main focus of the work to be stormwater management, in parallel with building out the bulk, and primary substations. Needless to say, Sweetwater 2 is batch zero baseload. Sweetwater 2 is an early example of the market moving before the rulebook did. In March 2025, IREN committed roughly $31m to secure 600MW with AEP — ~$51.7k/MW. Nearly a year later, Texas settled on a $50k/MW financial-security benchmark (under CIAC) for large loads entering Batch Zero. This means $IREN and AEP (the interconnecting TDSP for SW2) were already operating with the kind of financial commitment Texas would later require to separate real projects from speculative load requests. In other words: IREN was positioning its projects as real/financially committed rather than speculative well before Batch Zero forced everyone to do it. Think about it, if anyone would be compliant to the batch zero baseload requirements, wouldn't it be the company that had completed CIAC (Contribution in Aid of Construction) a year before it became mandatory for everyone else? I see a site progressing as if it's approved, and a connection progress that was completed before it became common knowledge. And somehow there are people that doubt that IREN will add 600MW of power next year? Now if you are interested to find out what else there is in batch zero baseload from IREN, you know where to go. Long $IREN

Frans Bakker

102,932 просмотров • 13 дней назад

What if a network could deliver AI results closer to where data is created, instead of sending it to far‑off data centers? In collaboration with NVIDIA and Decart, we’re making that a reality by bringing GPU‑powered computing to the network edge — closer to homes and businesses — so AI applications respond in real-time. This is how we're laying the foundation for the next generation of AI‑driven services:

What if a network could deliver AI results closer to where data is created, instead of sending it to far‑off data centers? In collaboration with NVIDIA and Decart, we’re making that a reality by bringing GPU‑powered computing to the network edge — closer to homes and businesses — so AI applications respond in real-time. This is how we're laying the foundation for the next generation of AI‑driven services:

Comcast

15,708 просмотров • 6 месяцев назад

This week is already so hot. 🔥 Massive release from Decart : Lucy 2.0 a World Editing Model running at 1080p, 30FPS in realtime. This is truly exciting, the era of real-time generative reality is here. We are moving from watching AI video to living inside AI video. A breakthrough model capable of transforming the visual world in real-time. Moving beyond offline rendering, Lucy 2.0 delivers high-fidelity 1080p video generation with near-zero latency. Lucy 2.0 literally "redraws" the entire world pixel-by-pixel, while you are watching it. e.g. If you want to be an anime character, it doesn't just put a mask on you. It turns your skin into anime skin, your hair into anime hair, and the lighting in your room into anime lighting. Lucy 2.0 is also trained to stop the generated video from slowly falling apart over time, so the same stream can run much longer without faces and details drifting. So why is this a "Massive Deal"? Traditional AI video-generation model takes a prompt, you wait 10–20 minutes, and the computer "bakes" a video for you. You couldn't touch it or change it while it was happening. But Lucy 2.0 works like a mirror. It happens in real-time (30 frames per second). There is no waiting. You move your hand, the AI character moves its hand instantly. The craziest part isn't the visuals; it's the physics. Usually, AI hallucinations are glitchy—hands merge into faces, walls melt. Lucy 2.0 understands how the world works without being told. It knows that if you take off a helmet, there is hair underneath. It knows that if you splash water, droplets fly. It learned "physics" just by watching millions of videos. The physical behavior you see emerges from learned visual dynamics, not from engineered geometry or explicit physics engines. Their official technical report explicitly states that the model does not use traditional 3D engines, depth maps, or wireframes. It is a "pure diffusion model."

This week is already so hot. 🔥 Massive release from Decart : Lucy 2.0 a World Editing Model running at 1080p, 30FPS in realtime. This is truly exciting, the era of real-time generative reality is here. We are moving from watching AI video to living inside AI video. A breakthrough model capable of transforming the visual world in real-time. Moving beyond offline rendering, Lucy 2.0 delivers high-fidelity 1080p video generation with near-zero latency. Lucy 2.0 literally "redraws" the entire world pixel-by-pixel, while you are watching it. e.g. If you want to be an anime character, it doesn't just put a mask on you. It turns your skin into anime skin, your hair into anime hair, and the lighting in your room into anime lighting. Lucy 2.0 is also trained to stop the generated video from slowly falling apart over time, so the same stream can run much longer without faces and details drifting. So why is this a "Massive Deal"? Traditional AI video-generation model takes a prompt, you wait 10–20 minutes, and the computer "bakes" a video for you. You couldn't touch it or change it while it was happening. But Lucy 2.0 works like a mirror. It happens in real-time (30 frames per second). There is no waiting. You move your hand, the AI character moves its hand instantly. The craziest part isn't the visuals; it's the physics. Usually, AI hallucinations are glitchy—hands merge into faces, walls melt. Lucy 2.0 understands how the world works without being told. It knows that if you take off a helmet, there is hair underneath. It knows that if you splash water, droplets fly. It learned "physics" just by watching millions of videos. The physical behavior you see emerges from learned visual dynamics, not from engineered geometry or explicit physics engines. Their official technical report explicitly states that the model does not use traditional 3D engines, depth maps, or wireframes. It is a "pure diffusion model."

Rohan Paul

12,761 просмотров • 7 месяцев назад

You don't understand... Higgsfield MCP + Claude just automated AI film making. Every single step you used to grind through to make an AI movie, you can now do 10x faster. Drop the script into Claude Opus 4.8 and say: "Here's my script. Break it into a full shotlist. Shot number, scene, shot type, camera move and the action in each frame." Now the whole film is mapped, shot by shot. - Pull your assets. Ask Claude: "From this shotlist, list every character, every location and every prop across the whole film." That's your build list. The stuff you would need to generate and give as references in next steps. - Build the character sheets. Higgsfield MCP is connected, so Claude has hands now to do stuff directly. It generates the images itself. Have the full body, back view and close up in the character sheet. One per character. Each sheet becomes the locked reference for that face. Same move for locations, generate the empty plate for each one before anyone steps into it. - Generate the frames. Feed Claude the references plus the shot and have it write and fire the Seedance 2.0 prompt. "Using the lead's character sheet and the alley plate, generate shot 4 in Seedance 2.0. Low angle, slow push-in, rain." Claude builds the prompt, calls Seedance 2.0 and the frame lands back in chat. Use a Seedance 2.0 skill to teach Claude how to prompt it properly. Now, there are 3 ways to make the shots. Pick one per scene. - Pure prompting. Fastest one. You describe the action in words and let Seedance interpret it. For consistency across a sequence, feed it a frame from the previous shot so the look carries. - Storyboarding. You hand it a panel and it matches that composition exactly. Way more control over how the shot is framed. The tradeoff is that it can introduce more cuts than you actually want. - Path Control System This is the latest technique Seedance 2.0 technique. Generate a still base plate of the scene. Draw a red line across it to mark the exact path of the movement, then describe what's happening. Seedance follows that line for the action. Also ask Claude to remove the red line when animating. This is the one for anything where motion has to land precisely. The output reads like real live action. - Lastly, generate every clip you need, then cut them together. Get it to Capcut for editing and audio design. And that's it. The pipeline that used to need a full crew and a studio can now run from one Claude chat. 2026 is gonna be wild

You don't understand... Higgsfield MCP + Claude just automated AI film making. Every single step you used to grind through to make an AI movie, you can now do 10x faster. Drop the script into Claude Opus 4.8 and say: "Here's my script. Break it into a full shotlist. Shot number, scene, shot type, camera move and the action in each frame." Now the whole film is mapped, shot by shot. - Pull your assets. Ask Claude: "From this shotlist, list every character, every location and every prop across the whole film." That's your build list. The stuff you would need to generate and give as references in next steps. - Build the character sheets. Higgsfield MCP is connected, so Claude has hands now to do stuff directly. It generates the images itself. Have the full body, back view and close up in the character sheet. One per character. Each sheet becomes the locked reference for that face. Same move for locations, generate the empty plate for each one before anyone steps into it. - Generate the frames. Feed Claude the references plus the shot and have it write and fire the Seedance 2.0 prompt. "Using the lead's character sheet and the alley plate, generate shot 4 in Seedance 2.0. Low angle, slow push-in, rain." Claude builds the prompt, calls Seedance 2.0 and the frame lands back in chat. Use a Seedance 2.0 skill to teach Claude how to prompt it properly. Now, there are 3 ways to make the shots. Pick one per scene. - Pure prompting. Fastest one. You describe the action in words and let Seedance interpret it. For consistency across a sequence, feed it a frame from the previous shot so the look carries. - Storyboarding. You hand it a panel and it matches that composition exactly. Way more control over how the shot is framed. The tradeoff is that it can introduce more cuts than you actually want. - Path Control System This is the latest technique Seedance 2.0 technique. Generate a still base plate of the scene. Draw a red line across it to mark the exact path of the movement, then describe what's happening. Seedance follows that line for the action. Also ask Claude to remove the red line when animating. This is the one for anything where motion has to land precisely. The output reads like real live action. - Lastly, generate every clip you need, then cut them together. Get it to Capcut for editing and audio design. And that's it. The pipeline that used to need a full crew and a studio can now run from one Claude chat. 2026 is gonna be wild

Rez Karim

10,951 просмотров • 3 месяцев назад

Batch Normalization by hand ✍️ ~ 7 steps walkthrough below Batch normalization is common practice for improving training and achieving faster convergence. It sounds simple. But it is often misunderstood. 🤔 Does batch normalization involve trainable parameters, tunable hyper-parameters, or both? 🤔 Is batch normalization applied to inputs, features, weights, biases, or outputs? 🤔 How is batch normalization different from layer normalization? So I drew and calculated one entirely by hand. Goal: normalize a mini-batch of 4 examples to mean 0 and variance 1, then let the network scale it back. = 1. Given = A mini-batch of 4 training examples, each with 3 features. = 2. Linear layer = Let us multiply by the weights and add the biases. Batch norm sits after this, which answers the second question: what gets normalized is features, not inputs, weights or biases. = 3. ReLU = We apply the activation, and -2 becomes 0. Negative values are suppressed before any statistic is taken. = 4. Batch statistics = Let us compute the sum, mean, variance and standard deviation, one row at a time. A row is a feature and the four columns are the four examples, so every number here measures one feature against the rest of the batch. That is the "batch" in batch normalization, and it is exactly what layer normalization does not do. The statistics are rounded to whole numbers, which is what keeps the rest of the page doable in pen. = 5. Shift to mean 0 = We subtract the mean, in green. The four values in each feature now average to zero. = 6. Scale to variance 1 = Let us divide by the standard deviation, in orange. Each feature now has variance one, whatever scale it arrived at. = 7. Scale and shift = We multiply by a linear transformation and pass the result on. The diagonal and the last column are trainable, so having just forced every feature to mean 0 and variance 1, we hand the network the means to undo it. The outputs: Mean of each feature = [2, 1, 2] Std dev of each feature = [1, 1, 2] To the next layer = [2, -2, 2, 0], [-3, 3, 6, -3], [2, 0, 1, 2] The answers: 🤔 Both. The scale and shift are trainable, the statistics are not. Epsilon and the momentum on the running statistics are the hyper-parameters, and one mini-batch by hand needs neither. 🤔 Features, after the linear layer, not inputs, weights or biases. 🤔 Batch norm measures across the batch, one feature at a time. Layer norm measures across the features, one example at a time. 💾 Save this post!

Batch Normalization by hand ✍️ ~ 7 steps walkthrough below Batch normalization is common practice for improving training and achieving faster convergence. It sounds simple. But it is often misunderstood. 🤔 Does batch normalization involve trainable parameters, tunable hyper-parameters, or both? 🤔 Is batch normalization applied to inputs, features, weights, biases, or outputs? 🤔 How is batch normalization different from layer normalization? So I drew and calculated one entirely by hand. Goal: normalize a mini-batch of 4 examples to mean 0 and variance 1, then let the network scale it back. = 1. Given = A mini-batch of 4 training examples, each with 3 features. = 2. Linear layer = Let us multiply by the weights and add the biases. Batch norm sits after this, which answers the second question: what gets normalized is features, not inputs, weights or biases. = 3. ReLU = We apply the activation, and -2 becomes 0. Negative values are suppressed before any statistic is taken. = 4. Batch statistics = Let us compute the sum, mean, variance and standard deviation, one row at a time. A row is a feature and the four columns are the four examples, so every number here measures one feature against the rest of the batch. That is the "batch" in batch normalization, and it is exactly what layer normalization does not do. The statistics are rounded to whole numbers, which is what keeps the rest of the page doable in pen. = 5. Shift to mean 0 = We subtract the mean, in green. The four values in each feature now average to zero. = 6. Scale to variance 1 = Let us divide by the standard deviation, in orange. Each feature now has variance one, whatever scale it arrived at. = 7. Scale and shift = We multiply by a linear transformation and pass the result on. The diagonal and the last column are trainable, so having just forced every feature to mean 0 and variance 1, we hand the network the means to undo it. The outputs: Mean of each feature = [2, 1, 2] Std dev of each feature = [1, 1, 2] To the next layer = [2, -2, 2, 0], [-3, 3, 6, -3], [2, 0, 1, 2] The answers: 🤔 Both. The scale and shift are trainable, the statistics are not. Epsilon and the momentum on the running statistics are the hyper-parameters, and one mini-batch by hand needs neither. 🤔 Features, after the linear layer, not inputs, weights or biases. 🤔 Batch norm measures across the batch, one feature at a time. Layer norm measures across the features, one example at a time. 💾 Save this post!

Tom Yeh

20,848 просмотров • 2 месяцев назад

Gemini Omni doesn’t just allow you to render text more accurately — but to create it in sync with your visuals. 🎥 Choose your type, placement, animation, exposure and more. Prompt for this video: Word by word, one word on the screen at a time: did, you, know, that, this, model, can, do, pretty, good, text!? each word appears with a different animated style, perfect pacing to a rhythm, sizzle reel.

Gemini Omni doesn’t just allow you to render text more accurately — but to create it in sync with your visuals. 🎥 Choose your type, placement, animation, exposure and more. Prompt for this video: Word by word, one word on the screen at a time: did, you, know, that, this, model, can, do, pretty, good, text!? each word appears with a different animated style, perfect pacing to a rhythm, sizzle reel.

Google

153,807 просмотров • 3 месяцев назад

🚨 SCIENTISTS ARE USING AI TO MAP A HIDDEN “CLEANING SYSTEM” INSIDE THE HUMAN BRAIN AND IT COULD CHANGE HOW WE UNDERSTAND SLEEP, AGING, AND NEURODEGENERATIVE DISEASE. It’s called the glymphatic system a vast network of fluid channels that flushes toxic waste from the brain while you sleep. For years it was almost impossible to observe in detail. Now AI-powered imaging is revealing it like a living galaxy of microscopic rivers and pathways inside neural tissue. Why this matters: Your brain produces toxic proteins constantly. The glymphatic system is one of its primary waste-clearance mechanisms clearing the very proteins linked to Alzheimer’s, Parkinson’s, and other neurodegenerative diseases. But here’s the unsettling part: This cleaning system becomes dramatically less efficient with age, poor sleep, stress, and brain injury. Sleep may not just “rest” your mind it may literally wash your brain. The deeper implication is staggering: The brain isn’t just a computer. It’s a dynamic, living network that constantly rebuilds and cleanses itself in real time. The more we map it, the more it looks like an entire universe of connected energy flows inside our skulls. What if some neurological diseases begin when the brain can no longer properly “wash” itself at night? Follow for more frontier neuroscience and future technology.

🚨 SCIENTISTS ARE USING AI TO MAP A HIDDEN “CLEANING SYSTEM” INSIDE THE HUMAN BRAIN AND IT COULD CHANGE HOW WE UNDERSTAND SLEEP, AGING, AND NEURODEGENERATIVE DISEASE. It’s called the glymphatic system a vast network of fluid channels that flushes toxic waste from the brain while you sleep. For years it was almost impossible to observe in detail. Now AI-powered imaging is revealing it like a living galaxy of microscopic rivers and pathways inside neural tissue. Why this matters: Your brain produces toxic proteins constantly. The glymphatic system is one of its primary waste-clearance mechanisms clearing the very proteins linked to Alzheimer’s, Parkinson’s, and other neurodegenerative diseases. But here’s the unsettling part: This cleaning system becomes dramatically less efficient with age, poor sleep, stress, and brain injury. Sleep may not just “rest” your mind it may literally wash your brain. The deeper implication is staggering: The brain isn’t just a computer. It’s a dynamic, living network that constantly rebuilds and cleanses itself in real time. The more we map it, the more it looks like an entire universe of connected energy flows inside our skulls. What if some neurological diseases begin when the brain can no longer properly “wash” itself at night? Follow for more frontier neuroscience and future technology.

TheNewPhysics

15,641 просмотров • 3 месяцев назад

Slideshow clipping has to be the chillest business model you can really be making $5k - $15k+ a month running 10 TikTok accounts and have complete location freedom + make more than you would working a job you can literally just go to content rewards, pick a saas or brand to promote, for example skin care buy 5 aged TT accounts to start with connect US proxy / sim find videos in the niche the product is in for example skin care steal the hook of the video and content inside it and turn it into a slideshow for example: “skin care tips for broke girls” generate the images with NBP by finding a Pinterest image and getting the JSON from Gemini or ChatGPT promote the product as another “glow up” tip Post 1 a day from the start and as the accounts get more warm boost it to 2-3 + scale to more accounts If you can’t make your first $5k doing this then there is no hope

Pounds

15,415 просмотров • 7 месяцев назад