What is causing all the Metabolic Dysfunction? @Paul Saladino MD thinks it is linoleic acid in the mitochondria. If linoleic acid is a problem, then the following foods are bad for you: wheat, corn, walnuts, soy, sesame seeds, pumkin seeds, rice, pistachios, almonds, canoia oil, commercial chickens, peanuts, ... all of which the fat portion has >20% LA. Even egg yolks are 16%. It is hard for me to believe that the natural foods in that list are causing the metabolic problem. My hypothesis is that humanity's romance with chemistry has produced thousands of variations of endocrine disruptors which are now all throughout or food, water and soil, and especially in plastics. People know about BPA, but all those "BPA-free" plastics just have different endocrine disruptors, possibly much worse ones. You can improve by sticking to natural and organic foods and using glass containers. But you can't eliminate your exposure. Of cousre these are both just hypotheses with no good evidence behind them.

Warning: Do not search for "bitcoin" in any nostr client. Your client may not give you back control of your computer.

Conductor (related to Chorus) Every few days somebody posts an "Introducing ___" note to nostr, where they tell everybody about their new project that they have been working on for ages and finally have released. These are exciting and very cool. I'm a little different. I'm gonna tell you want I'm working on before it is ready. For a couple weeks I've been working on a web application called "conductor" (like that guy who swings a baton at an Orchestra). It is a relay management tool using NIP-86. I know there are a few others in development by other people, but it was time for me to get better at writing web applications and it seemed like I could get one working in just a few days (after the first day I felt like I was halfway there). Also, being the chorus developer I can adjust both sides until it does all the right things, which makes it easier to make progress. In the process of developing conductor, I ran into issues with chorus and AUTH and have worked to get them resolved.

GitHub

Unclear nip-42 auth spec and/or behavior · Issue #163 · nostrability/nostrability

https://njump.me/nevent1qqs25grkfk6w0hq5l57h5v57yv29pqrc5czd4y2k9dvhwzxcw9edd4gm9vldg I'm not sure exactly, but I think it has to do with how the A...

GitHub

Add 2 prefixes, and define them all by mikedilger · Pull Request #1778 · nostr-protocol/nips

Here I'm proposing 2 new prefixes: deleted - for EVENT, when the relay rejects the event because it has been deleted redacted - for CLOSED, wh...

GitHub

AUTH issues between nostr-sdk (rust) and chorus · Issue #167 · nostrability/nostrability

client initiating action Custom client using nostr-sdk relay receiving or observing action (or lack thereof) chorus what happens At a high level, t...

Also, a number of breaking changes had to happen to chorus (such as moving user configuration into the database so it could be dynamic) prompting me to prepare towards releasing a Chorus 2.0 which requires a small amount of migration. This is not ready yet, I'm just telling you what I am in the middle of doing. Conductor will start out very basic, and while it will work with chorus relays it might not work with other relays as NIP-86 might not have the commands I was interested in. It won't work with 1984 reports yet either (but that is coming). It will just allow approving (or rejecting) events and pubkeys that haven't been approved yet using the same scheme chorus already uses with the `chorus_moderate` command. I will release it when this is all it does. I will release it again once you can manage users with it. And I will release it again once it handles 1984 reports too. One step at a time.

EAT REAL FOOD I'm more confident in that advice than any other dietary advice. Bickering about carbs versus fat or plants versus meat is relatively minor. Humans thrive off of all sorts of crazy real-food diets including eating only fish and their guts, or living on only milk and blood, or eating mostly honey and boiled roots. But we do not thrive on aspartame. View quoted note →

I love my new Flair Neo. Yes, it takes 8 minutes and dirties all the dishes to make a single espresso milk drink... but it tastes just like (or even better than) the cafe. 1) Boil water 2) Setup the frame 3) Grind 14g of coffee (Karajoz or Jed's 4 or Ebony Windy Ridge or any good dark but not burnt roast) 4) Funnel into the portafilter and tamp, putting screen on top 5) Place in the frame 6) Put metal sleeve in bowl and cover in hot water to preheat 7) Pour 250g of milk into french press, and microwave on high 1:40 8) Get a coffee cup under the machine 9) Get a second coffee cup ready to catch the drips 10) Place sleeve on machine, fill with hot water 11) Insert plunger 12) Press down lightly and leave 30 seconds to pre-infuse 13) Press hard (well, 9 bar, not crazy hard) and less hard over time until the bar is at the bottom, the coffee is now in the cup 14) Remove cup, swapping for the drip cup 15) Get milk from microwave, froth with french press screen (20 times fast, but not deep) 16) Pour into stainless milk device 17) Bang on table so I look like I know what I am doing 18) Slowly pour milk into coffee and make a nice design on the top 19) Leave the mess behind for later, taking the coffee to the computer 20) After coffee has been drunk, bring coffee back to kitchen 21) Wash coffee cup in the sink 22) Remove sleeve and portafilter from frame, and separate them 23) Separate and wash the screen, portafilter, heavy metal sleeve, and plunger 24) Fold up frame, put it back in the box 25) Remove drip cup and wash it 26) Wash preheating bowl 27) Wipe coffee grounds off of the counter 28) Wait for all the dishes to dry 29) Place all parts into the box, close up, and put away It is so easy!

I think I'm going to change chorus to send "CLOSED: auth-required" upon ANY event needing redaction from the results. It is too complicated with various existing clients to silently redact or signal redaction, and many expect this "auth-required" signal to know they need to AUTH. For a long time I thought giving people partial results was at least a little bit helpful, now I think it is harmful. If you think I'm wrong please stop me.

2024 YR4 now has a 2.6% chance of striking Earth and wiping out a city-sized area. I'm looking forward to finding out which city God is going to obliterate first.

I discovered this track on a compilation CD in London many years ago now. It never became popular, except in my own collection.

Damn power outage!