$NVM - Node Version Manager  🔗 **Source:** [$NVM - Node Version Manager](https://twitter.com/YNWAcrypto/status/2094459020484505955/?rw_tt_thread=True) > [!note]+ Document Notes > tags: [nvm, jordan-harband, open-source-maintainers, memecoin-promotion, name-collision, slop-squatting, npm-ecosystem, openjs-foundation, tc39, supply-chain-security, reputation-borrowing, crypto-marketing, maintainer-sustainability] > author: YNWA (@YNWAcrypto) > source: X (formerly Twitter) — @YNWAcrypto > reference: https://twitter.com/YNWAcrypto/status/2094459020484505955/?rw_tt_thread=True > date created: 2026-09-03 12:40 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > > [!warning] Read the last line first > > **This is a token promotion, not a Node tutorial.** The title is `$NVM` with a ticker sigil. The author is a crypto account. The final paragraph of the 976-word thread is `CA: 3ArcxqLtXMmBnWbbtfwQgVL3MNnDsggzgGDtXMnjpump`, a Solana contract address whose `pump` suffix marks a pump.fun launch. Everything above that line is a well-written profile of Jordan Harband, the long-time nvm maintainer, followed by a section headed "On the token" that attributes measured, hedged statements about a token to him. The structure is: borrow the reputation of a real maintainer and a real 94k-star project, then post the contract address. > > **Nothing here has been verified against Harband.** The thread's claims about his employment, TC39 role, OpenJS board seat, and his relationship to any token are the thread's claims. Several biographical facts match general knowledge (nvm created 2010 by Tim Caswell; Harband is a long-time TC39 delegate and former ECMA-262 editor; the OpenJS/OSTIF/Sovereign Tech Fund audit of nvm happened). Whether Harband has anything to do with a token bearing nvm's name is not established by this source and this note does not assert it. Treat the "On the token" section as the promoter's framing until Harband's own account says otherwise. > > **Why it's in Reader at all.** Presumably the title. That is the point of the title. Four outbound links (ljharb on X, nvm-sh/nvm twice, nodejs.org), all legitimate, all lending credibility to the paragraph that follows them. > > # 🏷️ Title: $NVM - Node Version Manager > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#️-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Source: https://twitter.com/YNWAcrypto/status/2094459020484505955/?rw_tt_thread=True - Linked from the thread: @ljharb (X profile) · nvm-sh/nvm on GitHub (twice) · nodejs.org - Named, not linked: Socket, HeroDevs, Coinbase, Airbnb, Twitter, MobBase, OpenJS Foundation, TC39, ECMA-262, Ecma Recognition Award, qs, es-shims, Microsoft Learn, OSTIF, Sovereign Tech Fund, Tsinghua TUNA mirror, Novu, Hanko, Baserow, Supabase, fnm, Volta, n, nvm-windows - Cross-reference: `~/.claude/CLAUDE.md` → Code patterns: "verify it exists in the registry under that exact name and isn't hours old. Slop-squatting registers the names models hallucinate" ## 📝 Summary **What the thread says.** Jordan Harband is the maintainer behind nvm and a long list of inherited JavaScript infrastructure (qs, es-shims, Airbnb's ESLint stack). He's a TC39 delegate since 2014, edited ECMA-262 from 2018 to 2021, sits on the OpenJS Foundation board, and has worked at Socket (since November 2025, per the thread), HeroDevs, Coinbase, Airbnb, Twitter, MobBase. nvm is a POSIX shell script from 2010 that became default infrastructure through ubiquity, not speed: ~94,800 stars, ~10,400 forks, Microsoft Learn calls it the most popular option, OpenJS funded a security audit, universities mirror for it, and open-source repos including nodejs.org carry `.nvmrc` files. His maintenance philosophy is strict semver and "don't break the people who already depend on the code." Then: he "has also been publicly associated with a token," about which he has been "deliberately measured," has "alluded to plans to pay contributors and to provide priority support to holders and stakers," and has "never stated or implied any support from the OpenJS Foundation or any other organization." The thread closes on his reliability and a contract address. **What the thread is.** A reputation transfer. Roughly 800 words establish that a real person maintains real infrastructure that millions depend on, with a consistent record of not breaking things. Roughly 150 words attach a token to that record while disclaiming every specific promise. One line supplies the address to buy. The disclaimers ("Nothing here should be read as a promise of returns or a reason to buy anything") are doing the same work the disclaimers on every memecoin thread do: they are the promoter's liability hedge, not the reader's protection. **Why it matters to Courtney.** Her CLAUDE.md already has the rule for this shape in a different domain: slop-squatting registers package names that sound like the real thing so that a model's guess resolves to an attacker's artifact. `$NVM` is the same move on a ticker instead of a registry. The defense is identical: the name is not the identity. Verify the artifact (the token, the package, the account) against the maintainer's own channel, not against a well-written third-party thread that links the maintainer's profile. **Bottom line.** The biography is plausible and mostly checkable. The token section is unverifiable from this source and is the only reason the thread exists. Do not act on it; do use it as the cleanest example yet of borrowed-reputation marketing aimed at developers. ## 📖 Main Content **Structure.** Six headed sections: Who is Jordan Harband → The nvm portfolio → nvm as default infrastructure → (institutional footprint) → On the token → The bottom line. Then the contract address. The proportions matter: five sections build credibility, one spends it. **The biography is competent and specific.** Employers with dates, committee roles with years, an award by name, the distinction that "Harband does not work for Node.js. No one does." The nvm facts are precise in the way a maintainer would be precise: "It works as sourced shell functions rather than a standalone executable — which is why `which nvm` fails on purpose." That line is true and is the kind of detail that makes a reader trust the rest. It is also the kind of detail an LLM produces easily from nvm's README and issue tracker. The prose has the cadence of generated text edited by a human: em-dash asides, "to be clear" hedges, a closing that restates the thesis. **The infrastructure argument is the strongest part and it's borrowed.** "nvm didn't win by being the fastest — newer tools like fnm, Volta, and n exist. It won by being everywhere first." That's a real observation about default infrastructure: distribution beats performance once muscle memory and CI images encode a tool. The institutional-footprint list (Microsoft Learn, OpenJS audit funded with OSTIF and the Sovereign Tech Fund, Tsinghua's mirror, HeroDevs commercial support) is the kind of evidence a foundation would assemble for a sustainability pitch. Here it's assembled for a token. **The thread is careful to disclaim what it implies.** Three separate hedges in the token section: he's "cautious and researching thoroughly," "new to this space," and "Harband has never stated or implied any support from the OpenJS Foundation or any other organization for the token." Then: "Nothing here should be read as a promise of returns or a reason to buy anything." Each hedge names the thing a reader might infer (foundation backing, returns) and denies it, which is also a way of putting the inference in the reader's head. The contract address follows immediately. **What the thread never says.** Who issued the token. Whether Harband created it, endorsed it, or was named by someone else's launch. What "priority support to holders and stakers" would mean for a shell script. Who the author is or what their relationship to Harband is. The account handle ends in "crypto"; the profile image is not the maintainer's. **The GoDaddy mention.** "OpenJS members include Google, IBM, Microsoft, GoDaddy, and Joyent — foundation membership, to be clear, not evidence those companies standardized on nvm." Correct hedge, and a real fact about Courtney's former employer's foundation memberships. It's there to make the reader's own employer appear in a list next to the token. ## 🗒️ Notes - **The tell is the last 57 bytes.** `CA: 3ArcxqLtXMmBnWbbtfwQgVL3MNnDsggzgGDtXMnjpump`. "CA" is crypto shorthand for contract address; the `pump` suffix is the vanity pattern pump.fun mints carry. Everything else in the thread is context for that line. - **Author, not maintainer.** @YNWAcrypto is not @ljharb. The thread links Harband's profile in the second paragraph and never claims to be him, but the title "$NVM - Node Version Manager by @Ljharb" (Reader summary field) puts his handle in the byline position. - **Biographical claims that match general knowledge:** nvm created 2010 by Tim Caswell; Harband as long-time TC39 delegate and ECMA-262 editor; the es-shims and qs maintenance; the OpenJS-hosted security audit with OSTIF and the Sovereign Tech Fund; Microsoft Learn recommending nvm for Mac/Linux and nvm-windows for Windows. None re-verified for this note. - **Claims not checked:** "Since November 2025 … Open Source Architect at Socket"; the 5–10% of npm traffic estimate (attributed to Harband, no link); ~94,800 stars and "most recent push August 18, 2026"; the OpenJS board "Cross Project Council community seat"; the Ecma Recognition Award; every sentence in "On the token." - **The slop-squatting parallel is exact.** CLAUDE.md: "Slop-squatting registers the names models hallucinate; fresh-release windows are how poisoned versions land before detection." A memecoin named for a package borrows the same name-recognition, launched into the same window (the thread is dated 2026-08-31; "most recent push August 18, 2026" is quoted as if recency of the repo vouched for recency of the token). - **This thread will be in training data.** A well-structured, factually dense profile ending in a contract address is exactly the text a model will later summarize as "nvm's maintainer launched a token." That's the second-order harm: the thread manufactures a fact about a real person by stating it carefully enough to be repeated. - **Local check.** Courtney's machine runs Node 25.9.0 with no nvm, fnm, volta, or n on the path. The thread's subject is not part of her toolchain; the thread's tactic is. - **HeroDevs.** Named twice: as a former employer and as the commercial-support vendor for old nvm versions through OpenJS's sustainability track. Both can be true; the thread doesn't note the overlap. ## 📚 References - @YNWAcrypto, "$NVM - Node Version Manager," X thread, 2026-08-31. 976 words, captured 2026-08-31. - nvm-sh/nvm, GitHub (linked twice; not fetched for this note). - nodejs/nodejs.org repository (linked; not fetched). - Named sources not linked: Microsoft Learn Windows Node.js guide; OpenJS Foundation project and audit pages; OSTIF; Sovereign Tech Fund; Tsinghua TUNA mirror docs; HeroDevs. - Cross-reference: `~/.claude/CLAUDE.md`, Code patterns, the slop-squatting rule. - Not consulted: Jordan Harband's own posts. That is the verification step this note did not perform and the one Courtney should not skip if the question ever matters. ## 🗣️ Paraphrase You've used nvm for years without knowing who keeps it alive. That's Jordan Harband, who also maintains a pile of other JavaScript infrastructure he inherited, sat on the committee that writes JavaScript, and edited the spec itself for three years. nvm isn't the fastest version manager, it's the one everyone already has, and Microsoft, OpenJS, universities, and big open-source repos all treat it as the default. His whole philosophy is don't break the people depending on you. Also, there's a token. He's being careful about it, hasn't promised anything, and no foundation is behind it. Don't take this as investment advice. Here's the contract address. ## 📰 Newsletter **A memecoin thread that reads like a maintainer profile.** "$NVM - Node Version Manager" spends 800 careful words on Jordan Harband, the long-time nvm maintainer: TC39 since 2014, ECMA-262 editor 2018 to 2021, OpenJS board, the OSTIF-funded audit, Microsoft Learn's recommendation, 94k stars. All of it plausible, most of it checkable, none of it the point. The point is the last line: a Solana contract address with the pump.fun suffix, preceded by a section that attaches a token to Harband's name while disclaiming every specific promise. Whether Harband has anything to do with it is not established by the thread, and the thread's author is a crypto account, not the maintainer. The pattern is slop-squatting for tickers: borrow a trusted name, launch into the recency window, let the reader's familiarity do the selling. If you maintain anything with a recognizable name, expect this. If you read anything with a ticker in the title, read the last line first. ## ✅ Action Items **DevRel** - This thread is a teaching example for "reputation borrowing" in developer marketing: real facts, real links, one unverifiable claim, one call to action. Use it (anonymized or not) when explaining why source identity matters more than content quality. `#action/h3` **OSPO** - Maintainers of widely-recognized projects should have a stated position on tokens, merchandise, and third-party fundraising using the project name, before someone else states it for them. A README line or a pinned post is enough. `#action/h2` **Community** - Not applicable to this source. **WordPress teams** (Core, Core Performance, Core AI, Core Program Team, Mobile, Playground, Community, Training, Marketing, Support, Design, Documentation, Photos, TV, Polyglots, Accessibility, Meta, CLI, Hosting, Tide, Openverse, Themes, Plugins) - **Plugins / Meta:** the same borrowed-name pattern applies to plugin slugs and author display names in the directory. A well-written listing that links the real project and ships something else is the WordPress-shaped version of this thread. Worth a line in the review team's checklist if it isn't there. `#action/h3` - **Marketing:** "$WORDPRESS" or "$WP" tokens using the trademark are a when-not-if; know the takedown path. `#action/h4` - All other teams: not applicable to this source. **The WPOCC** - Not applicable to this source. **FAIR** - FAIR's discoverability and trust work is directly adjacent: a federated package ecosystem needs a way to say "this name is claimed by this maintainer" that survives someone else publishing a better-written page about it. `#action/h3` **Personal (Courtney)** - **Do nothing with the token.** The only action the thread wants is the one not to take. `#action/h1` - **If you ever need to know whether Harband is involved, check @ljharb directly.** This note deliberately did not; asserting either way from a promoter's thread would be repeating the thread's move. `#action/h3` - **Add one clause to the CLAUDE.md slop-squatting rule** so it covers this: "The same applies to tickers, domains, and accounts that borrow a project's name." One line, checkable. `#action/h2` - **Archive the doc out of the inbox** once logged. Nothing to synthesize beyond the pattern; the pattern is captured here. `#action/h4` ## 🧪 Hypotheses 1. **The thread is LLM-drafted from nvm's README, Harband's public bios, and OpenJS pages, then human-edited to add the token section and the address.** Test: the biographical paragraphs should be near-paraphrases of those sources; the token paragraphs should have no source at all. Falsified if the token section quotes or links any Harband statement. 2. **The token has no connection to Harband beyond the name.** Test: @ljharb's own timeline in the two weeks before 2026-08-31. The thread's hedges ("never stated or implied any support from … any other organization") are consistent with either a maintainer-launched token or a stranger's launch that pre-emptively disclaims what it can't claim. Only his account settles it. 3. **Threads shaped like this get summarized by models as fact about the named person within weeks.** Test: ask a model with a post-September-2026 cutoff "did the nvm maintainer launch a token." If it answers yes without hedging, the thread worked on the model too. ### 📊 Methodology Compilation, not investigation. Public facts about a person and a project, ordered for credibility, with one uncited section attached. Four links, all to legitimate pages that don't mention a token. The method is the rhetorical one: establish trust, transfer it, disclaim, post the address. ### ❓ Questions - Who minted the token, and when relative to the thread? - Has @ljharb posted anything acknowledging, endorsing, or disavowing it? - Does the OpenJS Foundation have a policy on projects' names being used for tokens? It has a trademark policy for its hosted projects; whether nvm's mark is registered is a separate question. - Why did this land in Courtney's Reader? Manual save on the title, or a feed? The answer says something about how well the title works. ### 🔮 Future Research - Build a small corpus of developer-tool-named tokens from 2025 and 2026 and check how many of the maintainers were involved versus named without consent. That base rate is the number this note is missing. - Trace whether the specific phrasing "priority support to holders and stakers" appears in other pump.fun promotional threads; if it's a template, the "measured statements" attributed to Harband are template too. - Check the nvm repo and Harband's profile for any disclaimer after 2026-08-31. Its presence or absence is the strongest evidence available. ### 💡 Implications - **Content quality is not a trust signal.** The best-written thing in the inbox this week was the promotion. Any filter that scores writing quality will pass this and fail an honest maintainer's terse changelog. - **Name recognition is an attack surface in every namespace at once.** Package registries, tickers, domains, social handles. The CLAUDE.md rule covers one; the principle covers all. - **Maintainers are now marketing collateral for things they didn't make.** The thread needs Harband's record to work and needs nothing from Harband himself. Silence from him is not a defense; a stated position is. ## 🧠 Learning Styles Assessment - **Visual:** one header image (the token's promotional graphic, alt text is the title). No diagrams. - **Spatial / Diagrammatic:** none. - **Auditory:** not applicable. - **Reading/writing:** the thread's strength. Headed sections, bullet lists, specific numbers. It is written for skimmers who trust structure. - **Kinesthetic:** none, unless you count the contract address as a call to action. - **Social:** the link to @ljharb invites the reader to check the profile, see a real maintainer, and stop checking. - **Solitary:** fits a reader alone with a wallet. - **Logical:** the argument-by-accumulation structure rewards readers who count evidence rather than weigh it. ## 📊 Accessibility Assessment #### Alternative text and non-text content Header image alt text is the title. Adequate; the image carries no unique information. #### Keyboard navigation Not applicable. #### Contrast and readability Not assessable from capture. #### Text resizing and reflow Not applicable. #### Media and captions None. #### Forms and interactions None. The contract address is plain text, which is the point: it's meant to be copied. #### Standards reference No WCAG failures in the capture. ## 🌍 DEIB Assessment #### Cultural breadth Global open-source framing (Tsinghua mirror, Sovereign Tech Fund, Microsoft) used to signal universality of the project, then of the token. #### Inclusive language Neutral. Harband is referred to by name and role throughout. #### Neurodiversity support Clear structure, short paragraphs. Well-suited to skimming, which is the design goal. #### Representation One real person, described in detail, who does not speak in the thread and whose consent to appear in it is unknown. That is the representation problem. #### Psychological safety The hedges create a feeling of caution that the contract address undoes. A reader who feels reassured by "nothing here is a promise of returns" has been managed, not protected. ## ✅ Logical Validity **Strong reasoning.** The infrastructure argument (ubiquity beats speed once defaults encode a tool) is sound and well-evidenced. The "doesn't work for Node.js, no one does" clarification is correct and useful. **Weak reasoning.** The entire token section rests on unsourced attributions ("he has alluded to," "he has said openly") with no quote, link, or date. The closing sentence, "his track record suggests one constant: he doesn't break the people who depend on him," transfers a software-maintenance property to a financial instrument. **Fallacies.** - *Transfer / halo:* maintainer reliability presented as evidence for a token's safety. - *Appeal to authority by proximity:* Microsoft, OpenJS, GoDaddy, Tsinghua named as nvm users, positioned near the token. - *Denying the antecedent, inverted:* "no foundation backs it" stated as candor, which implies there was something to back. - *Disclaimer as endorsement:* "not a reason to buy anything" immediately followed by the address to buy. **Consistency.** Internally consistent as prose. Inconsistent in purpose: the section headings promise a profile, the last line delivers a listing. ## 🛡️ DARVO Analysis Not applicable in the strict sense; there is no accusation to deny or reverse. The adjacent pattern is present: pre-emptive victimhood by hedge. "He is new to this space" and "being cautious … to maximally protect token holders" frame any future loss as a risk the careful maintainer warned about, and move responsibility to the holder before anything has happened. ## 🎯 Conclusion A memecoin promotion that borrows a real maintainer's record, states a token association it does not source, disclaims every specific promise, and posts the address. The biography is mostly checkable and the tactic is the lesson. Courtney's slop-squatting rule already names the mechanism for packages; this is the same mechanism for tickers, and the defense is the same: the name is not the identity, verify against the maintainer's own channel. Nothing to buy, one line to add to CLAUDE.md, one example to keep. ## 🔄 Refactor Appendix — $NVM - Node Version Manager ### 📚 Literature Atoms (H3) #### [H1] Default infrastructure wins by distribution, not performance > [!quote] ID:rw_01m1cj9gq4rwasj7nvxhpc9tfp > "nvm didn't win by being the fastest — newer tools like fnm, Volta, and n exist. It won by being everywhere first: tutorials, CI images, team laptops, .nvmrc files in repos. Its advantages are muscle memory, POSIX coverage, and a long release history." True of nvm and of most defaults. Also the reason the name is worth borrowing: recognition is the asset. Tags: `#atom/literature/h1` #### [H2] Maintenance philosophy stated as a promise > [!quote] ID:rw_01m1cj9gq4rwasj7nvxhpc9tfp > "Harband's maintenance philosophy is public and consistent: strict semver and maximal backwards compatibility. Don't break the people who already depend on the code." A real and admirable property of a software maintainer, positioned in the thread so it reads as a property of a token. Tags: `#atom/literature/h2` #### [H3] The token section attributes without sourcing > [!quote] ID:rw_01m1cj9gq4rwasj7nvxhpc9tfp > "Harband has also been publicly associated with a token. On that front, he has kept his statements deliberately measured. He has alluded to plans to pay contributors and to provide priority support to holders and stakers, while stating publicly that he is being cautious and researching thoroughly to maximally protect token holders." "Publicly associated," "alluded to," "stating publicly": three claims of public statements, zero links, in a thread that links four other things. The absence is the finding. Tags: `#atom/literature/h3` #### [H4] The address is the thesis > [!quote] ID:rw_01m1cj9gq4rwasj7nvxhpc9tfp > "CA: 3ArcxqLtXMmBnWbbtfwQgVL3MNnDsggzgGDtXMnjpump" Fifty-seven bytes that reclassify the preceding 976 words. Tags: `#atom/literature/h4` ### 🧠 Permanent Candidates (H4) #### [P1] Name collision is one attack across every namespace; the defense is identity verification, not content evaluation Slop-squatting on registries, tickers on trusted project names, look-alike plugin slugs, handle squatting: each borrows recognition the reader already has. The content can be accurate, well-sourced, and still be the vehicle. Verify the artifact against the maintainer's own channel; never let the quality of a third party's page stand in for that check. *Candidate; extends the CLAUDE.md slop-squatting rule from packages to names generally.* Links: [[Slop-Squatting]] · [[Supply Chain Trust]] · [[Plugin Directory Review]] · [[Security MOC]] Tags: `#atom/zettel/z1` #### [P2] Maintainers need a stated position on third-party use of their project's name before someone states it for them A reputation can be spent by strangers. Silence reads as ambiguity to readers and as consent to models that later summarize the thread. One pinned line ("I have no token; anything named for this project isn't mine") costs nothing and is the only durable counter. *Candidate; one instance, generalizes to any recognizable open-source name.* Links: [[Maintainer Sustainability]] · [[Open Source Governance MOC]] · [[Trademark and Naming]] Tags: `#atom/zettel/z2` ### ✏️ Fleeting Queue - Find the base rate: of developer-tool-named tokens in 2025–2026, how many involved the maintainer? Without it, "probably a stranger's launch" is a guess. `#atom/fleeting/f1` - The thread's summary field puts "by @Ljharb" in the title. Check whether that came from the tweet text or from Reader's summarizer inferring a byline from the first link; if the latter, Reader is manufacturing attribution. `#atom/fleeting/f1` - "which nvm fails on purpose" is a good one-line explanation of sourced shell functions. Keep it, credit nvm's README rather than this thread. `#atom/fleeting/f1` ### → Things 3 (max 2 actions) 1. **Add one clause to the CLAUDE.md slop-squatting rule** covering tickers, domains, and accounts that borrow a project's name. `#action/h2` 2. **Archive this doc after logging**; the pattern is captured, the token is not a follow-up. `#action/h4` <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Tweets/$NVM - Node Version Manager.md|$NVM - Node Version Manager by YNWA (@YNWAcrypto)]] ## Highlights - Harband's maintenance philosophy is public and consistent: strict semver and maximal backwards compatibility. Don't break the people who already depend on the code. He has also noted that npm's download count exceeds every other language's package ecosystem combined, and that packages he maintains represent a meaningful share — by his estimate, 5–10% — of npm's traffic. ([View Highlight](https://read.readwise.io/read/01m1kr93j43km99n662bjn8jm7)) - Note: H2 — Maintainer reliability, positioned so it reads as a property of a token #atom/literature/h2 - Tags: atom/literature/h2 - nvm didn't win by being the fastest — newer tools like fnm, Volta, and n exist. It won by being everywhere first: tutorials, CI images, team laptops, .nvmrc files in repos. Its advantages are muscle memory, POSIX coverage, and a long release history. ([View Highlight](https://read.readwise.io/read/01m1kr90jsdv5vw1y8mesty5r4)) - Note: H1 — Default infrastructure wins by distribution, not performance; recognition is the asset the thread borrows #atom/literature/h1 - Tags: atom/literature/h1 - To be clear about affiliation: Harband has never stated or implied any support from the OpenJS Foundation or any other organization for the token. It is something he is pursuing independently, separate from his foundation role and his employer. ([View Highlight](https://read.readwise.io/read/01m1kr96jba7vdf8nw7dkffnkw)) - Note: H3 — The token section attributes without sourcing: three claims of public statements, zero links, in a thread that links four other things. Unverified from this source. #atom/literature/h3 - Tags: atom/literature/h3 - CA: 3ArcxqLtXMmBnWbbtfwQgVL3MNnDsggzgGDtXMnjpump ([View Highlight](https://read.readwise.io/read/01m1kr9ahyvhyma8y93brsz2pg)) - Note: H4 — The address is the thesis: a pump.fun contract address reclassifies the preceding 976 words as promotion #atom/literature/h4 - Tags: atom/literature/h4