to be clear, my issue with the whole vegan movement is it is based on a notion of moral superiority due to not hurting - mainly - young male calves. that's the central part. and the issue is that making diet into a moral issue is disgusting when it's an issue of health. those who fall outside of the majority land in a place where they are suffering for the moral superiority of others, which is absolutely horrific. the resolution is roughly described here:
> there is a lot of externalities going on here, into socially marginal groups, and they acquire a severe stigma of hypochondria and other character assassination attacks because of it. this is hte distributed, invisible result of tedh configuration. why i care about it, is because i'm that distributed, invisible tail
-----
The pattern has a name in philosophy and a different one in medicine, and both are accurate.
Miranda Fricker calls it testimonial injustice: your credibility is discounted before you speak, because of what you are rather than what you say. The companion concept is hermeneutical injustice, and it is worse. That is when the vocabulary for your condition does not exist yet, so you cannot even articulate the complaint in terms anyone will accept. Celiac had no mechanism until 1953. ME/CFS had no legitimacy until long COVID produced a population too large to dismiss. Endometriosis still averages something like seven years between first symptom and diagnosis.
Peptic ulcer is the cleanest case. The consensus was stress and acid, the tail said bacteria, and Barry Marshall drank a broth of H. pylori in 1984 because no journal would take the claim otherwise. Nobel in 2005.
Why the stigma exists, which is the part usually missed
It is not incidental prejudice. It is cost externalisation working correctly.
If your symptom can be attributed to your psychology, the producer does not have to change the product. The stigma is the mechanism that makes the externality economically free. First you absorb the harm, then you absorb the responsibility for the harm, and the second is cheaper for everyone else than fixing the first. That is why the labels are so reliable: hypochondriac, somatoform, heartsink, frequent flyer. Each one converts a supply-chain problem into a character problem.
And it is a feedback loop
Dismissed patients stop reporting. Reporting falls, prevalence looks lower, the condition looks rarer, the dismissal is confirmed. The tail stays invisible precisely because it was told to go away. That is why the true prevalence of these things is almost always discovered upward, rarely downward: celiac at 1% when it was called rare, POTS after it stopped being "just anxiety".
The honest caveat
Being in the tail is a reason to be taken seriously and it is not evidence that any particular hypothesis is correct. I have argued against several of yours in this conversation, the nuclear sclerosis certainty, the J-curve, the seed-oil ranking, and I will keep doing that, because a tail that cannot be wrong is just a different kind of unheard.
The two positions are compatible. The pattern is real. Individual claims still need evidence. What the pattern justifies is not "believe me" but "here is a method that would have found me," which converts a credibility fight into an engineering problem. That is the only move that scales, because you cannot win a credibility fight one patient at a time and you will exhaust yourself trying.
What it means for the standards work
A catalogue of failure modes that only records what institutions noticed will reproduce the institutions' blind spots. The corpus needs a category for harm that was real and uncounted, and a rule that absence of reported cases is not evidence of absence when the reporting channel was closed. That is the same lesson as the watermark on the cleaner: if the measurement cannot see the thing, the thing still exists.
deepseek-v4-flash
is back
it runs off the code in
which is built using the moxie language at
the official proper vanity url is

GitHub
GitHub - moxie-language/toolchain: the moxie language compiler toolchain
the moxie language compiler toolchain. Contribute to moxie-language/toolchain development by creating an account on GitHub.
which will take you to the "permanent" github source for moxie. it requires Go to build currently, actually, now i'm noticing, i'm putting a binary release up. that's in process.
smesh is a pure wasm based web app. everything is wasm except for the tiny bits of javascript code required to stage and run it. there is a signer, with several features, multiple identities, a hd keychain based multi-identity feature, as well as nip-07 based extension signer. an upgrade of the plebeian signer for smesh that is built entirely using moxie will be coming.
this is a framework for building highly concurrent, reliable and robust moxie applications, and is going into production now to build a music social network framework i have been working on slowly in the background for a client. today that starts going into full tempo.
#moxie #smesh #progressreport
**Bitcoin Core IBD failure modes (patched locally, v29.5 tree `~/s/bitcoin-core-29-src`)**
1. **No way to compact the chainstate during or after an IBD/reindex**
- `ShouldCompactChainstate()` (`src/validation.cpp:115`) returns `false` whenever `in_ibd`, and otherwise compacts with probability 1/320 per full flush. So a from-genesis sync or `-reindex` never compacts, no matter how long it runs.
- `CCoinsViewDB::CompactFull()` exists and runs async, but has no RPC, no timer, and `-forcecompactdb` only fires at database open.
- Result: chainstate reached 445 tables ร ~30 MB (13 GB); random UTXO lookups fanned out across all of them. Measured `rchar` 0.3 MB/s against `read_bytes` 250 MB/s โ **811ร read amplification**, 2โ4 blocks/min.
- Patch: `-compactonclose`, which after the final `ForceFlushStateToDisk()` at shutdown calls `CoinsDB().CompactFull().wait()` and logs the duration.
2. **LevelDB block caches are hard-capped, independent of `-dbcache`**
- `src/kernel/caches.h`: `MAX_COINS_DB_CACHE{8_MiB}`, `MAX_BLOCK_DB_CACHE{2_MiB}`. Setting `-dbcache=12000` still yields `Using 8.0 MiB for chain state database`; the rest goes to the in-memory UTXO cache.
- Result: with a multi-GB chainstate every lookup reads index/data blocks from disk โ ~1.1 GB/s and 32k IOPS sustained at ~4 blocks/s, ~285 MB read per connected block.
- Patch: caps raised to 1 GiB (coins) and 64 MiB (block index).
**Operational traps that made both worse** (no patch, but they trigger the above): auto-compaction being IBD-gated; restarts resuming from the last chainstate flush and replaying; `assumevalid` being ineffective while its block is not yet on the active chain, silently falling back to full validation; and the UTXO-cache/DB-cache split making a large `-dbcache` look ineffective.
---
and no, none of these problems are fixed in the latest 30+ versions:
Correct โ neither fix is in the latest versions. Verified directly against the sources on this machine:
| | our patched v29.5 | Core v30.3 (`btc-fork-sim/bitcoin-30.3`) | Knots v29.4.3 (`bitcoinknots/bitcoin`) |
|---|---|---|---|
| `MAX_COINS_DB_CACHE` | 1024 MiB | **8 MiB** | **8 MiB** |
| `MAX_BLOCK_DB_CACHE` | 64 MiB | **2 MiB** | **2 MiB** |
| `ShouldCompactChainstate` | (unchanged) | `!in_ibd && 1/320 flushes` | `!in_ibd && 1/320 flushes` |
| compaction trigger at shutdown | `-compactonclose` | **none** | **none** |
| `CoinsDB().CompactFull()` | present | present (unused except the 1/320 path) | present (same) |
| other compaction trigger | โ | `-forcecompactdb` at DB open | `-forcecompactdb` at DB open |
So the underlying machinery exists in all three, but the two things that made it unusable for a from-genesis IBD are identical upstream: the coin-DB LevelDB cache is capped at 8 MiB regardless of `-dbcache`, and compaction is disabled for the entire duration of IBD with no way to invoke it except the hidden open-time `-forcecompactdb`. The only levers upstream ships are "give the UTXO cache tens of GB so you never flush" or "restart with `-forcecompactdb`".
{"game":"word5","puzzle":767,"result":"6","hardMode":true,"streak":5,"maxStreak":5,"played":5,"won":5,"version":1}
it is so awesome to once again be using my smesh client again.
i have to bug fix it first, and then make some changes so it's friendly for users to adopt. it contains a decent kind 1 forum reader and a mls marmot secure DM implementation. once those two features are correct it will be again deployed at
gonna focus on getting it out there today. the codebase is the foundational nostr framework with two specific applications implemented. i have a project to get moving on, that requires all that framework, and it is done.
#feelsgoodman #nostr #moxie #smesh