We’ll if that’s not the pot calling the kettle black…

bombshell not the least bit surprising leak

I’ll usually stop and read them for apps that I like. I like knowing what’s changed.

The scene where they reference other movies is just establishing the in-universe rules for time travel. Specifically, that when they time travel, they’re actually traveling to a different branch of the “many worlds” tree of possibilities. This is a real theory that says that every time a quantum waveform collapses, what’s actually happening is that the universe is splitting into multiple copies, one for each possible outcome, so that all the possible outcomes actually happen. So their time travel is actually finding a different universe that is identical to the one they want to travel to. The in-universe consequence of this is that, since they’re going to a whole different universe, any changes made there don’t affect the universe that they came from.

It’s accurate in that the “many words” theory is a real (but unproven, possibly unfalsifiable) theory. It’s not accurate in that there’s no reason to think you could get from one universe to another. And maybe questionable that a universe identical to your own universe’s past actually exists as one of the many words.

It’s also internally inaccurate, since Steve Rogers travels to the past and then apparently just waits around to show up in the present again, which is exactly how they said it doesn’t work.

It combigated them.

I think that just makes it easier to use smaller amounts at a time.

I just hope that when the dust settles from all this hyperpartisan redistricting, enough voters will recognize it as a problem that we can push toward banning it nationally. Dare I dream of moving to proportional representation?

They’re really playing up the ominous tone.

“We know this because your IP address — xxx.xxx.xxx.xxx — was the first thing your device sent us. We know the rest of it. We chose not to display it. Most pages would not have made that choice. We did not ask for your location. Your address arrived before you did.”

Uh, yeah. That’s how IP addresses work.

Most of the time the front doesn’t fall off at all! Unless a wave hits it.

That’s got it, thanks!

Ok, I can import the file now, but some entries are getting messed up. This line, for example, shows up in the diary with the amount “NaNg · 722903 kcal”. And as much as I would like to eat Ginger Peanut Chicken until numbers fail to describe my gluttony, I just can’t afford that many calories.

Day,Group,Food Name,Amount,Energy (kcal),Alcohol (g),Caffeine (mg),Oxalate (mg),Phytate (mg),Water (g),B1 (Thiamine) (mg),B2 (Riboflavin) (mg),B3 (Niacin) (mg),B5 (Pantothenic Acid) (mg),B6 (Pyridoxine) (mg),B12 (Cobalamin) (µg),Folate (µg),Vitamin A (µg),Vitamin C (mg),Vitamin D (IU),Vitamin E (mg),Vitamin K (µg),Calcium (mg),Copper (mg),Iron (mg),Magnesium (mg),Manganese (mg),Phosphorus (mg),Potassium (mg),Selenium (µg),Sodium (mg),Zinc (mg),Net Carbs (g),Carbs (g),Fiber (g),Insoluble Fiber (g),Soluble Fiber (g),Starch (g),Sugars (g),Added Sugars (g),Fat (g),Cholesterol (mg),Monounsaturated (g),Polyunsaturated (g),Saturated (g),Trans-Fats (g),Omega-3 (g),ALA (g),DHA (g),EPA (g),Omega-6 (g),AA (g),LA (g),Cystine (g),Histidine (g),Isoleucine (g),Leucine (g),Lysine (g),Methionine (g),Phenylalanine (g),Protein (g),Threonine (g),Tryptophan (g),Tyrosine (g),Valine (g),Category 2026-04-20,"Lunch","Ginger Peanut Chicken","750.00 g",963.87,0.00,0.00,202.97,411.64,438.18,0.54,0.84,24.82,1.63,1.88,1.54,142.39,1074.55,62.64,2.52,4.13,39.04,547.85,0.77,12.70,252.20,1.97,913.92,2259.83,76.25,1861.40,6.73,38.20,55.08,16.50,12.52,1.88,9.13,17.86,7.79,45.73,236.74,16.68,10.61,7.96,0.08,3.19,3.15,0.02,0.01,6.92,0.05,6.82,0.88,1.93,3.15,5.60,5.57,1.68,2.96,85.62,3.14,0.78,2.56,3.38,"Meals, Entrees, and Sidedishes"

Also, there’s a bit of layout weirdness when reimporting days:

I gave this a shot, but when I press the “preview” button I just get a little popup that says “Invalid CSRF token”.

Half ands half.

If you’re going to work on CSV import anyway soon, then I’ll just wait. Thanks!

Rain, Rain, Beautiful Rain - Ladysmith Black Mambazo. Do recommend. Maybe not my top pick from them, but pretty good.

I have exports of my nutrition and weight info from other apps as csv files, and I’d like to import that data if I can. It looks like Nutritrace can export to csv but not import that. There is the option to import from a json backup though. If I can massage my data into that json format, does it seem reasonable to use that as a way to import my historical data?

If the answer isn’t “omg don’t do that”, then I have a couple of questions about the json:

• Does each item in the diary array require a matching foodList/meals/recipes entry? Or could I just generate items in the diary array?
• How much do I need to worry about IDs? The “import JSON” option says that it merges with existing data; how would it handle ID conflicts (which I assume could happen normally when exporting and importing anyway)?
• Are there any gotchas you can think of that I should watch out for?

This gets laughed out of court, right? Right?

All I had to do was run the pull command again.

I’m seeing “Could not reach server — retry” on the diary page and when going to enter foods. The diagnostics log has

[14:25:38.821] [ERROR] [diary] loadEntry error: _fetch@http://my.server:3000/assets/index-Dl7TTIk7.js:175:24686

[14:25:41.686] [WARN] [settings] direct push failed for startPage: Server responded 401
[14:25:41.689] [WARN] [settings] direct push failed for weightUnit: Server responded 401
[14:25:41.695] [WARN] [settings] direct push failed for heightUnit: Server responded 401
[14:25:41.699] [WARN] [settings] direct push failed for statsGoalLine: Server responded 401
[14:25:41.701] [WARN] [settings] direct push failed for lengthUnit: Server responded 401
[14:25:41.702] [WARN] [settings] direct push failed for distUnit: Server responded 401
[14:25:41.704] [WARN] [settings] direct push failed for statsYZero: Server responded 401
[14:25:41.705] [WARN] [settings] direct push failed for tempUnit: Server responded 401
[14:25:41.705] [WARN] [settings] direct push failed for usdaEnabled: Server responded 401
[14:25:41.706] [WARN] [settings] direct push failed for statsAvgLine: Server responded 401
[14:25:41.708] [WARN] [settings] direct push failed for offSearchCountry: Server responded 401
[14:25:41.708] [WARN] [settings] direct push failed for offUploadCountry: Server responded 401
[14:25:41.709] [WARN] [settings] direct push failed for offSearchLanguage: Server responded 401
[14:25:41.710] [WARN] [settings] direct push failed for statsTrendLine: Server responded 401
[14:25:41.710] [WARN] [settings] direct push failed for statsChartType: Server responded 401

Looks good, so I’ve got it up and running now. Thanks!