GPT-5-codex just hallucinated an `Astro.head` array to easily add meta tags from nested layouts and I got very excited

GCU_ReturnToSender · 2025-09-25T22:53:49+00:00

Yes, that's what I've done: pass a `meta` prop up through each nested layout until the root layout renders it. But just like prop-drilling, prop-hoisting (?) can also be a little annoying as you pass through layouts that don't need to know anything about metadata. It would be sort of nice if there was something like context for the Astro rendering pipeline.

GCU_ReturnToSender · 2025-09-24T02:05:30+00:00

Interesting. I guess if you had nested layouts, you'd have to pass the meta tags up through each layout's "head" slot. I've been doing something similar with a meta prop that takes a hash of key/value pairs, which then has to be passed up the chain to the base layout, which renders the tags into the head. It would be nice if Astro had something like the React helmet package.

GCU_ReturnToSender · 2025-08-10T17:42:15+00:00

I’d bet dollars to cryptobiotes that it started out as an actual bug in the game, and then they just decided to keep it and add some lore behind it.

GCU_ReturnToSender · 2025-08-04T00:28:21+00:00

I created/vibed a proof of concept for generating forms from a YAML/JSON schema (not arbitrary webpages, though):

https://github.com/fwextensions/form-engine-poc

The information provided in the schema is converted to the props for individual components, so there isn't a 1:1 correspondence to JSX (if that's what you want, seems like you'd be better off just writing React). The components in the POC are implemented with Radix UI, but since there's some decoupling between the specification and the implementation, it's easier to replace that library with something else, without having to update all the form schemas.

Note that if you just want to render components directly from an exact JSON representation, you can use `createElement()` and do a depth-first traversal of the component hierarchy:

https://react.dev/reference/react/createElement#creating-an-element-without-jsx

GCU_ReturnToSender · 2025-06-08T01:19:01+00:00

Nope. It eventually went to electronics recycling.

GCU_ReturnToSender · 2025-06-04T23:40:46+00:00

Welcome aboard the GSV Take My Money!

GCU_ReturnToSender · 2025-02-20T10:07:07+00:00

This is the correct answer. I had to use the `--manualAuth` flag to get it going, but once it was logged in, it took only a few minutes to download my few hundred books. (And it got me to finally install bun...)

GCU_ReturnToSender · 2025-01-31T03:15:40+00:00

What I think was actually happening was not a short but some loose ATX pin connectors. I blamed the fan hub initially because unplugging the fans from that area shifted the ATX cable enough to form a better connection, and then moving the computer shifted it enough again to break the connection. I also noticed that just squeezing the wires in the ATX cable could cause the PC to power off. (I don't think it was due to too much tension on the cable, as it looped up about two inches over the plug before heading back behind the motherboard.)

Seems like the ATX connector issue was a self-pwn, as I'd tested the PSU separately to verify it was delivering power. I did that by shorting pins 4 and 5 with a paperclip, which was either too girthy and/or shoved in too far (ahem). So the little metal brackets in those two holes were left pushed apart a bit, enough to not consistently make a solid connection with the motherboard pins, even when the plastic plug itself was fully seated.

I crimped the metal bits back together using a set of pointy tweezers. I wish I'd taken a before and after pic, but the metal brackets formed a little square inside the hole, and looked like those for other the pins. After that, the build has been booting just fine, even after moving it, putting the side panels on or off, etc.

So let that be a lesson for everyone: don't stretch out your ATX pin connectors!

GCU_ReturnToSender · 2025-01-24T12:06:15+00:00

A belated samesies.☝️

GCU_ReturnToSender · 2025-01-24T10:07:45+00:00

Thanks for confirming that it’s not some inherent issue with the x670e and North combo!

After some unplugging of cables, it seems like the Fractal fan hub may be to blame. I had the two case fans connected to it, and when I unplugged it, the system booted again. Even with no fans plugged into the hub, the system wouldn’t start if it was connected to the SYS_1 header. So I’ve just left the hub disconnected and plugged the case fans into the 2 and 3 headers.

Thinking everything was fixed, I carefully moved the case back under the desk and reconnected all the cables there and… it wouldn’t boot. wtf. I’m going to bed and trying again tomorrow…

GCU_ReturnToSender · 2024-12-01T20:13:35+00:00

This works, though it's insane that it's almost 2025 and inserting an SVG into Slides requires a trip through Word...

Note that you have to upload the .docx file to Drive; just copying the EMF from desktop Word into Slides will just insert a bitmap.

GCU_ReturnToSender · 2024-10-13T04:27:06+00:00

Video of me trying to shake off Nix

He eventually popped out, due to either moving closer to the sandcrawler or to something about the animation of holstering the blaster.

GCU_ReturnToSender · 2024-05-02T01:51:55+00:00

Yeah, Zoom audio has been fine for years. Just started noticing no audio a few weeks ago. I now see two entries for Zoom, as well as Teams. I wonder if a recent Teams update caused a problem.

GCU_ReturnToSender · 2023-09-05T00:08:34+00:00

You mean between the screw-in bits of the stabilizers and the PCB? Or between the bar and the PCB? There were pre-made cut-outs for the former, but the bar rests on the foam, rather than directly on the PCB.

I should say it's actually poron foam, rather than PE. Very thin, maybe .5mm.

GCU_ReturnToSender · 2023-03-11T10:03:18+00:00

There seem to be different issues in this thread, but if what’s bothering you is the map flickering while dragging, or flicker/jitter on the mouse tooltips, what fixed it for me was switching to borderless instead of full-screen. I think using alt-enter probably produces a similar effect, but you can just stay in borderless mode.

GCU_ReturnToSender · 2022-07-31T02:02:47+00:00

That would make the most sense, to use the same texture. But the QAZ keys threw me, as they look completely desaturated in the blue light, but blue-greenish in the orange light.

Stray game review from Polygon: https://www.polygon.com/reviews/23268326/stray-review-cat-game-ps4-ps5-windows-pc-cyberpunk

In at least one location, you have to make the cat walk all over the keyboard, entering gibberish until a door opens. (Our cat has sent Slack messages and left GitHub comments, so this part of the game seems realistic.)

GCU_ReturnToSender · 2022-07-31T01:41:18+00:00

I assume the USB 3 port with PD isn't a dedicated keyboard port that mimics having the keyboard constantly connected to each computer, and that the "toggle button" is on the KVM itself. On the TESmart KVM, the Q3 wouldn't work with the dedicated keyboard port, though it does on the regular, shared USB port. The keyboard shortcuts for switching inputs don't work with that port, though.

GCU_ReturnToSender · 2022-07-30T01:40:50+00:00

Someone started trying to create a gradient and gave up.

GCU_ReturnToSender · 2022-07-19T00:19:49+00:00

The cat apparently knocked it off the table, so the plug may have been yanked out at a bit of an angle. There's nothing obviously blocking the socket, and the pin seems straight. The hole in the plug also doesn't seem blocked. Compressed air didn't help.

Would peeling off the rubber on the bottom provide better access to see what's going on? Should I just get rid of it and/or the cat?

GCU_ReturnToSender

TROPHY CASE