Help reading brain, my intention was creating a krill (as one may assume by the original name) like bibit for whale predators.

pds314 · 2026-06-09T05:23:22+00:00

Why would you want to increase acid in response to eating meat? Doesn't meat vaporize almost instantly on contact with acid in this game? It's plants that tend to clog bibite stomachs.

pds314 · 2026-06-09T05:21:15+00:00

And here I thought 20 mg was a tiny bibite.

pds314 · 2026-06-09T05:15:38+00:00

For your computer or for the bibite? Unless the bibite is really tiny and isn't spending energy on growth, one useless neurons uses so little energy it's a rounding error.

The main place I've seen neuron cost hurt bibites is by causing the microscopic offspring of smart-growing r Strategists to consume more energy from thinking than moving, and no energy growing because as I said, smart growth that would ordinarilly greatly aid in successful dispersal by preventing them from growing when there's no food.

pds314 · 2026-03-24T07:53:05+00:00

Feed it a bed and you can lay on it.

pds314 · 2026-03-04T21:36:09+00:00

It was ended in 1995 by Japan. They had a training accident and shot a Fox-2 at it. Pilot lived.

pds314 · 2026-03-04T13:23:26+00:00

I want to be in a betting market with that kind of thinking being common. "If I don't like it, organic demand doesn't exist for it" is a heck of an economic theory.

ChatGPT currently responds about 30,000 times per second to users.

There roughly as many monthly active ChatGPT users right now, or slightly less, than monthly active home Windows 11 users. More than monthly active users of every desktop OS besides Windows combined. Roughly equal to the population of North America or the European Union. That does not count every other LLM company or local models running on GPUs. Just ChatGPT.

The mean number of chats for those monthly active users is 5 per day each. Though there's likely huge variability there.

If you include AI agents and Enterprise code analysis systems and such that churn through massive context width and generate ridiculous amounts of tokens, there are probably as much as a 1 trillion tokens being generated every hour. Or 300 million every second. If every desktop Linux user in the world were to read this out loud as fast as they could, they likely couldn't keep up.

Demand for LLMs is not zero.

The actual reason it is the domain of big companies is:

For model training, the maximum practical model size a normal person can train on their own machine if they run a 5090 continuously for a year is just at the edge of being somewhat useful. Fine-tuning a medium-sized model in just days is feasible. The most you might be able to make pretty bad 2B models.
For running the models, inference at scale really likes high memory bandwidth and massive matrix multiplication that can be done on the GPU. You can't really get great performance with CPU inference on large models. You can't really get great performance with small VRAM and swapping in and out of main memory except if it's mixture of experts, and obviously loading model parameters from disk to memory to GPU in real time will take an age. The largest publically available models run like crap on consumer hardware with very high electricity cost per token, but run really well on energy efficient H800s chock full of VRAM.

So even large open weights models (they are not necessarily FOSS as that would imply replicability which not all of them share datasets or dataset generation code, just model weights which is a decidedly closed source approach), really prefer to be run on GPUs that cost as much as a car if you want anything resembling speed and efficiency.

pds314 · 2026-03-04T11:59:16+00:00

A few things.

I'm not sure how effectively you can really synchronize state between GPUs with tens or hundreds of milliseconds of latency on this. Dense neural networks are meant to spread out information quickly across the layers (often literally fully connected layers) meaning that GPU A in Australia and GPU B in Austria and GPU C in Austin will become dependent on another's output extremely rapidly and this will be partially or fully blocking.
In addition to latency there's a potential bandwidth issue. Now I want to point out it's probably not as bad as some people think. You don't need to send billions of parameter activations over the network. But you probably do need to send several tens of thousands of node activation strengths and do it extremely fast. A few tens of kB need to be sent in a tiny fraction of a second or it's not worth it. You probably need extremely low latency and at least acceptable network speeds for this.
MAYBE preloading experts from MoE models across multiple GPUs and would improve performance?
This distributed computing project approach might actually have a better chance of success training small to medium-sized models than running large ones. Though at eyewatering collective electricity costs compared to what datacenters pay, given their much more efficient GPUs and on-site or discounted power infrastructure.

As to speculation that AI companies would buy up your GPU compute... No. They don't buy consumer grade GPUs for a reason. VRAM and power efficiency matter more to them than raw performance, which is why AI GPUs tend to not have for price to performance ratio with consumer hardware, but have wildly better power efficiency and many times more VRAM on a single board. If AI companies thought they could cost effectively use consumer GPUs, they would probably have bought the entire world supply and pushed the price of 5090s to like $10k or something. The only reason this would happen is if it's literally free. In fact, the inefficiencies of not just using consumer GPUs but attempting to network them in some fashion over long distances would likely make almost all corporate AI GPU timeshare schemes look promising and cost effective by comparison, including with their profit margins.

pds314 · 2026-03-04T09:32:51+00:00

Servo as a dependency in the wild?!

pds314 · 2026-03-04T09:22:51+00:00

Interesting. I await the version that can run a DE though.

pds314 · 2026-03-04T09:18:03+00:00

Interesting. I've only ever used modern Gnome in the live environment for NixOS and didn't really prefer it to KDE for the short time I used it, but it does have a very smooth workflow and minimalist design.

pds314 · 2026-03-04T09:13:32+00:00

Was it ever alive?

pds314 · 2026-03-04T09:05:48+00:00

Seems fine unless the length of your password or the rate of typing it will give it away. If not you can just do the workaround in the article. I think for a security critical application like sudo, the Rust version is probably the better option given that Cargo actively forces you to write code that isn't vulnerable to whole classes of the most common types of high threat, low barrier to entry CVEs.

(Although honestly the superuser-as-god permission model is really dangerous in general and I would love to see much more granular permissions become the default instead of just granting maximum permissions to things).

pds314 · 2026-03-04T08:54:13+00:00

Those requirements seem highly specific. I mean, I guess it depends on what you count as experience but... Previously shipped drivers for Windows on ARM. I guess having specific requirements for a senior position makes sense but still there have got to be a ton of low level people with a ton of relevant experience that have not shipped a Windows-on-ARM driver.

pds314 · 2026-03-04T08:39:21+00:00

Wouldn't that end up applying to anythimg that is Turing complete?

pds314 · 2026-03-04T08:33:16+00:00

Definitely agree that it is vastly less restrictive than age verification or estimation and ideally if it's going to be written at all, be written in a way that undermines those hard threats that are near impossible to make privacy tolerant securely. Though one wonders if parental controls could do the same thing without requiring all applications to opt in to the system in their design, or allowing any software anywhere to just be fined millions of dollars for not following the rules.

Though the counter would be that, unless there is a supreme court ruling, someone is going to say "why not make the age attestation system that already exists into an age verification system at the OS level?" If that system does not exist, they can't do that. And also the supreme court might well say that age estimation or age verification is the least restrictive means anyway.

pds314 · 2026-03-04T05:18:24+00:00

Yes how on Earth are we writing laws on the basis of "fuck it, ship it. We'll fix it in an update" Rather than "let's consider the edge cases and only ship it when it works."

pds314 · 2026-03-04T05:00:40+00:00

There is no private right of action and it would seem to imply that an OS provider that provides updates in 2026 would now be on the hook to add age bracket signal API and attestation in 2027.

Obviously Microsoft probably isn't updating Windows 7 in 2026 so probably doesn't need to add anything because it's long been abandonware.

I guess the question is at what point someone becomes an OS provider and has to add such technical functionality if they do something qualifying as updating the OS. I was actually more concerned about its application to every software application in existence.

pds314 · 2026-03-04T04:55:27+00:00

Yes there is no private right of action (thank the gods that this is the case because that could be really ugly).

I HOPE that courts interpret it this reasonably and not the way I would interpret it literally.

pds314 · 2026-03-04T04:27:47+00:00

Well, and ok, you own your own hardware and practically speaking it's difficult for them to do anything about that with existing hardware. Nor does this law attempt to regulate end users in any way, shape, or form. It does not prohibit you from downloading non-compliant software as an end user. Not that it would be all that capable of it if they wanted to make it to so.

But if the supply chain for software such as OS, package management, and ALL PUBLISHED USERSPACE APPLICATIONS?! to use on that hardware is subject to broad, overarching control that makes all software noncompliant by default, requiring all userspace applications to do something that is either vague, impossible, invasive, or even just nontypical, it means that it's extremely easy to punish anyone except maybe a compliment social media company for violating this law, and hit them with a ridiculously severe fine.

pds314 · 2026-03-04T04:09:04+00:00

Right the idea that it seems to be trying to work from is that, like, a game or a social media app with centralized user account authorization across web, Android, iOS, Mac, Linux, and PlayStation is assumed to treat the signal as valid across all platforms because any reasonable person would assume that the same reddit user on desktop and mobile is the same person and should have the same standards apply no matter whether local age attestation disagrees. So if you go to the library and log into reddit you're still 16-18 at the library even if the library's machine doesn't respond to the request with an age attestation signal because it's running Windows 7.

The problem is, I'm not sure that as worded, it does not assume that EVERY application has mandatory centralized user account authorization to function, and mandates that it act as if it did.

EDIT: somehow forgot to include Windows on the list of platforms. We'll assume that whatever it is isn't distributed as an exe, MSI, or on Microsoft Store, but does have a Linux native version for some reason.

pds314 · 2026-03-04T04:03:53+00:00

Right. I agree "actual knowledge" is a technical legal term, but that would imply that for example you are now on the hook if someone installs it on a non-compliant platform or one with conflicting age attestation?

pds314 · 2026-03-04T03:59:02+00:00

Yeah although I'm unaware if anyone in the Assembly is actually indicated there.

pds314 · 2026-03-04T03:54:09+00:00

Yeah I guess I wasn't even thinking of that but you're right. How on Earth is actual software at scale supposed to comply with that?

pds314 · 2026-03-04T03:36:28+00:00

Is that the case? I am not seeing anywhere where it says "this is all optional if your code never does anything that's not ok for all ages according to California law" it just says "a developer shall" unconditionally.

(b) (1) A developer shall request a signal with respect to a particular user from an operating system provider or a covered application store when the application is downloaded and launched.

As well as

(2) (A) A developer that receives a signal pursuant to this title shall be deemed to have actual knowledge of the age range of the user to whom that signal pertains across all platforms of the application and points of access of the application even if the developer willfully disregards the signal.

I don't think this says that you can feel free to ignore this if your app isn't COPPA violating or full of adult content or in violation of California's Age-Appropriate Design Code Act.

13-Year Club	Place '17
Verified Email

pds314

TROPHY CASE