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

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

На главную

Trying to 'fix spam' with BIP444 is misguided: this fork is slow, costly, coordination-heavy & easy to evade, while spammers adapt instantly. The fork would launch obsolete on day 1, worsen Bitcoin for real users, and trap supporters in an endless, unwinnable cat-and-mouse game.

coinjoined's profile picture

Coinjoined Chris ⚡

7,715 subscribers

60,792 просмотров • 9 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

LUKE DASHJR WANTS TO HARD FORK BITCOIN — CASEY Casey RESPONDS 0:00 Intro 4:00 Bitcoin Core v30 & the history of the blocksize wars 9:00 Spam filters, technical vs. moral argument 19:00 Bitcoin core's response 22:50 calle's explanation of spam 27:00 Dealing with Knots people on X 31:30 Luke Jr's plan to hard fork Bitcoin 47:00 Nick Szabo clocking in for the discourse 57:30 What is consensus? 1:07:00 Are girls allowed in Bitcoin?
1:13:22

LUKE DASHJR WANTS TO HARD FORK BITCOIN — CASEY Casey RESPONDS 0:00 Intro 4:00 Bitcoin Core v30 & the history of the blocksize wars 9:00 Spam filters, technical vs. moral argument 19:00 Bitcoin core's response 22:50 calle's explanation of spam 27:00 Dealing with Knots people on X 31:30 Luke Jr's plan to hard fork Bitcoin 47:00 Nick Szabo clocking in for the discourse 57:30 What is consensus? 1:07:00 Are girls allowed in Bitcoin?

Hell Money

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

Bitcoin spam debates with Charlie Spears | SLP724 cbspears ◉, co-founder Blockspace joins me to discuss spam, feasibility of BIP110, protocol upgrades, on-chain data, ordinals, OPNEXT and more. (00:00) - Intro (01:13) - The BIP110 fork and filter debate (03:59) - Consensus changes vs. policy solutions (08:36) - Understanding spam and data on the Bitcoin blockchain (11:29) - Diversity of Bitcoin clients (14:29) - What is considered spam? (17:55) - Will BIP110 stop or curb spam? (24:51) - Evolution of spam tactics in Bitcoin (29:18) - The future of Ordinals (32:16) - Does Ordinals & spam make Bitcoin a worse money? (37:04) - What is ‘Bitcoin Layers’? (43:02) - What is OPNEXT 2026? (52:49) - Closing thoughts
54:58

Bitcoin spam debates with Charlie Spears | SLP724 cbspears ◉, co-founder Blockspace joins me to discuss spam, feasibility of BIP110, protocol upgrades, on-chain data, ordinals, OPNEXT and more. (00:00) - Intro (01:13) - The BIP110 fork and filter debate (03:59) - Consensus changes vs. policy solutions (08:36) - Understanding spam and data on the Bitcoin blockchain (11:29) - Diversity of Bitcoin clients (14:29) - What is considered spam? (17:55) - Will BIP110 stop or curb spam? (24:51) - Evolution of spam tactics in Bitcoin (29:18) - The future of Ordinals (32:16) - Does Ordinals & spam make Bitcoin a worse money? (37:04) - What is ‘Bitcoin Layers’? (43:02) - What is OPNEXT 2026? (52:49) - Closing thoughts

Stephan Livera

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

JEREMY RUBIN RETURNS... for his annual vibe check on Bitcoin development, and the evolving art of soft forking Bitcoin. 0:00 Intro 1:35 What is my doing now?? 4:45 Bitcoin L2s 17:40 How hard is Jeremy working?? 23:20 VR has been an absolute fuckin flop 25:10 Rubin year in review 32:17 Bitcoin Soft forks 33:44 Covenants without a soft fork change? 39:50 Runes 50:40 Stablecoins on Bitcoin 54:35 erin's soft fork vibe check 59:16 OP_CAT and use of human capital 1:01:45 Bitcoin script 1:08:35 Ethereum vs. Bitcoin block production 1:13:20 Solana and global state 1:15:45 Predictions for Bitcoin soft forks 1:17:40 Could OP_CAT happen in 2025? 1:20:30 Casey's opinions on Bitcoin soft forks 1:22:22 How to soft fork Bitcoin 1:29:00 Overall 2025 predictions & outro
1:30:48

JEREMY RUBIN RETURNS... for his annual vibe check on Bitcoin development, and the evolving art of soft forking Bitcoin. 0:00 Intro 1:35 What is my doing now?? 4:45 Bitcoin L2s 17:40 How hard is Jeremy working?? 23:20 VR has been an absolute fuckin flop 25:10 Rubin year in review 32:17 Bitcoin Soft forks 33:44 Covenants without a soft fork change? 39:50 Runes 50:40 Stablecoins on Bitcoin 54:35 erin's soft fork vibe check 59:16 OP_CAT and use of human capital 1:01:45 Bitcoin script 1:08:35 Ethereum vs. Bitcoin block production 1:13:20 Solana and global state 1:15:45 Predictions for Bitcoin soft forks 1:17:40 Could OP_CAT happen in 2025? 1:20:30 Casey's opinions on Bitcoin soft forks 1:22:22 How to soft fork Bitcoin 1:29:00 Overall 2025 predictions & outro

Hell Money

31,389 просмотров • 1 год назад

BITCOIN RAILS #71: Expecting Hardforks | with Drivechains author Paul Sztorc 🔗 YouTube: 🌿 Spotify: Paul Sztorc founder and CEO of LayerTwo Labs and author of Bitcoin Improvement Proposals 300 and 301 (Drivechains), has been one of Bitcoin's most persistent—and controversial—thinkers, advocating for merge-mined sidechains as a way to dramatically expand Bitcoin's functionality while preserving the security of the base layer. Following our previous episode introducing his proposed Bitcoin hard fork, eCash, we discuss how the project has evolved in recent months, what to expect when the fork launches on mainnet, and Paul's perspectives on today's Layer 2 landscape and the soon-to-activate BIP 110 soft fork. An entertaining, popcorn-style conversation with one of Bitcoin's most unconventional thinkers, this episode offers diverse—and at times irreverent—commentary on some of the most important technical debates shaping Bitcoin's future. This episode of Bitcoin Rails is brought to you by: LayerTwo Labs LayerTwo Labs — developing research, software, and technologies for scaling Bitcoin via the integration of Drivechains (BIP 300/301) Hashi on Sui — a primitive for executing Bitcoin DeFi transactions, without having to trust a federated bridge or other centralized entity BitBox BitBox — an open-source Bitcoin-only hardware wallet, with smooth UX and no compromises on security. Check out Bitbox [dot] swiss and use code BITCOINRAILS to get a discount TIMESTAMPS: 00:00 — Intro 00:16 — The Coldcard exploit 09:37 — Can Bitcoin still soft fork? 15:30 — Paul's hard fork 26:12 — BIP 110's fork and the ghost of SegWit 42:03 — How drivechains work and eCash 53:00 — Quantum resistance and OP_CAT 1:01:44 — Launching a drivechain and the OP_RETURN debate 1:08:57 — The BIP 110 endgame: Udi trolling, hashrate, and Ocean 1:13:54 — Why Stratum V2 is a bad idea 1:20:33 — The decline of maximalism and the road ahead
1:32:08

BITCOIN RAILS #71: Expecting Hardforks | with Drivechains author Paul Sztorc 🔗 YouTube: 🌿 Spotify: Paul Sztorc founder and CEO of LayerTwo Labs and author of Bitcoin Improvement Proposals 300 and 301 (Drivechains), has been one of Bitcoin's most persistent—and controversial—thinkers, advocating for merge-mined sidechains as a way to dramatically expand Bitcoin's functionality while preserving the security of the base layer. Following our previous episode introducing his proposed Bitcoin hard fork, eCash, we discuss how the project has evolved in recent months, what to expect when the fork launches on mainnet, and Paul's perspectives on today's Layer 2 landscape and the soon-to-activate BIP 110 soft fork. An entertaining, popcorn-style conversation with one of Bitcoin's most unconventional thinkers, this episode offers diverse—and at times irreverent—commentary on some of the most important technical debates shaping Bitcoin's future. This episode of Bitcoin Rails is brought to you by: LayerTwo Labs LayerTwo Labs — developing research, software, and technologies for scaling Bitcoin via the integration of Drivechains (BIP 300/301) Hashi on Sui — a primitive for executing Bitcoin DeFi transactions, without having to trust a federated bridge or other centralized entity BitBox BitBox — an open-source Bitcoin-only hardware wallet, with smooth UX and no compromises on security. Check out Bitbox [dot] swiss and use code BITCOINRAILS to get a discount TIMESTAMPS: 00:00 — Intro 00:16 — The Coldcard exploit 09:37 — Can Bitcoin still soft fork? 15:30 — Paul's hard fork 26:12 — BIP 110's fork and the ghost of SegWit 42:03 — How drivechains work and eCash 53:00 — Quantum resistance and OP_CAT 1:01:44 — Launching a drivechain and the OP_RETURN debate 1:08:57 — The BIP 110 endgame: Udi trolling, hashrate, and Ocean 1:13:54 — Why Stratum V2 is a bad idea 1:20:33 — The decline of maximalism and the road ahead

Isabel Foxen Duke⚡️

18,664 просмотров • 23 дней назад

smolvm has hit stable release: v1.0.0! You can now fork smolvm. It means you can fork to create virtual machines off of an existing one in less than 100ms, with all the processes cloned and running. smolvm is the first to have this feature + cross platform compatibility (macOS and linux natively). Here's a demo of a counter continuing on a forked clone while I only started it on the original!
0:46

smolvm has hit stable release: v1.0.0! You can now fork smolvm. It means you can fork to create virtual machines off of an existing one in less than 100ms, with all the processes cloned and running. smolvm is the first to have this feature + cross platform compatibility (macOS and linux natively). Here's a demo of a counter continuing on a forked clone while I only started it on the original!

BinBin

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

Tomorrow, independent developer Super Testnet comes on the show to share why he's proposing a User-Rejected Soft Fork for BIP 110 — and explores the different ways a potential 'soft fork war' could play out around BIP 110 in August. This episode is chockfull of soft-fork history, with insights into how changes to consensus have historically been executed and how these processes could shift going forward.
0:33

Tomorrow, independent developer Super Testnet comes on the show to share why he's proposing a User-Rejected Soft Fork for BIP 110 — and explores the different ways a potential 'soft fork war' could play out around BIP 110 in August. This episode is chockfull of soft-fork history, with insights into how changes to consensus have historically been executed and how these processes could shift going forward.

Isabel Foxen Duke⚡️

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

Midnight's guarded period is coming to an end as the network prepares for its next hard fork, unlocking major upgrades. Monument Bank aims to tokenize £250M in deposits on Midnight with more banks and insurers exploring RWAs and yield opportunities.
0:47

Midnight's guarded period is coming to an end as the network prepares for its next hard fork, unlocking major upgrades. Monument Bank aims to tokenize £250M in deposits on Midnight with more banks and insurers exploring RWAs and yield opportunities.

Input Output Group

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

The director of Dragon Ball FighterZ is making an anime-styled sword-fighting game - Flip and dodge to evade attacks, parry to counter - Duel 1-on-1 or fight in massive group melees - Solo, versus, and couch co-op for up to 4 It's called Varvarion. Would you play this?
2:01

The director of Dragon Ball FighterZ is making an anime-styled sword-fighting game - Flip and dodge to evade attacks, parry to counter - Duel 1-on-1 or fight in massive group melees - Solo, versus, and couch co-op for up to 4 It's called Varvarion. Would you play this?

Indie Game Joe

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

Cats are fast! This was an easy meal for this amazing feline. The rattle snake rattles and coils which is a give away to its attack plan. In the game of cat vs snake, a cat usually wins.
2:08

Cats are fast! This was an easy meal for this amazing feline. The rattle snake rattles and coils which is a give away to its attack plan. In the game of cat vs snake, a cat usually wins.

NukeTaco ™️🇺🇸

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

"The crypto world has one very powerful idea going for it, and that's the idea of forks..." - George Hotz 🌑 I consider the ability to fork as the most underrated aspect of crypto. People forget it's the power to fork that allows cryptocurrencies to avoid centralized control, and ensure resilience against censorship, and disagreements within the community. This is what happened to the Bitcoin Cash network in late 2020. The lead developers forked the network when they dissented with the majority and decided to chart their own path by creating eCash - old handle placeholder. Anyone who held BCH through the eCash fork would now also hold an equivalent amount of XEC. Just as George describes in the clip below, holders are faced with a choice. They can split their coins, choose to sell one fork to buy more of the other, or do nothing and hold onto both. But if you held your BCH on Coinbase 🛡️, Gemini or Kraken, those exchanges have so far acted as if this fork never happened. In other words, their customers have been prevented from making a choice. While I can understand wanting to see if a fork is even viable before listing it on your exchange, the fact is over the past four years, eCash - old handle placeholder has proven itself to be one of the most technically proficient development teams in all of crypto. XEC is listed on many top tier exchanges such as Binance and Upbit Global and the team is available to offer any assistance if needed. I am urging Brian Armstrong and Jesse Powell, as well as Emilie Choi 🛡️ and Rishi to take a look at the eCash project. I am asking as respectfully as I can, please do the right thing and give your customers their eCash and let them choose for themselves. Plus, wouldn't it be great for your customers to suddenly be rewarded with free eCash they likely didn't even know they had? I'm guessing it would.
0:42

"The crypto world has one very powerful idea going for it, and that's the idea of forks..." - George Hotz 🌑 I consider the ability to fork as the most underrated aspect of crypto. People forget it's the power to fork that allows cryptocurrencies to avoid centralized control, and ensure resilience against censorship, and disagreements within the community. This is what happened to the Bitcoin Cash network in late 2020. The lead developers forked the network when they dissented with the majority and decided to chart their own path by creating eCash - old handle placeholder. Anyone who held BCH through the eCash fork would now also hold an equivalent amount of XEC. Just as George describes in the clip below, holders are faced with a choice. They can split their coins, choose to sell one fork to buy more of the other, or do nothing and hold onto both. But if you held your BCH on Coinbase 🛡️, Gemini or Kraken, those exchanges have so far acted as if this fork never happened. In other words, their customers have been prevented from making a choice. While I can understand wanting to see if a fork is even viable before listing it on your exchange, the fact is over the past four years, eCash - old handle placeholder has proven itself to be one of the most technically proficient development teams in all of crypto. XEC is listed on many top tier exchanges such as Binance and Upbit Global and the team is available to offer any assistance if needed. I am urging Brian Armstrong and Jesse Powell, as well as Emilie Choi 🛡️ and Rishi to take a look at the eCash project. I am asking as respectfully as I can, please do the right thing and give your customers their eCash and let them choose for themselves. Plus, wouldn't it be great for your customers to suddenly be rewarded with free eCash they likely didn't even know they had? I'm guessing it would.

Cain's Chronicles

11,395 просмотров • 1 год назад

How in the world is this still happening in this day and age with all the knowledge that we have. Poor elephant. It is too heavy to pull and not something an elephant is built to do. Shame on you India
0:40

How in the world is this still happening in this day and age with all the knowledge that we have. Poor elephant. It is too heavy to pull and not something an elephant is built to do. Shame on you India

Christina

40,831 просмотров • 1 год назад

Bitcoin Spam: A Libre Relay View with Proof of Cash | SLP703 ProofOfCash ⚔️ URSF joins me for a deep discussion on Bitcoin’s spam debate — from walking through the different 'camps', Libre Relay, filters and fee-market chaos to BRC-20 hype, inscriptions, and miner incentives. We explore consensus vs policy, node costs, RDTS, and more. (00:00) - Intro (01:49) - What are the different camps in this debate? (04:55) - What is consensus and how is it different from policy? (11:23) - Libre Relay and its role in Bitcoin (15:53) - Are certain transactions strictly harmful? (19:30) - Do Dust filters work?; Dust limits and their implications (29:59) - Orphan rates & mining dynamics (35:14) - What is Spy mining? (38:14) - Can all the small miners gather to punish spam on Bitcoin?; Decentralizing mining (43:40) - Do Bitcoin miners shape reality? (48:13) - What constitutes spam in Bitcoin? (56:09) - Cultural perspectives on Bitcoin and spam (1:03:15) - Are miners short-term focussed?; Bitcoin’s robust fee market (1:11:39) - The unsustainable nature of hype (1:19:50) - What are the hardware costs of running a node?; Connectivity & accessibility for Bitcoin nodes (1:29:00) - Spam - incremental costs & time of transaction confirmation (1:36:40) - Is it cost & time intensive for spammers to run Libre Relay? (1:42:00) - What are the legal perspectives of data embedding in Bitcoin? (1:49:47) - Is it feasible to block inscriptions?; Dilemma of temporary fixes (2:01:50) - Kevin’s thoughts on RDTS (Reduced Data Temporary Softfork) (2:21:53) - Is programmability important in Bitcoin? (2:27:40) - Closing thoughts
2:28:48

Bitcoin Spam: A Libre Relay View with Proof of Cash | SLP703 ProofOfCash ⚔️ URSF joins me for a deep discussion on Bitcoin’s spam debate — from walking through the different 'camps', Libre Relay, filters and fee-market chaos to BRC-20 hype, inscriptions, and miner incentives. We explore consensus vs policy, node costs, RDTS, and more. (00:00) - Intro (01:49) - What are the different camps in this debate? (04:55) - What is consensus and how is it different from policy? (11:23) - Libre Relay and its role in Bitcoin (15:53) - Are certain transactions strictly harmful? (19:30) - Do Dust filters work?; Dust limits and their implications (29:59) - Orphan rates & mining dynamics (35:14) - What is Spy mining? (38:14) - Can all the small miners gather to punish spam on Bitcoin?; Decentralizing mining (43:40) - Do Bitcoin miners shape reality? (48:13) - What constitutes spam in Bitcoin? (56:09) - Cultural perspectives on Bitcoin and spam (1:03:15) - Are miners short-term focussed?; Bitcoin’s robust fee market (1:11:39) - The unsustainable nature of hype (1:19:50) - What are the hardware costs of running a node?; Connectivity & accessibility for Bitcoin nodes (1:29:00) - Spam - incremental costs & time of transaction confirmation (1:36:40) - Is it cost & time intensive for spammers to run Libre Relay? (1:42:00) - What are the legal perspectives of data embedding in Bitcoin? (1:49:47) - Is it feasible to block inscriptions?; Dilemma of temporary fixes (2:01:50) - Kevin’s thoughts on RDTS (Reduced Data Temporary Softfork) (2:21:53) - Is programmability important in Bitcoin? (2:27:40) - Closing thoughts

Stephan Livera

27,764 просмотров • 9 месяцев назад

#Bitcoin Rollups: Whiteboard Session. There is a lot of confusion about #ZK #Rollups on Bitcoin. So I mapped out in detail how it works (afaict) under the hood. tl;dr we can use ZKP's (the scaling kind, not the privacy kind) to create an end game scaling solution for #Bitcoin. For now, BitVM enables trust minimized version of ZK Rollups (which is still really dang good). True, fully trustless roll-ups would require a soft-fork.
42:00

#Bitcoin Rollups: Whiteboard Session. There is a lot of confusion about #ZK #Rollups on Bitcoin. So I mapped out in detail how it works (afaict) under the hood. tl;dr we can use ZKP's (the scaling kind, not the privacy kind) to create an end game scaling solution for #Bitcoin. For now, BitVM enables trust minimized version of ZK Rollups (which is still really dang good). True, fully trustless roll-ups would require a soft-fork.

David Seroy 🏔️

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

A FORK IN THE POLITICAL ROAD : Liberals align with Labor, Greens & Teals and surrender on Paris Climate scam. It’s time to vote 1 - The Libertarian Party NB. : YouTube rejected this video as suitable for ads, and would have shadow banned it if I tried to publish it on their platform. I have appealed against this ruling.
12:32

A FORK IN THE POLITICAL ROAD : Liberals align with Labor, Greens & Teals and surrender on Paris Climate scam. It’s time to vote 1 - The Libertarian Party NB. : YouTube rejected this video as suitable for ads, and would have shadow banned it if I tried to publish it on their platform. I have appealed against this ruling.

Craig Kelly:🇦🇺Foundation for Economic Education

23,562 просмотров • 1 год назад

#FirewallUltra is out now on #PSVR2! We’re committed to continuing to work on and improve Firewall Ultra beyond launch, and listening to your feedback is vital. This is the beginning of an exciting journey & with the community, we will make this game as great as it can be.
0:44

#FirewallUltra is out now on #PSVR2! We’re committed to continuing to work on and improve Firewall Ultra beyond launch, and listening to your feedback is vital. This is the beginning of an exciting journey & with the community, we will make this game as great as it can be.

First Contact Entertainment | Firewall Ultra PSVR2

56,431 просмотров • 3 лет назад

Bitcoin Core OP RETURN and spam explained by a Core Dev with Antoine Poinsot | SLP661 Seeing as people want to discuss Bitcoin spam, Antoine Poinsot and I discuss Bitcoin's OP_RETURN in depth - covering spam filtering, consensus rules, miner centralization, the future of spam concerns & more. (00:00) - Intro (01:42) - Understanding Consensus & Relay policies in Bitcoin (05:21) - Historical context of standardness Rules in Bitcoin Core (11:05) - Are Bitcoin Core proponents being paid to ‘break’ Bitcoin? (13:42) - Differentiating b/w OP_RETURN PR & the general spam filtering debate (22:46) - Is Bitcoin Money or a Data Storage protocol? How do most Core devs view it? (25:36) - Why not raise the OP_RETURN limit to ~150 bytes? (29:02) - How urgent is it to fix the issue? (31:56) - Why not let the node runners choose what they want to relay? (39:03) - Do filters work or do they not? (43:27) - Are concerns about UTXO bloat, miner centralisation, block propagation etc. being overplayed by Core devs? (50:30) - Will miners who mine spam be penalised if node runners run knots? (1:00:28) - Is Bitcoin Core serious about stopping UTXO bloat? (1:07:00) - Why did Core not try to stop bare multisig spam? (1:08:58) - Should Bitcoin devs be playing a whackamole game with spammers? (1:18:24) - Summary & Future of OP_RETURN and spam concerns Includes Paid Partnerships
1:26:13

Bitcoin Core OP RETURN and spam explained by a Core Dev with Antoine Poinsot | SLP661 Seeing as people want to discuss Bitcoin spam, Antoine Poinsot and I discuss Bitcoin's OP_RETURN in depth - covering spam filtering, consensus rules, miner centralization, the future of spam concerns & more. (00:00) - Intro (01:42) - Understanding Consensus & Relay policies in Bitcoin (05:21) - Historical context of standardness Rules in Bitcoin Core (11:05) - Are Bitcoin Core proponents being paid to ‘break’ Bitcoin? (13:42) - Differentiating b/w OP_RETURN PR & the general spam filtering debate (22:46) - Is Bitcoin Money or a Data Storage protocol? How do most Core devs view it? (25:36) - Why not raise the OP_RETURN limit to ~150 bytes? (29:02) - How urgent is it to fix the issue? (31:56) - Why not let the node runners choose what they want to relay? (39:03) - Do filters work or do they not? (43:27) - Are concerns about UTXO bloat, miner centralisation, block propagation etc. being overplayed by Core devs? (50:30) - Will miners who mine spam be penalised if node runners run knots? (1:00:28) - Is Bitcoin Core serious about stopping UTXO bloat? (1:07:00) - Why did Core not try to stop bare multisig spam? (1:08:58) - Should Bitcoin devs be playing a whackamole game with spammers? (1:18:24) - Summary & Future of OP_RETURN and spam concerns Includes Paid Partnerships

Stephan Livera

28,305 просмотров • 1 год назад

Codex 0.107.0 is here, and with it: FORKS🍴 This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt. "Fork this session using n subagent(s)" This unlocks some interesting use-cases where you can launch multiple agents that retain all of your chat history up to that point, each in their own independent session. For example, you've been discussing architecture with Codex for 20 minutes, talked through constraints, reviewed existing code, settled on a model. Now you want to see two different implementation strategies side by side. Fork lets both children start from that full shared understanding. With a normal spawn, you'd have to re-explain the entire context to each child, and they'd inevitably miss nuance from the earlier conversation - which is basically a form of compaction/compression. With something like this, you could also just tell it to fork itself 5 times, and implement the same UI/frontend 5 different times in their own worktree to see which one you like the most. Other potential uses: - branching after reviews - try and rollback patterns using worktrees - parallel debugging strategies Otherwise, this is a minor update with improvements to the app server, realtime transcription, and memory. Enjoy!
0:31

Codex 0.107.0 is here, and with it: FORKS🍴 This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt. "Fork this session using n subagent(s)" This unlocks some interesting use-cases where you can launch multiple agents that retain all of your chat history up to that point, each in their own independent session. For example, you've been discussing architecture with Codex for 20 minutes, talked through constraints, reviewed existing code, settled on a model. Now you want to see two different implementation strategies side by side. Fork lets both children start from that full shared understanding. With a normal spawn, you'd have to re-explain the entire context to each child, and they'd inevitably miss nuance from the earlier conversation - which is basically a form of compaction/compression. With something like this, you could also just tell it to fork itself 5 times, and implement the same UI/frontend 5 different times in their own worktree to see which one you like the most. Other potential uses: - branching after reviews - try and rollback patterns using worktrees - parallel debugging strategies Otherwise, this is a minor update with improvements to the app server, realtime transcription, and memory. Enjoy!

am.will

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