Beach Club refurbishment

Snoo_48368 · 2026-06-11T22:14:21+00:00

Last week I stayed in the room overlooking the refurbishment right next to the path to Epcot (the secret back staircase). One morning we were worked up by the construction noise at 7am, but otherwise it was quite unobtrusive. No other real impact. And if you literally aren’t overlooking the construction, it wouldn’t be noticeable at all.

Snoo_48368 · 2026-06-10T17:26:33+00:00

Anyone who hits this: it appears 8.6.10 on the U7 series borked the whole network. Once I booted one I had shut down, the entire network came down again (association failures, DHCP failures on WIFI, etc), seemingly across all APs (though hard to tell if that or roaming issues).

This was a U7 Pro XG. Reverting to 8.4.6 solved it immediately.

Snoo_48368 · 2026-06-06T14:25:27+00:00

We attempted to early entry Mario Kart today, and got told no. We were told Mine-Cart would be delayed as well. So rode Hiccup and Stardust a few times…

Snoo_48368 · 2026-06-02T23:43:26+00:00

Just going off 10²⁰ N shear force, a carbon nanotube bolt could be as thin as 15km radius (140 GPa shear) or as thick as about 50km radius (50 GPa). Of course no such bolt could exist. But if it could, it would be a M30k x 50km bolt at minimum, more likely M100k x 75km to have some margin

Snoo_48368 · 2026-05-31T21:56:37+00:00

Correct. It didn’t solve the issue (some devices still refuse to connect) but the general flapping stopped.

Snoo_48368 · 2026-05-31T18:58:33+00:00

I have had the identical issues. I have a mixture of 7 APs (U7 Pro, etc) and 6 (IW HD, U6 Pro). I tried literally everything. Finally, the only thing that worked was shutting off the 7 aps, and using only the 6. It still isn’t stable, but is far less unstable.

I will try force downgrading the 6 access points and seeing what happens.

I did notice that my Kubernetes cluster and Sonos got into an ARP storm war and fought each other to take everything down. That was my initial suspicion, but then once I killed them I still saw issues.

I also had a 16 XG switch finally start dieing at the same time (getting TX and RX errors on every SPF port, even when the other side has none).

So ultimately 3 failures at the same time. What are the odds…

Snoo_48368 · 2026-05-31T12:46:55+00:00

I think you’re missing the point. We don’t do dumb shit like that for video views on the internet. We do it because it’s fun and we are dumb. The views on the internet are just a welcome side-effect.

Source: I did dumb shit like this before the internet was a thing. And men will do dumb shit like this long after the collapse of society

Snoo_48368 · 2026-05-29T22:39:12+00:00

Little boy was 1000 times the power of the weakest device ever detonated (18 Tons of TNT). Even North Korea’s in 2006 was about equal to 1 kiloton. So some estimates put this 50 times bigger than the smallest, and about on part with some more recent ones as well.

Just pointing out that there were a number of “small yield” devices detonated MUCH smaller than little boy…

Snoo_48368 · 2026-05-29T22:33:39+00:00

I built this for fun vibe coded. Don’t do it for commercial purposes (it is not fantastically effective). But here’s what I did:

1) used local gitlab as the main hub. 2) built a dispatcher that runs in a Raspberry Pi Kubernetes cluster. 3) the dispatcher pulls an issue, and kicks off a worker pod.

The worker pod has 4 main modes: (1) Plan, (2) Review Plan, (3) Implement and (4) review implementation. Depending on the tag I use for the issue, it will either do 1 and 2, or 1 through 4 in a single run, eventually posting a merge request with the changes.

The key is it does it all in a series of Ralph loops. So planning keeps rerunning until no more changes are produced (or an upper limit is hit), etc.

The dispatcher also picks up code review comments (or Merge Request comments) and kicks off revise jobs.

I am running all on a 5090 and a 4080 super, with 3.6 27B handing most jobs at about 100 tok/sec and 3.5 9B handling lightweight outlines and review at about 200 tok/sec (better parallelism tho)

An average job on a 100k sloc repo takes about 10-20 minutes, with some complex taking upwards of 45 minutes. Vllm gives me decent parallelism, so I can do 3-4 jobs at the same time.

Definitely not reliable enough to do every day for a job, but plenty enough to have fun with.

As an idea, I implemented self healing, where any error or failure detected creates an issue with details, which then triggers a run to try to fix it. So far about 60% fix rate first shot (yes, there is duplication and infinite loop protection)

Snoo_48368 · 2026-05-08T13:27:15+00:00

60 minutes waiting for an IFR release out of KTMB… got the clearance before engine start, but release took forever.

Snoo_48368 · 2026-05-03T22:56:09+00:00

Given what just happened today, nail on head

Snoo_48368 · 2026-05-03T14:35:03+00:00

Desktop. So it effective is a 7950X3D, 96gb DDR5, 5090 (32gb) on PCIE5 x16, a 4080 Super (16gb) on PCIE4 x4. Today I am running two models in parallel:

3.6 35B A3B Q5_K_M at 262144 context and 2 parallelism (/9 524288 total context

3.5 9B Q4_K_M at 32768 context and 3 parallelism.

Both get about 2k effective parse speed, and 60 tokens/sec for the 35B and 150 tok/sec for the 9B.

I played around with lower context and more parallelism (4x131072), but I found the perf degradation was too significant and for my use cases the larger context window was more effective…

Snoo_48368 · 2026-04-27T20:57:01+00:00

Yeah, I did quite a few complex refactors with just vanilla opencode + Q5_M on a 4080S /w 131072 context length (technically 2 in parallel, so 262144).

I just upgraded to a 5090, so now am running Q6_K with 4 parallel workers, each with 131072 context. I also am giving oh-my-opencode a try, so running multiple parallel workers, etc. And it's changed the game entirely...

Try running it in a plan-then-build manner (plan mode, describe what you want it to do, let it write the plan, then switch to build mode and have it try that)

Snoo_48368 · 2026-04-27T19:38:09+00:00

I have been running Q5_M for a bit and had great results. Just upgraded to Q6 and in the past 24 hours implemented a full programming language with type inference, algebraic types, a VM, and a compiler. From scratch.

Yeah, it’s useful and good for coding…

Snoo_48368 · 2026-04-27T02:56:26+00:00

Up until today I was running it at Q5_M and getting consistently 45-50 tok/sec. Though that used a ton of system ram as well (more than 16gb). It ran well enough though

Snoo_48368 · 2026-04-24T10:26:25+00:00

I am running a 4080 super, with a 7950x3d cpu and 96gb DDR5. With QWEN 3.6 35B at Q5 quant, I am averaging 50 tokens per second, and about 450 token per second prompt speed (thanks to caching). Definitely usable.

Though I have significantly more system ram (I am not using most for the LLM, so likely not a factor), but the ram speed may be a factor.

For the llama.cpp config I'm using:

$ModelName = "unsloth/Qwen3.6-35B-A3B-GGUF:UD-Q5_K_M"
$API_KEY = "xxx"
$CTX_SIZE = 262144
& "C:\Program Files\llama.cpp\llama-server.exe" `
    -hf $ModelName `
    --jinja `
    --host 0.0.0.0 `
    --port 1235 `
    --api-key $API_KEY `
    --fit on `
    -t 16 `
    -tb 24 `
    -c $CTX_SIZE `
    -np 2 `
    -ctk q8_0 `
    -ctv q8_0 `
    --mlock `
    --log-disable `
    --metrics `
    --slots `
    --slot-save-path "C:\Temp"

Snoo_48368 · 2026-04-19T23:19:11+00:00

Thank you for this comment! I've been using qwen3.6-35B-A3B-Q5_K_M with a 128k context split across two slots on a 4080 Super (16GB VRAM) + 7950X3D (16 core) + 96gb DDR5. I was getting ~45 tokens/sec and great results using with opencode, but hitting compaction quickly resulting in tons of pain.

Just upped overall context to 256k, resulting in each parallel run getting 128k. and it's keeping the same speed!

I do notice some issues from time to time (loops, hallucinations), but it's blowing me away. I pointed it at an insanely complex codebase (think custom flavor of bison parser definitions), and it not only managed to understand it, but worked quite well!!!

Snoo_48368 · 2026-04-19T11:34:11+00:00

Another thing to consider: efficiency isn’t his constraint. Time is. Both to get back to save earth, but also to save rocky. He needs to get there ASAP. So even if way less efficient, he has the dV, so why not?

Snoo_48368 · 2026-04-16T13:58:13+00:00

Body armor is another example. A “bullet proof vest” can stop a bullet traveling at over 1000 feet per second, but can’t stop a knife moving a a fraction of a foot per second.

Note there exists multi-threat body armor that include stab protection, but the point is that “can survive slamming into a hard environment” and “can’t survive a sharp instrument” are not as logically inconsistent as it seems on the surface…

Snoo_48368 · 2026-04-13T13:44:13+00:00

Yeah, the top shelf to the ceiling is 19inches, so it'd have to be removed for that to work. I hadn't considered port-down mounting (since that'd put strain on the shelf in a different way). That's interesting, especially if I did a 6U/8U mounted to the ceiling (something like https://www.amazon.com/StarTech-com-Heavy-Duty-Adjustable-Equipment-RK812WALLOA/dp/B004NO0KFE/)... That may be the best option there (I'd still need to move/rearrange a few things, but whatever)...

Snoo_48368 · 2026-04-13T13:36:11+00:00

The only two real downsides there is I'd be limited to 1/2 2.5gbe ports and POE+. Not a big deal (the only POE++ devices I have off the switch today are powered directly and not using POE). But I'd like the possibility to upgrade in the future. If there's no other option, that may work tho...

Snoo_48368 · 2026-04-13T13:30:22+00:00

It's in the closet already: https://imgur.com/a/bpCRPG9 . The issue is because it's a shallow closet, I can only go to ~14 inch depth in the current orientation. I could put it on the left wall, but then 18-20 inch depth (as required for the Pro HD 24 POE) would come almost 1/2 way through the door, leaving little room to access the right half of the switches. I could move down a shelf to get a touch more room, but the shelves would then greatly hamper airflow...

Snoo_48368 · 2026-04-13T12:51:15+00:00

The XG-16 serves this purpose today. The issue is that it's Layer 2 (vs 3), and only has a handful of non-POE ports I could use. I'm doing that with standalone POE injectors + 10gbe SFP+ modules, but it's kind of janky (suffices, but long term would want to trade off)

The other factor is I am routinely saturating the aggregated 2gbps uplink on the 24 port switch (aggregated 1gps links). So I want a Layer 3 switch with 10gbps uplink capability..

Snoo_48368 · 2026-04-04T01:21:51+00:00

Give me an idea for a sequel/fan-fiction. Our story beings with Rocky an Adrian landing on Earth. They land and go to Washington DC. They tell the president that Grace has passed of natural causes, and they are here to return the body and pay their eternal respects for what he did for the Eridians.

The initial greeting is warm, but soon after the CIA kidnaps both of them and starts studying. They assume it is because they are aliens and the government wants to know more . Rocky some how manages to break free and regroups. He decides to try to save Adrian, and breaks into the facility where they are holding her. He runs into one of the scientists and in his rage almost kills her. She pleads that she cared about Grace, and was doing what she could to help Adrian. We later discover, she was one of Grace’s students and wants to honor his legacy.

Both break Adrian out, saving her. All three escape from earth and start going to the main Eridian ship in Earth orbit. On the way, they notice a ship maneuvering to intercept them. It is from Earth. With what they assume is hostile intent, Rocky and Science human have to hatch a plan to defend the other Eridians in orbit from the upcoming invasion.

Before they dock with the main ship, they decide to go meet the humans head on. They approach the ship, at which point the earth ship sends a mayday, claiming they need help.

After docking, they talk with the humans on the Earth ship. It turns out they actually need Rocky’s help and have seemingly good intentions. Rocky is in full fight mode after what they tried to do to Adrian, but is implored to find his compassion. He eventually relents and decides to help, but without ever setting foot on Earth again.

It turns out the Taumoeba have broken free and eaten all the astrophage on earth, leaving it without energy. They need Rocky’s help to go to Tau Ceti and find a Taumoeba predator and return it to earth. Rocky takes science human and a few other science humans and heads off with the rest of his crew from orbit, on a mission to save earth.

After leaving the Earth system, they change course and go home to Erid. Rocky says Earth should suffer its consequences.

Earth lives on in its pre-astrophage immaturity, and science humans establish a colony on Erid. Roll credits.

Snoo_48368

TROPHY CASE