This is basically telling Claude "Make Resizable Bar work on my RTX 3080" and publishing the summary of the conversation.
For context, the RTX 3080 got ReBAR support with a VBIOS update. Some models ship with an updated VBIOS that supports it, some don't. The author's didn't.
The GPU manufacturer only provides Windows executables to update the VBIOS, the author's on Linux.
There is some valuable exploration (e.g. the mismatch in supported args in nvflash on Windows vs Linux) and just about as much information that is only useful on OP's machine (e.g. Ollama and LightDM are stopped before flashing, which is great if you happen to use either of those) or not useful at all (e.g. the word-soup-slop of diagram after diagram including "CPU Overhead Breakdown" -- what are we doing here?)
The topic is interesting and you have my thanks for taking the time to look into it and prepare the post. Would you say it's fair to say that if you didn't use LLMs to prepare the post, we would have no blog post at all?
In that case, I think I lean more towards being OK with this usage of LLMs, as I'd rather have this content available than not. However, I can only read that one repeated sentence about "booleans" (Ctrl-F "Boolean" and you'll know what I mean) this many times before I start questioning the validity of the entire document. It is not _good_ writing, to be frank.
> Only the current audio/video frame is being sent to the viewers, there is no way they can download/cache the videos either for future usage.
This seems misleading, though. I think I get what was meant: clients can't send a request to download from the start or a specific offset and thus "download" the original file, the server is in charge of what's being sent. However, clients can still capture the frames, save them, and replay them, obviously. And I see a button to "Seek", so...
I'm only YouTube-level informed on how silicon manufacturing works, but something that is, perhaps intentionally, not made clear to someone unfamiliar with the field is that this is not manufacturing chips in space. This is to grow the crystals only, the very first step in silicon chip manufacturing. This is how you get the ingot, then you slice it to get the wafers upon which the chips are built. The reason you would even consider doing it in space in the first place is because, on Earth, gravity and other forces are stronger and result in lower-purity crystals. Basically, what I'm getting at, is that I believe this is pretty much a glorified oven. Moving the entire manufacturing process in space wouldn't make sense, as I don't think the benefits to other steps of the process like CVD would outweigh the insane costs of sending things into orbit.
I was going to switch to Waterfox in light of this news, but a cursory search revealed that it, too, was sold to an advertising company not long ago. While they have published a blog post opposing Mozilla's AI stance, I'm really past the point of giving ad companies any benefit of the doubt.
I'm looking into Librewolf now.
Can you imagine someone willing to do those things because of some reason other than monetary gain, as it would be in OP's world?
How many people currently stuck in Jobs would work toward accomplishing these things with the idea of ending world hunger, because they _want_ to do it, instead of having to do it because they have student loans and bills to pay?
I suppose the difference is that you only have to rush to claim your domain name (the DNS kind) once and then you get to use it for all "open social" platforms rather than doing that for your username on each platform.
For context, the RTX 3080 got ReBAR support with a VBIOS update. Some models ship with an updated VBIOS that supports it, some don't. The author's didn't.
The GPU manufacturer only provides Windows executables to update the VBIOS, the author's on Linux.
There is some valuable exploration (e.g. the mismatch in supported args in nvflash on Windows vs Linux) and just about as much information that is only useful on OP's machine (e.g. Ollama and LightDM are stopped before flashing, which is great if you happen to use either of those) or not useful at all (e.g. the word-soup-slop of diagram after diagram including "CPU Overhead Breakdown" -- what are we doing here?)
Thanks for sharing, anyway.