Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Open-source TradingView Premium GitHub repo just went private The repo gained more than 2k stars in a single day, bringing the total to 43.7k in just a couple of months The devs announced on Discord that they’re going private because of the insane amount of traffic You can still... show more

Trice

2,740 subscribers

69,205 views • 3 days ago •via X (Twitter)

Finance Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

We 💙 open source hardware. Quiver, our multipurpose drone, is 100% open source: designed in our Discord community, and tested by our contributor network. Open the repo, and help us push it further. Github: Discord:

We 💙 open source hardware. Quiver, our multipurpose drone, is 100% open source: designed in our Discord community, and tested by our contributor network. Open the repo, and help us push it further. Github: Discord:

Arrow

29,896 views • 3 months ago

Wow.. you can now instantly turn any GitHub repo into AI-generated documentation, just by changing the URL. Replace “github” with “deepwiki” in any GitHub URL and you’ll see: → Instant docs for any codebase → Chat with it like a conversation

Wow.. you can now instantly turn any GitHub repo into AI-generated documentation, just by changing the URL. Replace “github” with “deepwiki” in any GitHub URL and you’ll see: → Instant docs for any codebase → Chat with it like a conversation

Oliver Prompts

122,082 views • 8 months ago

A few of you asked for the code for these SwiftUI prototypes, I just added them to my open source repo, link in the replies

A few of you asked for the code for these SwiftUI prototypes, I just added them to my open source repo, link in the replies

Mike Lee

70,188 views • 1 year ago

I used Claude Code to build and automate a legitimate quant trading strategy. The framework I built is based on the GARCH model, and it's one of the most-used trading models by real quant desks. The crazy thing is, I just completely open-sourced the GitHub repo. It contains: a Pine Script indicator for TradingView that loads the quant strategy in real time, complete installation instructions, a reusable Claude Skill & more. This is probably the most-valuable thing I've shared on 𝕏 in 2026. →

I used Claude Code to build and automate a legitimate quant trading strategy. The framework I built is based on the GARCH model, and it's one of the most-used trading models by real quant desks. The crazy thing is, I just completely open-sourced the GitHub repo. It contains: a Pine Script indicator for TradingView that loads the quant strategy in real time, complete installation instructions, a reusable Claude Skill & more. This is probably the most-valuable thing I've shared on 𝕏 in 2026. →

Miles Deutscher

88,351 views • 2 months ago

Super excited to unveil and open source Polar today (in private alpha)! Polar gives open source maintainers a better and funded backlog based on what drives the most impact within their community. Github ⭐

Super excited to unveil and open source Polar today (in private alpha)! Polar gives open source maintainers a better and funded backlog based on what drives the most impact within their community. Github ⭐

Birk Jernström

70,169 views • 3 years ago

🔴 BOMBSHELL: Some Chinese developers just humiliated the entire paid AI video industry You upload a photo You upload an audio And it generates a video of a person speaking in sync that lasts for minutes It's called LongCat-Avatar It's open source and on top of that FREE What used to require a camera, studio, and editing now comes straight from a repo I'll leave the repo link in the comments

sauda moni

272,869 views • 24 days ago

We are open-sourcing TTSKit! Run state-of-the-art text-to-speech models on your Mac and iPhone. The launch version supports Qwen Qwen3-TTS and generates audio faster than real-time playback with sub-200 ms time-to-first-byte. Voice cloning and advanced speed optimizations will be in the next version. Link to the GitHub repo and models on Hugging Face in comments.

We are open-sourcing TTSKit! Run state-of-the-art text-to-speech models on your Mac and iPhone. The launch version supports Qwen Qwen3-TTS and generates audio faster than real-time playback with sub-200 ms time-to-first-byte. Voice cloning and advanced speed optimizations will be in the next version. Link to the GitHub repo and models on Hugging Face in comments.

argmax

61,998 views • 7 months ago

Years ago, my girlfriend worked in Yamaha's pick-and-place machine business. Even after we broke up, I still didn't really understand what a "pick-and-place machine" was. Only recently, after discovering LumenPnP, an open-source pick-and-place machine, did I finally understand this fascinating piece of technology. LumenPnP enables reliable and accurate assembly of electronic components onto circuit boards — bringing industrial SMT technology closer to the open-source hardware community. The GitHub repo for this open-source pick-and-place machine is in the comments.

Years ago, my girlfriend worked in Yamaha's pick-and-place machine business. Even after we broke up, I still didn't really understand what a "pick-and-place machine" was. Only recently, after discovering LumenPnP, an open-source pick-and-place machine, did I finally understand this fascinating piece of technology. LumenPnP enables reliable and accurate assembly of electronic components onto circuit boards — bringing industrial SMT technology closer to the open-source hardware community. The GitHub repo for this open-source pick-and-place machine is in the comments.

Steven Cheng

83,086 views • 3 months ago

having a centralized skill repo in the company solves a lot of otherwise annoying problems: - visibility on which skills are actually being used, in which use cases - duplication / needing to copy same skills into a repo - allows non-technicals to use and create - version control - eval the skills the common approach to this is to throw everything into a shared GitHub repo, butit creates a poor user experience and misses a lot of the observability benefits

having a centralized skill repo in the company solves a lot of otherwise annoying problems: - visibility on which skills are actually being used, in which use cases - duplication / needing to copy same skills into a repo - allows non-technicals to use and create - version control - eval the skills the common approach to this is to throw everything into a shared GitHub repo, butit creates a poor user experience and misses a lot of the observability benefits

cole murray

12,348 views • 1 month ago

Novo Nordisk hackers got in through a GitHub token left in a repo stayed for two months took 1.3TB of data including unreleased drug formulas and internal AI models then asked for $25 million Novo Nordisk said no so now they're selling Ozempic's secrets on the dark web a GitHub token did this

Novo Nordisk hackers got in through a GitHub token left in a repo stayed for two months took 1.3TB of data including unreleased drug formulas and internal AI models then asked for $25 million Novo Nordisk said no so now they're selling Ozempic's secrets on the dark web a GitHub token did this

Mololuwa | Cybersecurity - (The God Complex)

3,427,303 views • 3 months ago

Trying to focus, sleep, or just unwind? Ambie for Windows wraps up some background noise and nature sounds in a delightful app that can help you do just that. Lose yourself in code with sounds of the beach, white noise, or even a busy coffee shop:

Trying to focus, sleep, or just unwind? Ambie for Windows wraps up some background noise and nature sounds in a delightful app that can help you do just that. Lose yourself in code with sounds of the beach, white noise, or even a busy coffee shop:

GitHub

64,129 views • 3 years ago

I'm adding a🤡 mode to the InVer_OS speech rewriter and will release a standalone .exe in the Discord so you can use it independently of InVer_OS. 🎉🎉 It's already available in the Discord, but I'll make some more tweaks and also create a free version before making a Patreon post for it *honk honk*🎊🎊 xP

I'm adding a🤡 mode to the InVer_OS speech rewriter and will release a standalone .exe in the Discord so you can use it independently of InVer_OS. 🎉🎉 It's already available in the Discord, but I'll make some more tweaks and also create a free version before making a Patreon post for it honk honk🎊🎊 xP

Dango

25,696 views • 6 months ago

We Open-Sourced a Quantized Fruit-Fly oBrain on GitHub 95% Smaller, ~98% as Accurate as the Published Connectome We quantized the entire fruit-fly nervous system that Google Research, HHMI Janelia, and collaborators published — the complete male Drosophila central nervous system, on the order of 166,000 neurons and a massive synaptic graph — and compressed it by about 95% while retaining roughly 98% of the original simulation accuracy. That is the technical claim. The more important decision is what happens next. After the oBrain team met and debated it, we made a final call: we will not keep this brain closed. We are open-sourcing it on GitHub so researchers, builders, skeptics, and anyone obsessed with biological computation can inspect the weights, the wiring, the quantization path, and the benchmarks. If a “brain” is going to live on-chain, it has to be checkable. Closed source would make that impossible. This is the same instinct that made OpenClaw🦞 a public harness instead of a private assistant, that made Hermes / Nous Research ship agent stacks in the open, and that NVIDIA keeps repeating: the strongest systems are the ones a community can attack, fork, and improve. What we actually released A quantized runtime of the published fly CNS, not a cartoon “inspired by” a fly. A size cut of ~95%, so more people can load, step, and experiment without a research cluster. Accuracy held near 98% against the reference simulation of the published connectome. Source, evaluation notes, and the path to reproduce the comparison — on GitHub, in public. Nothing inside this connectome was “trained” into being a fly. The wiring is the published map. Quantization is an engineering layer so the same graph can run cheaper, smaller, and — in our case — in environments where you can put a brain on-chain and still let outsiders verify it. Why open source, and why on-chain A biological brain map is only as useful as the number of people who can run it and try to break the claims. If we say the on-chain brain matches the Google-published fly brain, that statement is worthless unless you can: pull the code, pull the quantized artifacts, run the same probes, compare spike statistics, circuit responses, and size/accuracy tradeoffs, publish a counter-benchmark if we are wrong. That is the point of this release. Open source so the on-chain brain can be independently verified against the published connectome — and so the community can actually use it. We want people to ask hard questions: Which circuits survive quantization, and which degrade first? Do sensory-to-descending pathways still fire in the right order? How does batch simulation, GPU vs CPU, and lower precision change behavior? What does “98% accuracy” mean for a specific cell type, not just a global score? Can the compressed graph be hashed, attested, and stepped in a verifiable way on-chain without turning the science into marketing? If those questions annoy us, good. That is how a public brain should work. Who this is for Neuroscientists who already live in MaleCNS / FlyEM data. Systems people who care about sparse graphs and event-driven simulation. Quantization researchers who are tired of toy models. Crypto builders who want an on-chain object that is more than a JPEG of a neuron. Students who should not need a petabyte pipeline just to poke a looming detector and watch a giant fiber. Come read the repo. Run the reference vs quantized comparison. File issues. Propose better compressors. Port it. Wrap it. Attack the accuracy number until it is either solid or replaced by a better one. The published fly brain was already a gift to science. Keeping a compressed, runnable version locked behind a private wall would have been a waste of that gift. The brain is on GitHub. Fork it. Measure it. Make it better.

We Open-Sourced a Quantized Fruit-Fly oBrain on GitHub 95% Smaller, ~98% as Accurate as the Published Connectome We quantized the entire fruit-fly nervous system that Google Research, HHMI Janelia, and collaborators published — the complete male Drosophila central nervous system, on the order of 166,000 neurons and a massive synaptic graph — and compressed it by about 95% while retaining roughly 98% of the original simulation accuracy. That is the technical claim. The more important decision is what happens next. After the oBrain team met and debated it, we made a final call: we will not keep this brain closed. We are open-sourcing it on GitHub so researchers, builders, skeptics, and anyone obsessed with biological computation can inspect the weights, the wiring, the quantization path, and the benchmarks. If a “brain” is going to live on-chain, it has to be checkable. Closed source would make that impossible. This is the same instinct that made OpenClaw🦞 a public harness instead of a private assistant, that made Hermes / Nous Research ship agent stacks in the open, and that NVIDIA keeps repeating: the strongest systems are the ones a community can attack, fork, and improve. What we actually released A quantized runtime of the published fly CNS, not a cartoon “inspired by” a fly. A size cut of ~95%, so more people can load, step, and experiment without a research cluster. Accuracy held near 98% against the reference simulation of the published connectome. Source, evaluation notes, and the path to reproduce the comparison — on GitHub, in public. Nothing inside this connectome was “trained” into being a fly. The wiring is the published map. Quantization is an engineering layer so the same graph can run cheaper, smaller, and — in our case — in environments where you can put a brain on-chain and still let outsiders verify it. Why open source, and why on-chain A biological brain map is only as useful as the number of people who can run it and try to break the claims. If we say the on-chain brain matches the Google-published fly brain, that statement is worthless unless you can: pull the code, pull the quantized artifacts, run the same probes, compare spike statistics, circuit responses, and size/accuracy tradeoffs, publish a counter-benchmark if we are wrong. That is the point of this release. Open source so the on-chain brain can be independently verified against the published connectome — and so the community can actually use it. We want people to ask hard questions: Which circuits survive quantization, and which degrade first? Do sensory-to-descending pathways still fire in the right order? How does batch simulation, GPU vs CPU, and lower precision change behavior? What does “98% accuracy” mean for a specific cell type, not just a global score? Can the compressed graph be hashed, attested, and stepped in a verifiable way on-chain without turning the science into marketing? If those questions annoy us, good. That is how a public brain should work. Who this is for Neuroscientists who already live in MaleCNS / FlyEM data. Systems people who care about sparse graphs and event-driven simulation. Quantization researchers who are tired of toy models. Crypto builders who want an on-chain object that is more than a JPEG of a neuron. Students who should not need a petabyte pipeline just to poke a looming detector and watch a giant fiber. Come read the repo. Run the reference vs quantized comparison. File issues. Propose better compressors. Port it. Wrap it. Attack the accuracy number until it is either solid or replaced by a better one. The published fly brain was already a gift to science. Keeping a compressed, runnable version locked behind a private wall would have been a waste of that gift. The brain is on GitHub. Fork it. Measure it. Make it better.

oBrain Arc

48,524 views • 19 days ago

A 23 year old developer randomly found an open-source trading bot on GitHub. The repo already had 899 stars, so he decided to test it on a small account. He launched it in the evening. By morning, the account was up $280. The interesting part is that the bot wasn’t trying to predict Bitcoin or Solana. It barely predicted anything at all. The system monitored multiple markets at the same time and looked for moments when price or liquidity became unusually attractive. One module scanned Polymarket. Another watched Binance. A third monitored liquidity and cancelled trades whenever the risk got too high. While he was asleep, the system kept scanning markets and only executed trades that passed its filters. In the morning, he just opened Telegram and saw the list of filled orders. And this is the weird part: a few years ago, infrastructure like this would have looked like an internal tool at a small trading firm. Now you can find a similar stack sitting publicly on GitHub. Repo:

A 23 year old developer randomly found an open-source trading bot on GitHub. The repo already had 899 stars, so he decided to test it on a small account. He launched it in the evening. By morning, the account was up $280. The interesting part is that the bot wasn’t trying to predict Bitcoin or Solana. It barely predicted anything at all. The system monitored multiple markets at the same time and looked for moments when price or liquidity became unusually attractive. One module scanned Polymarket. Another watched Binance. A third monitored liquidity and cancelled trades whenever the risk got too high. While he was asleep, the system kept scanning markets and only executed trades that passed its filters. In the morning, he just opened Telegram and saw the list of filled orders. And this is the weird part: a few years ago, infrastructure like this would have looked like an internal tool at a small trading firm. Now you can find a similar stack sitting publicly on GitHub. Repo:

exit

148,384 views • 1 month ago

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 views • 2 months ago

Claude Mobile starts the idea... Ghostty finishes it I basically use Claude Mobile as a notepad now. Whenever something comes to mind, I open the app, pick a repo, and ask Claude to start exploring. Then I just let it run while I go on with my day. Later I jump into Claude Desktop and I’m right back in the same session, with context, structure, and a clearer shape of the idea. I tweak a few things to set up the coding phase. Finally, one click to Ghostty (video), open a couple of worktrees, and start working on the PR. IMPORTANT: when you move to Ghostty, it must be the exact same repo you started on mobile, otherwise the --teleport command will fail

Claude Mobile starts the idea... Ghostty finishes it I basically use Claude Mobile as a notepad now. Whenever something comes to mind, I open the app, pick a repo, and ask Claude to start exploring. Then I just let it run while I go on with my day. Later I jump into Claude Desktop and I’m right back in the same session, with context, structure, and a clearer shape of the idea. I tweak a few things to set up the coding phase. Finally, one click to Ghostty (video), open a couple of worktrees, and start working on the PR. IMPORTANT: when you move to Ghostty, it must be the exact same repo you started on mobile, otherwise the --teleport command will fail

Daniel San

67,891 views • 8 months ago

As announced in partnership with NVIDIA at CES, we’re excited to introduce Stable Point Aware 3D (SPAR3D), setting a new standard in 3D generation. Ideal for running on NVIDIA RTX AI PCs, SPAR3D enables real-time editing and complete structure generation of 3D objects from a single image in under a second. You can download the weights on Hugging Face and code on GitHub, or access the model through the Stability AI API. Learn more here: (1/3)

As announced in partnership with NVIDIA at CES, we’re excited to introduce Stable Point Aware 3D (SPAR3D), setting a new standard in 3D generation. Ideal for running on NVIDIA RTX AI PCs, SPAR3D enables real-time editing and complete structure generation of 3D objects from a single image in under a second. You can download the weights on Hugging Face and code on GitHub, or access the model through the Stability AI API. Learn more here: (1/3)

Stability AI

182,082 views • 1 year ago