So there would need to be standard defined, whereby the exe would basically embed a "protobuf" definition in it's header area, and then a maximally sized "message" could be tacked on to the end of the exe. In the Explorer>file-Properties screen, there could be a config tab that shows the current config (and maybe allows direct editing), plus buttons for import/export/clear config. And as part of the standard, options could be defined as public/shared or private, and thus private fields would get encrypted by the OS/TPM, which means sharing an exe with sensitive info embedded would "not be a risk". The config tab could even have a "meta" option for things like "config changes update this executables modified date" (again for the sync/backup aspect).

* ini spawning programs include CPU-Z, HWMon, HWiNFO, BulkRenameUtility, HxD (newer versions spawn a settings folder), seemingly every NirSoft + O&O tool - and the master of all spawners: explorer.exe dropping desktop.ini's.

  # make a 6 second long video that alternates from green to red every second.
  ffmpeg -f lavfi -i "color=red[a];color=green[b];[a][b]overlay='mod(floor(t)\,2)*w'" -t 6 master.mp4; # creates 150 frames @ 25fps.

  # try make a 1 second clip starting at 0sec. it should be all green.
  ffmpeg -ss 0 -i "master.mp4" -t 1 -c copy "clip1.mp4"; # exports 27 frames. you see some red.
  ffmpeg -ss 0 -t  1 -i "master.mp4" -c copy "clip2.mp4"; # exports 27 frames. you see some red.
  ffmpeg -ss 0 -to 1 -i "master.mp4" -c copy "clip3.mp4"; # exports 27 frames. you see some red.

  # -t and -to stop after the limit, so subtract a frame. but that leaves 26...
  # so perhaps offset the start time so that frame#0 is at 0.04 (ie, list starts at 1)?
  ffmpeg -itsoffset 0.04 -ss 0 -i "master.mp4" -t 0.96 -c copy "clip4.mp4"; # exports 25 frames, all green, time = 1.00. success.

  # try make another 1 second clip starting at 2sec. it should be all green.
  ffmpeg -itsoffset 0.04 -ss 2 -i "master.mp4" -t 0.96 -c copy "clip5.mp4"; # exports 75 frames, time = 1.08, and you see red-green-red.
  # maybe don't offset the start, and drop 2 at the end?
  ffmpeg -ss 2 -i "master.mp4" -t 0.92 -c copy "clip6.mp4"; # exports 75 frames, time = 1.08, and you see green-red.
  ffmpeg -ss 2 -t 0.92 -i "master.mp4" -c copy "clip7.mp4"; # exports 75 frames, time = 0.92, and you see green-red.
  
  # try something different...
  ffmpeg -ss 2 -i "master.mp4" -c copy -frames 25 "clip8.mp4"; # video is broken.
  ffmpeg -ss 2 -i "master.mp4" -c copy -frames 25 -avoid_negative_ts make_zero "clip9.mp4"; # exports 25 frames, all green, time = 1.00. success?
  # try export a red video the same way.
  ffmpeg -ss 3 -i "master.mp4" -c copy -frames 25 -avoid_negative_ts make_zero "clip10.mp4"; # oh no, it's all green!

Have you got an ancestor that was born in Canada? [1]

It sounds like that a child of a "red coat" born on the lands that would become Canada is sufficient... [2]

[1]: [Heads Up: Canadian Genealogy is about to get VERY popular!](https://old.reddit.com/r/Genealogy/comments/1qqkzte/heads_up...)

> On December 15, 2025 Canada enacted "Bill C-3", granting citizenship to people born before Dec. 15, 2025 with ANY level of Canadian ancestry they can document. (It used to be a "first generation limit")

[2]: https://old.reddit.com/r/Genealogy/comments/1qqkzte/heads_up...

> ancestors domiciled in the former colony of Newfoundland are still considered as Canadian born or naturalized for the purpose of citizenship by descent.

I'm far from an expert, yet I came to believe that what you've described is basically "code smell". And the smell probably comes from seemingly innocuous things like enum's.

And you wondered if the solution was using Go, but no, it isn't. I was actually Go at the time myself (this was a few years ago, and I used Twirp instead of Protobuf) - but I realised that RDBMS > "Server(Go)" layer had quirks, and then the "Server(Go)" > "API(JS)" had other quirks -- and so I realised that you may as well "splat" out every attribute/relationship. Because ultimately, that's the problem...

Eg: is it a null field, or undefined, or empty, or false, or [], or {}? ...

[] == my valentines day inbox. :P

* Toxicity resulting from lack of monitoring is frequently seen in patients requiring high doses to treat ailments like osteoporosis, renal osteodystrophy, psoriasis, gastric bypass surgery, celiac, or inflammatory bowel disease.

* Patients who are on high doses of Vitamin D and taking inadvertently increased amounts of highly fortified milk are also at increased risk for vitamin D toxicity.

* According to the latest report from America's Poison Centers (APC), there were 11,718 cases of vitamin D exposure recorded in the National Poison Data System. More than half of these cases were in children younger than 5 years.

* The clinical signs and symptoms of vitamin D toxicity manifest from hypercalcemia's effects.

* Clinical management of vitamin D toxicity is mainly supportive and focuses on lowering calcium levels.

* Isotonic saline should be used to correct dehydration and increase renal calcium clearance.

A lot of those point to people drinking too much milk! (enriched milk)

* People with osteoporosis thinking "I better drink more milk for strong bones" when they are already on supplements/medicine.

* Kids drinking lots of milk and presumably not drinking any water - hence the dehydration.

PS: There are a lot of people out there that don't drink any water, and stick to juice or milk or soda, etc. They are not always fat, but that doesn't mean they don't have issues.

> A statistical error in the estimation of the recommended dietary allowance (RDA) for vitamin D was recently discovered; in a correct analysis of the data used by the Institute of Medicine, it was found that 8895 IU/d was needed for 97.5% of individuals to achieve values ≥50 nmol/L. Another study confirmed that 6201 IU/d was needed to achieve 75 nmol/L and 9122 IU/d was needed to reach 100 nmol/L.

> This could lead to a recommendation of 1000 IU for children <1 year on enriched formula and 1500 IU for breastfed children older than 6 months, 3000 IU for children >1 year of age, and around 8000 IU for young adults and thereafter. Actions are urgently needed to protect the global population from vitamin D deficiency.

> ...

> Since 10 000 IU/d is needed to achieve 100 nmol/L [9], except for individuals with vitamin D hypersensitivity, and since there is no evidence of adverse effects associated with serum 25(OH)D levels <140 nmol/L, leaving a considerable margin of safety for efforts to raise the population-wide concentration to around 100 nmol/L, the doses we propose could be used to reach the level of 75 nmol/L or preferably 100 nmol/L.

I guess you could compare them as if they are API's to different LLM's, and my "consciousness" is the web-browser. So it's like;

  - `fast_facts.llm` is a micro model with good breadth and fast response times, but it has little depth. So it's API can be fetch'd without worrying about it blocking the main-thread/browser.  
  - `all_data.llm` is a full size model, but it's slow to respond, and "costs" more to run. So in the browser, it is only lazily-loaded (ie, not always used), and it has to be called async style because you have to wait for the results to slowly "stream in".

Continuing with the post-it-note analogy, the note can only hold a small amount of information, and so the grudge will be recorded as something simple like "fuck ___, they're an arrogant twat". So then the situation arises where you're talking to someone else and they ask "what do you think about ___?"; and so you answer "I can't stand them, they're so arrogant"; to which they respond "oh really, how so?"; and you can't give an answer, because it wasn't written on the note.

I think this ties in with memories not making you feel the relevant emotions, because the emotion you felt was also just saved as a "fact". I have found though that if I step through all the facts of an "event" and consider each "moment" along the way, that I can often generate the relevant emotion. So say I was remembering an argument, I can remember various facts about the argument and that I was angry about it, but I can't feel that anger. But if I walk through the moments, like `they said this, which made me think that, to which I rightly responded with...`, then eventually I'll start to feel angry just like I would have.

For an analogy on how I think memories are stored differently: then for non-aphantasiacs, I reckon their brain must save `memory.zip`, which contains `video, audio, smells, emotions, etc`. For a person like myself with aphantasia however, it's like I asked ChatGPT for a summary of `memory.zip`, and then I only saved the summary.

Saying that though, I do wonder about the connection between "fact based memories" and aphantasia's lack of mental imagery. Because if >50% of the usefulness of `memory.zip` is from the video, but you can't "see" the video because you aphantasia — then has your brain decided/learned to not bother saving `memory.zip` and instead just save the summary, or are all components of `memory.zip` also corrupt/unplayable?

I don't think the article is referring to that sort of issue, which sounds fundamental to the task at hand (calculations etc). To me it's about making the code flexible with regards to future changes/requirements/adaptions/etc. I guess you could consider Y2K as an example of this issue, because the problem with 6 digit date codes wasn't with their practicality at handling dates in the 80's/90's, but about dates that "spanned" beyond 991231, ie 000101.

You said the right words but with the wrong meaning! On Gigabyte mobo you want to increase the "CPU Vcore Loadline Calibration" and the "PWM Phase Control" settings, [see screenshot here](https://forum.level1techs.com/t/ddr4-ram-load-line-calibrati...).

When I first got my Ryzen 3900X cpu and X570 mobo in 2019, I had many issues for a long time (freezes at idle, not waking from sleep, bios loops, etc). Eventually I found that bumping up those settings to ~High (maybe even Extreme) was what was required, and things worked for 2 years or so until I got a 5950X on clearance last year.

I slotted that in to the same mobo and it worked fine, but when I was looking at HWMon etc, I noticed some strange things with the power/voltage. After some mucking about and theorising with ChatGPT (it's way quicker than googling for uncommon problems), it became apparent that the ~High LLC/power settings I was still using were no good. ChatGPT explained that my 3900X was probably a bit "crude" in relative quality, and so it needed the "stronger" power settings to keep itself in order. Then when I've swapped to 5950X, it happens to be more "refined" and thus doesn't need to be "manhandled" — and in fact, didn't like being manhandled at all!