spauka

Ironically, you've picked an example (Artemisinin) which is discussed at some length in the linked article - as an example where TCM success is overstated and not backed up by real-world results!

See P5-6 in section "The implausibility problem" - which points out that in order for the treatment to be effective it had to be refined into a form that is not rapidly eliminated from the body.

Without comment on the question of health benefits or harms, I'm curious whether you've had the well water you use tested. Fluoride concentrations in bore-well water varies quite widely, and concentrations higher than fluoridated tap water not uncommon. There are several areas here (in Aus) where fluoride is removed to reach the recommended concentration of 0.5-1.1 ppm. This obviously varies based on location.

Depending on how often you are refreshing - the status page only updates every 15 minutes:

> So I put together a simple shell script that runs from the crontab every 15 min, outputting some system stats to a basic HTML file in the webroot.

Raspberry Pi's RP2350 microcontroller introduced a multitude of new hardware security features over the RP2040, and included a Hacking Challenge which began at DEF CON to encourage researchers to find bugs. The challenge has been defeated and the chip is indeed vulnerable (in at least one way). This talk will cover the process of discovering this vulnerability, the method of exploiting it, and avenues for deducing more about the relevant low-level hardware behavior.

The RP2350 security architecture involves several interconnected mechanisms which together provide authentication of code running on the chip, protected one-time-programmable storage, fine-grained control of debug features, and so on. An antifuse-based OTP memory serves as the root of trust of the system, and informs the configuration of ARM TrustZone as well as additional attack mitigations such as glitch detectors. Raspberry Pi even constructs an impressive, bespoke Redundancy Coprocessor (RCP), which hardens execution of boot ROM code on the Cortex-M33 cores with stack protection, data validation, and instruction latency randomization.

Since there are many potential incorrect guesses to be made about where problems might lie, here I begin with the most fundamental features of the chip logic, including the reset process. Even small oversights at this level can entirely defeat sophisticated security efforts if higher-level mechanisms place complete trust in seemingly simple hardware operations. I show how cursory research into the design details of IP blocks used in the SoC can help inform an attack, and demonstrate the importance of fully testing new features which are built atop older IP. Ultimately, the significant amount of luck (or lack thereof) involved is a reminder of the need to meticulously understand and validate complex systems.

It seems like the summary of this article is: No

Encryption is mandated for data at rest and data in transit. There is a provision for encryption of data in use when homomorphic encryption becomes feasible, but the loophole referenced in the title is that it is not required now.

So ChatGPT didn't correctly summarize the text at all, this article does not talk about ethics at all, doesn't talk about potential uses and I would consider the statement about capturing context and incorporating knowledge from a wide range of sources to be a pretty poor summary of the text.

In fact I think that's a great example of exactly what is actually discussed, namely that the context that ChatGPT is able to hold is limited as it's context is held completely in its input. There is never any modification to it's internal state, we're just passing a longer input vector in to the start of the GPT-3 black box. For long inputs the embedding vector becomes more and more sparse and it needs to make more assumptions to fill in it's output.