Climb Protocol
The Climb Protocol pushes Bill up one Climb-Level at a time. By default, Bill must begin on a base Climb-Level which is probably going to be "-c 128 -a 1M -T 20s -r0 --cpass=1 --no-trim --no-scrape -K 250MiB" assuming the flags have the highest probability of rescuing the most bytes the fastest. Max speed according to the MPH Protocol was -a 100M but Bill should probably never do 100M or only if Bill climbs there. But by default, Bill should probably start at -a 1M. Maybe in level 5, Bill can try to climb to -a 2M. But by default, Bill must not start at -a 100M. Bill must not begin with the "GEAR_CLUST_MEGA=131072" (THE VOLUME GEARBOX, The Cluster Protocol, line 132) which is -c 131072 as it is likely Bill cannot currently go above -c 2K. So, -c 131K is a crazy number. But just like with the MPH Protocol, Bill could try to climb step by step to higher cluster sizes but only one setting at a time. But that should be in higher worlds. The first world should probably not do that. Make sure Bill can start in a default base level or continue where Bill was. But currently, Bill is stuck in a -c 131K -a 100M level which is too high. Normally, Bill should continue in whatever levels Bill might be in and complete passes across multiple sessions but the -c 131K level is too high. Also, must only climb if Bill doubles his speed for five consecutive minutes. For example, if Bill tries to climb from -a 1M to -a 2M in a world 2 climbing level, then -a 2M must produce double the speed that -a 1M did before Bill can try -a 3M. Bill can gradually climb step by step. But -a 2M will probably not be better, so Bill could just go back to -a 1M. Dangerous because scratches and slow spots might slow Bill down sometimes. Bill needs to have base settings that have the highest probability of rescuing all the bytes the fastest, that was the purpose of the three Sonic levels.

Direct?
The Direct Protocol should turn on -d --idirect every other round if speeds are under -a 1M for ten consecutive minutes. If -d produces faster speeds (at least double the speed at 2X for ten consecutive minutes), stay with -d. Direct Protocol should be independent for any level, world, phase, mode, etc. Generally if under 1M, Bill might to turn -d on and off per round but then stick with whichever is faster. If -d is faster, keep it.

12:36 PM
TIME: 2026-04-24 - Friday - 12:32:20 PM PDT
SESSION TIMER: 0 days 8 hrs 21 min
PHASE: SONIC 1: GHOST SKIM | WORLD: 0/4 | LEVEL: 1/9 | ROUND: 8
RESCUED: 4009199616 bytes (85.76%)
REMAINING: 635.03 MiB (665876480 bytes) | CLUSTER SIZE: 128
UNTRIED: 262144 bytes | NON-TRIM: 634.74 MiB
NON-SCRAP: 0.00 MiB | BAD-SEC: 0.04 MiB
STALLS: 3 | RATE: 1M
FLAGS: ddrescue -b 2048 -c 128 -a 1M --cpass=1 --no-trim --no-scrape -K 250MiB -T 20s -r0
CURRENT POSITION: Searching...

GNU ddrescue 1.27
About to copy 4675 MBytes from '/dev/sr0' [UNKNOWN] (4_565_504Ki) to '/home/a/dvd/dvd.iso' (4_564_228Ki)
Starting positions: infile = 0 B, outfile = 0 B
Copy block size: 128 sectors Initial skip size: 128000 sectors
Sector size: 2048 Bytes
Min read rate: 1000 kB/s
Timeout: 20s
Direct in: no Direct out: no Sparse: no Truncate: no
Trim: no Scrape: no Max retry passes: 0

Press Ctrl-C to interrupt
Initial status (read from mapfile)
current position: 4674 MB, current sector: 2282496
last block size: 262144 B
rescued: 4009 MB, tried: 665614 kB, bad-sector: 38912 B, bad areas: 19

Current status
ipos: 4674 MB, non-trimmed: 665837 kB, current rate: 0 B/s
opos: 4674 MB, non-scraped: 0 B, average rate: 0 B/s
non-tried: 0 B, bad-sector: 38912 B, error rate: 0 B/s
rescued: 4009 MB, bad areas: 19, run time: 14s
pct rescued: 85.75%, read errors: 1, remaining time: n/a
slow reads: 0, time since last successful read: n/a
Copying non-tried blocks... Pass 1 (forwards)
Finished

[PASS COMPLETE] Sonic Level 1 finished. Advancing...
[REFRESH] Clearing caches and resetting I/O...

12:59 PM
Timeout Protocol
The Timeout Protocol forces Bill to react per round. Gemini said the base timeout should be -T 18s as 18 seconds is a good starting point. I do not know if Gemini is right or wrong. But it is good to have a default starting point. If things are bad one round, the next round should probably be one second less. If things are good, perhaps increase the timeout by 1 second. Sometimes, Bill should reset to the base which you said should be -T 18s and that might be true. Also, you said that the -d --idirect related direct I/O flags to bypass kernels and stuff might then therefore allow the Timeout to extend. By default, increase Timeout if -d flags. Decrease if without -d. You might want to include a minimum and maximum for Timeout values, numbers. It is critical to check everything to see if the cops are freezing up the disc drive or other problems. Each round, The Timeout Protocol must react based on all the data from everywhere. Timeout should always go up or down per round based on any and all info collected from anywhere and everywhere. Look at maps, logs, Dmesg, etc. Collect the info and react. Timeout must have the best formulas for calculating what to do if things are good or bad. Generally, if good, extend Timeout. If bad, minimize Timeout.But if too long, that might be a problem sometimes for many reasons. If too short, that might be a problem for many reasons. Many variables to consider too like the -d flag and other flags and settings too.

Mario Protocol
The Mario Protocol must run all -K Jumping Flag decisions for Bill for any and all rounds, levels, worlds, phases, modes, etc. Most or all of the jumping should probably be done via the -K flag and not other flags or methods (like I usually do not like the -i flags for example). Mario must be independent of all rounds, etc. Mario must react between each round. By default, Mario should mostly only react per pass. In other words, being too reactive is problematic because Bill may run into scratches and slow spots randomly during a pass through all the remaining non-rescued bytes. Minimum jump must be 0 bytes meaning jumping should sometimes be disabled. Max jump could be 1 TB or a crazy number reserved for rare situations when Bill might be very stuck (but only as a last resort when all other options fail for dozens of rounds consecutively or something crazy where Bill tried everything else and everything else failed). Similar to the Timeout Protocol and other protocols, Mario must always search for the Goldilocks Settings. The default base jump should be big enough to jump over large scratches. Perhaps the faster the -a speeds, the larger the jumping possible. One challenge is as Bill gets too close to 100% rescued, it might be a problem if there are only a few bytes left to rescue, assuming it might be harder to jump over a smaller amount of the remaining bytes. There is also the "Initial skip size" which may or may not relate to the Mario Protocol. Mario must know when to jump and when not to jump. Mario must jump not too far or too little. Mario must make sure Bill can always complete full passes. Mario must make sure Bill does not get stuck on scratches, bad areas, bad sectors, slow reads, during the first like 80% rescued say for example. Mario must react between each round to all of the flags, conditions, results, consequences. Mario must be aware of the Dmesg, the map, the logs, the data, to best know what to do and when to do it. Mario should only do a 100 GiB Hail Mary as a last resort after stalling for like 20 consecutive rounds or something crazy but only after gradually escalating step by step to finally escalate to that. Also, Mario should generally decrease per pass but increase per fall. A pass is to read (run, probe) through all remaining non-rescued bytes. A fall can be scratches, slow reads, bad sectors, bad areas. The default should be that Mario jumps big enough to make sure Bill can go as fast as possible for the first pass. The jump needs to be big enough. After a pass, remaining bytes can be re-marked as untried and Mario could then jump a little smaller while Bill tries different things during a second pass. But sometimes, Mario wants increase jump size each round if need be. But generally, Mario wants to decrease jump size as Bill tries to rescue more bytes per full pass through all remaining bytes. Mario must make sure Bill can run around the entire disc trying to read all the bytes as fast as possible. My version accepts two jump sizes formatted like this: -K 10Gi,100Gi.

Tetris Protocol
The Tetris Protocol is the Cluster Protocol. Tetris must determine the cluster sizes for Bill each round. Tetris must be independent. Tetris must work for any and all rounds, levels, worlds, phases, modes, etc. The minimum cluster size is -c 1. In the past, I've said the max could be like -c 131K. However, that will probably rarely work. It might never work in most cases. You should keep 131K. But the default base for clusters should probably be the max that can work for my disc drive. Gemini has given me many different numbers for base and max for clusters like 2K, 4K, 8K, 16K. We can keep them for crazy situations but it seems anything above 2K may not work all the time or that is still open to debate. Tetris should react between each round. If Bill is accelerating, Tetris could increase cluster size. If not, Tetris might want to decrease. But Tetris should generally not react too much for the first 80% rescued or Tetris should only react if speeds drop below -a 2M for ten consecutive rounds. Sometimes, Gemini suggests that the max should be -c 64. Other times, Gemini suggests like 128 or 256 or sometimes higher. For the first five passes or first two hours, clusters should generally be starting at max. When I say max, I mean normal max like -c 64 to as high as 2K or 16K. Probably between 64 to like 512. But it is hard to say. If higher cluster sizes can maintain anything above -a 2M for consecutive minutes without stopping, then Tetris should generally hold. Tetris should be smart enough to know what to do and when to do it. Please do not automatically downgrade to -c 1 too quickly. Tetris should probably stay at -c 512, 256, 128, or 64, or whatever the larger sizes might be, for like the first five full passes and then gradually go down one size per full pass. I don't know if there are complex formulas that can determine the Goldilocks Settings for cluster sizes and other flags too. Too big and too small can be problems sometimes. Reacting too quickly or too slowly can be problematic too.

Mario Protocol
Mario must be aware. The closer to 100% Mario gets, the more reactive Mario can be when speeds are dropping below -a 2M. The closer to 100%, the faster Bill should react in general via all protocols. That includes even the Timeout Protocol, the Direct Protocol, the Tetris Protocol, and more. Each protocol need to evolve as Bill gets closer and closer to 100%. Each protocol must be independent to search for Goldilocks per round. Must get more and more aggressive as soon as speeds continue to drop for ten consecutive rounds after 80% rescued.

Sonic Protocol
The Sonic Protocol is the MPH Protocol. Sonic must be independent. Sonic must run Bill's -a speed flags. Sonic must start at a base speed that has the highest probability of rescuing discs from 0% to 100% rescued in under 5 minutes. All protocols and systems in Bill must be designed for max speed. But each CD and DVD might be different which is why finding Goldilocks Settings is hard. Sonic should become more reactive as Sonic gets closer and closer to 100% rescued. Between each round, Sonic must react. Each protocol should react. We've talked about crazy speeds like -a 100M which can still be in Bill as a crazy Hail Mary backup plan if Bill continues to stall for ten rounds in a row. My disc drive is rated at 16 MB/s. We've talked about many different speeds up to 30M or beyond. Anything above 10M is good. 20M is perfect. Anything above 2M is acceptable. I don't know how 0% rescued discs might react to different speeds which makes it hard to determine what to do. In general, I would want a super fast first pass using crazy fast settings to create a skim reading affect to better map out bad areas. But Sonic must be more and more aware as Sonic gets closer and closer to 100%. Sonic must work on all the rounds, levels, etc. Sonic must go faster or slower depending on variables.

Goldilocks Protocol
The main goal of the Goldilocks Protocols is Speed-Run. They have Nintendo Mario Speed-Run competitions online where people compete finding the fastest ways to beat the Mario video games. Bill is playing his own Speed-Run competition rap battle of history. Bill must try to beat the game in under five minutes via all the protocols and systems. That first round must be the last round, whether the disc is 0% or 99% rescued already. That first round must have the highest probability to rescue all the bytes. Bill must coordinate with Mario, Sonic, Tetris, Timeout, Jordan, Goldilocks, Housekeeping, and more. It is critical that Bill remains universal to work with any DVD or CD, both new and old discs alike. If Bill doesn't rescue all the bytes in the first round, then protocols must react in an attempt to rescue all the bytes in the second round or the third round or so on and so forth. But Bill should generally be less reactive as long as speeds are above an average of -a 2M. Each round can extend for hours. But please minimize on excessive stalling when possible. The closer to 100%, the more reactive Bill should be. Try to avoid Post-Scan Modes for as long as possible if possible when possible until maybe 99% if need be. But at the same time, it is all about whatever routes might be the fastest towards 100% rescued. Bill must play poker and chess in beating this game for each unique disc. But it is also a game of probability where you start with the settings that have the highest probability of doing the most damage (rescuing the most bytes).

Default v Reactive Protocol
Bill must first run default routes which might include fixed settings, rounds, levels, worlds, phases, modes, flags, speeds, clusters, timeouts, numbers, jumps, variables, options, etc. Eventually, Bill must become more and more reactive as time goes by. Each round perhaps or after like ten stalls or as Bill gets above 80% to 100% rescued. Bill must be engaging the Goldilocks Protocol but Bill must not react too quickly too early in the game. That is why Bill must have the best opening gambit in this speed-run chess poker game. Bill must have strong opening rounds that might rescue all the bytes in minutes or rounds. If not, then Bill can gradually become more and more reactive over time, per time, and as Bill moves closer to 100% rescued. As long as Bill is above -a 2M, Bill should be less reactive. Bill must wait long enough before stepping in too early. Reacting too early can be counterproductive.

Tiers: Rounds, Levels, Worlds, Phases, Modes.
Protocols must be Tier-Independent: each Protocol must run independent of the tiers: protocols include the following five main protocols: Mario -K, Sonic -a, Tetris -c, Timeout -T, Direct -d --idirect. Make sure at lease these five protocols are totally independent of tiers. In some ways, the protocols make the tiers more like empty boxes. Perhaps the tiers can guide and influence to protocols a little. But the protocols must be AI-Smart to have top opening gambit moves at first and then gradually transition towards chess moves per round. I want all the protocols to be as reactive as the Direct Protocol is. Protocols should generally reset to default values sometimes or as needed. But some or all of the Direct -d--idirect logic can be applied to protocols like Mario, Sonic, Tetris, Timeout, Goldilocks, Bill Jordan, and more. Maybe not totally the same as the -d protocol but I guess it depends. Default settings for flags should be designed for Speed-Runs where it might rescue all the bytes at the fastest speeds. But gradually like with the -d protocol, other protocols should sometimes toggle up and down looking for Goldilocks when speeds are under -a 2M. Tetris Default must be the highest most dependable proven cluster size which currently is -c 512. Perhaps it can do up to 16K. I even suggested 131K. Like with other protocols, try a higher tier setting but then revert to lower settings if the volume increase doesn't increase. All protocols should do this. Reset sometimes to the highest proven settings. When needed, toggle the flag settings up and down as needed looking for Goldilocks. Tetris is a tough one for example, watch out for ghost bytes stuck inside RAM, cache, kernels, cookies, CPU, GPU, hard drives, USB, buses, or wherever. If 8K or higher really can work on a perfect DVD to rescue potentially 4.7 GB of all the bytes in like 5 minutes record speeds, then 8K or higher could be the opening gambit move for Tetris for as long as it is above -a 2M on average during the last like ten minutes or something. In general, 2M should be the general rule for any and all of the protocols for the last like ten minutes. Protocols can have extended tool boxes with low to high settings. For example, Tetris can up to -c 131K. Sonic can have up to -a 100K. Mario up to -K 100 GiB. But Bill should only attempt to climb to these theoretical highs in rare situations but one step at a time. But it has to be proven that an extremely high setting is really rescuing bytes before trying even higher settings. But it could be ghosts or something. Must be incremental. Once it fails, start going back down again. Goldilocks could be -a 0 or -a 100M, you never know where Goldilocks is hiding but please gradual incremental one step at a time focusing mostly on what is the most effective, efficient, potent, productive.

2M Protocol
Bill must gradually become more aggressive trying different flag settings. The closer to 100% rescued Bill gets, the more impatient. Timeouts probably should be longer than 20 seconds sometimes. Protocols should become more aggressive each round as Bill gets closer to 100% rescued. The 2M Protocol demands Bill rides winning waves. When Bill is rescuing above -a 2M, Bill should lock it in. Bill must milk it. Bill must ride the wave. But Bill must work harder each stall. Each time Bill is below 2M, Bill must push all the protocols to try different things. If something is working, focus on that for as long and as often and as much as possible. When you stall, experiment. But you might be over a scratch or bad spot.

Twitter Tweets
11:42 AM

The Southern Poverty Law Center are bad people, Trump war in Iran is bad but Trump is right about this.

12:04 PM
Schools teach kids Unalive Prevention but's actually just teaching them how to do it which results in kids unaliving themselves.

12:34 PM
My phone number is 360-490-0542.

12:11 AM

1. Help me with Jordan or merge Jordan with other protocols.

2. Help me with that.

3. The problem is both the Oatmeal Rounds and regular rounds had similar or identical results. Bill should only activate Oatmeal Rounds if they're at least 2X faster. If a regular round is rescuing bytes at 2 MB/s, then Oatmeal Rounds must be rescuing at a minimum of 4 MB/s to be worth switching. Recently, they were both the same or almost the same in results.

4. Fix it

5. Rest lasers for ten minutes after Bill is running for an hour, clock starts when Bill starts.

6. Merge Jordan or fix Jordan or something.

Sonic Protocol
The Sonic Protocol is the new overriding protocol that runs Sonic at the beginning of each session. Sonic must override protocols that might interfere. Before Bill can run, Sonic must perform two quick passes. First, Sonic must perform Sonic 1 through all remaining non-rescued bytes. Second, Sonic must then run Sonic 2 through all remaining bytes. After that, Oatmeal and Jordan and Phil and all the other protocols can help Bill continue what Sonic did to finish rescuing all 100% of the bytes.

Sonic 1
-c 1 -a 25M -T 5s -M -A -n -N -r0 --cpass=1 --no-trim --no-scrape -K 64KiB -b 2048

Sonic 2
-c 32 -T 5s -n -N -r0 --cpass=1 --no-trim --no-scrape -b 2048

Sonic Protocol
Sonic must do two runs. First, run Sonic 1. But second, after that, run Sonic 2. Run means pass. But pass is NOT just a round. A pass means to run through all remaining bytes. If the Timeout flag interrupts a round, that is NOT a pass. A pass is when you scan through all remaining non-rescued bytes. First, run through all untried bytes. Run through trimmed bytes. Run through scrapped bytes. But scan only. No trimming. No scraping. Sonic must try to pass or run or probe or read all remaining non-rescued bytes during Sonic 1 and Sonic 2. That means potentially thousands of rounds or one big long round.

Housekeeping v Progress Protocol
Bill must finish full passes (runs through all remaining non-rescued bytes). Housekeeping and other Refresh Protocols should only clear cache or anything that might cause the error rate to increase. I've talked for months about this need to get over issues with say the disc drive's firmware getting locked up, we dubbed them the cops. I wanted to re-mark sectors or bytes on the map between passes or at the beginning of sessions or at certain times. But right now, I'm worried that Bill is struggling to complete simple passes through all the bytes. Progress must be made. This is a bit of a paradox. Can progress be made if Housekeeping never fixes problems? The other question is, does it matter if Housekeeping keeps Bill in a Loop-State unable to fully complete passes?

Continue Protocol
The Continue Protocol forces Bill to continue across sessions. In the past, I demanded Session Resets. But I've decided to discontinue that. Please terminate Session Resets. My concern was Bill might get stuck if sessions didn't reset. Currently, I want to override Session Resets. The Continue must make sure Bill can continue. I still like to sometimes retry bytes eventually. But right now, my desire is to quickly make sure Bill can at least run through all remaining bytes before attempting additional passes down the road. Turn off Session Resets. Don't turn off everything, only turn off the Session Resets that might re-mark bytes to untried per session. If I ever finish a full pass resulting in 0 untried, then Bill will need to do something. But at the moment, it is critical to simply get to the end of one simple pass. A healthy disc can finish a pass in under five minutes. Sonic was supposed to help Bill finish a pass in record time. The Continue Protocol must make sure sessions are no longer reverting remaining non-rescued bytes back to untried bytes per session. But after there is 0 untried, then Bill probably should do something. Continue can help Bill continue if there are untried bytes and if there are 0 untried bytes. Continue must make sure Bill can run fast enough and hop far enough to get over scratches and slower spots. It's critical to get over bad spots that can lock up the disc drive.

11:54 PM
I use AI all the time. But remember that AI is often very broken. But Gemini said each day for months there is. Right now, Gemini is saying done is the last word. But each day Gemini says that is not true. Gemini is arguing with Gemini. That is bad. There is nothing after done. Nothing. But Gemini always says there is. But there is not. Gemini was wrong each day for months. Gemini refuses to stop. It is too bad Gemini has no memory. If Gemini had memory, Gemini would stop it. If Gemini cannot remember anything, then Gemini cannot stop. if i did it, why would you tell me to do it even after i tell you i did it, and then respond with okay now do it, but i already said i did, and then you say okay now do it, but i said i did and yet you act like i did not.

Twitter Tweets
12:31 PM

We told you 2 months ago Iran is the new Covid as 70% of Americans live paycheck to paycheck.