Note on evidence: the Reddit slot in this run is mostly not about Meshtastic. Reddit's public search 403'd on every attempt, so the engine fell back to subreddit listing discovery, and r/preppers — a resolved subreddit for the topic — supplied its own front page instead: a Costco trip at 231 points, "Don't forget to live your life" at 620, flashlight recommendations at 80, water storage, mylar buckets, basement vs. bunker. Nine of fifteen Reddit items are prepper staples with no mesh content, which means the 1,977 upvotes in the footer below are very largely somebody else's conversation. Four items are genuinely on topic. Every cluster in the run also carries the engine's entity-miss demotion tag, and YouTube contributed zero items to the final corpus despite six transcripts being fetched mid-run. What actually carried this reading: sixteen web supplements, two GitHub repos with live counts, and the on-topic X posts.

What I learned:

The live argument in this window is not about range at all — it is about routing, and it has produced a second firmware people are actually flashing. Meshtastic floods: every node that receives a packet rebroadcasts it to every node within earshot, up to a hop limit, which is why there is "no routing table to build and no topology to plan ahead of time." That property is the whole product — Little Bird Electronics puts it as "the appeal is that there's nothing to configure. Turn a node on, and it's part of the mesh and helping carry other people's traffic," with the cap at 7 hops. It is also the failure mode, and the clearest statement of it in the window comes from a search-and-rescue operations write-up rather than from the hobby forums: as a flood network grows, "channel utilization climbs, latency increases, and eventually the mesh becomes a source of interference with itself." MeshCore's pitch is the opposite trade — it "routes traffic deliberately, which lets it scale across a larger geographic footprint without the self-congestion problem." A mesh that scales by being told where to send things is not the same product as a mesh that scales by everyone shouting.

The sharpest sentence of the month is a scope verdict, and it explicitly forecloses the usual consolation that a firmware update will fix it. The same SAR piece, dated 23 August, lands on: "Meshtastic is the right platform for a single incident with a defined team. It's the wrong platform for a statewide network, and no firmware update changes that math." Its allocation is by operational footprint, not preference — Meshtastic for one incident with a defined team, MeshCore for "county-to-county coordination, EOC-to-EOC links, and statewide awareness," Reticulum for a multi-transport backbone where you have the expertise to run one. The instruction attached is worth more than the ranking: "Pick based on what the operation actually requires" rather than forum consensus. That is someone with a radio budget telling you the internet argument is the wrong input.

A city-scale mesh spent the summer asking its users to make their nodes quieter, and has now given up on asking. Philly Mesh wrote on 2 September that the settings they had been requesting all summer — reduce position reporting, telemetry, NodeInfo — are now "baked into the firmware," with the stated result that "without these packets clogging the mesh, there is more room for messages to reliably flow. Higher Hop Limit." Read that in order: the way you buy more hops on a flood network is to delete the traffic the network generates about itself. Almost none of a struggling mesh's air time is people talking. It is nodes announcing that they exist, where they are, and how warm they are — and the fix shipped as a default because a fix that depends on every operator changing a setting is not a fix.

Range is an antenna decision, and the honest numbers only appear once someone names the antenna. The one measured pair in the corpus comes from an Atlavox Beacon owner review: 702 feet on the 7-inch BLE antenna talking to an iPhone, against 11.5 miles on LoRa once they fitted "a Wio Tracker L1 with an upgraded whip antenna and the 7" Alpha antenna on the Beacon" — and the reviewer volunteers that terrain limited the testing. A Heltec customer reports the same lever more bluntly: "I bought the 'SMA whip 868/915 antenna' and it has extended the range signifi[cantly]." The one video the web sweep surfaced on the question is titled Is Your Meshcore / Meshtastic Setup Wrong? | Range & Propagation and opens on "why the st[ock antenna]" — so the field's own framing is that the default configuration is the problem, not the protocol. Note the asymmetry that makes range threads useless: 702 feet and 11.5 miles are both true, from the same device, on the same day.

The vendors have stopped picking a side, which is the strongest evidence the split is real. Heltec now markets the WiFi LoRa 32 V4.3 as "Meshtastic, MeshCore and LoRaWAN Compatible" in the product title itself. LoraMeshDevices Hub runs live node maps across "MeshMap, MeshCore and LetsMesh" as one view, and serves browser clients for both firmwares over USB and Bluetooth with no app install. Supply Drop BBS hit v1.0.0 on 5 September as a bulletin board that "runs on MeshCore or Meshtastic (or any protocol YOU write a plugin for!)". When the maps, the web clients and the application layer all go protocol-agnostic inside one month, the ecosystem has priced in a two-firmware world. Meanwhile the entry point stays cheap: OERadio puts working hardware at "around 35 euros," and RAK is selling a 1W booster kit explicitly for people "who understand antenna placement, power planning, and local transmit power rules" — the upsell is knowledge, not silicon.

The highest-engagement on-topic post of the month is an attack tool, and the properties it exploits are exactly the ones the emergency-comms people are buying. LoKi, presented at DEF CON 34 and posted on 6 September at 86 likes, is "a BadUSB HID device that looks like a computer mouse," commanded over LoRa: "Hackers send commands to a LoKi device using long range (LoRa) radio signals and it runs whatever it was asked to. Works from miles away." A second account circulates DEF CON 33's RF Village talk "Meshtastic Command & Control" alongside grid-down comms material, in the same post, without apparently noticing the tension. Unlicensed, long-range, infrastructure-independent, no fee — that list reads as resilience in one room and as exfiltration in the other. Worth holding next to the civic framing that showed up the same week, with community members in Floyd, Virginia gathering on 3 September to stand up a secondary communication network.

What the window does not contain is a long-run delivery-rate receipt, and the one two-year retrospective is a correction rather than a testimonial. The project is large and busy — meshtastic/firmware sits at 8.3K stars with 455 open issues, the Android client at 1.8K stars with 37 — and yet across 30 days there is exactly one first-person account of living with a deployment: "Two years of solar-powered Meshtastic deployments, here's what I'd do differently", 206 points and 41 comments on 11 August. The title is the finding. Nobody in this corpus publishes what fraction of messages actually arrive across a city mesh over a month, which is the number that would settle the flood-versus-structured argument outright — and its absence is why that argument is still being had in blog posts.

KEY PATTERNS from the research:

1. The bottleneck is self-congestion, not distance — a flood mesh eventually becomes "a source of interference with itself", so past a certain size the question stops being how far a node reaches and becomes how much air time the network wastes describing itself.
2. Match the firmware to the operational footprint: one incident with a defined team is Meshtastic's case, county-to-county and statewide is MeshCore's, and "no firmware update changes that math."
3. Zero-configuration is the feature and the bill — nothing to configure, 7 hops, every node carries everyone's traffic is one property described twice, once as the pitch and once as the limit.
4. Turn down telemetry before you buy hops: Philly Mesh baked position, telemetry and NodeInfo reduction into the firmware precisely because asking operators to change settings did not work.
5. Ignore any range figure that does not name an antenna — 702 feet and 11.5 miles came from the same node on the same day, and the stock antenna is the default failure.
6. The ecosystem has already hedged: dual-firmware hardware, joint node maps and web clients, and protocol-agnostic applications all shipped inside 30 days, so plan for two firmwares rather than a winner.
7. The same properties are dual-use and the security side is louder — a LoRa-commanded BadUSB implant that "works from miles away" drew more engagement than any resilience post in the window.
8. Read the fuel gauge, not the star count — 8.3K stars sits on top of 455 open firmware issues, and the community's only two-year retrospective is titled "what I'd do differently".
9. Nobody publishes month-long message delivery rates for a city mesh, which is the single measurement that would end the routing argument — until someone does, both sides are arguing from architecture rather than from data.

Note on evidence: this run's footer is close to meaningless and the numbers below should be read with that in mind. Reddit's public search 403'd, and of the three items that survived, one is an r/BestofRedditorUpdates thread about a doctor's appointment carrying 7,022 of the 7,162 upvotes in the footer — nothing to do with genealogy. The Hacker News slot is two keyword traps stacked: an AI-text-watermarking cluster (five stories) pulled by "text," and an archives cluster (Anna's Archive, Amazon destroying rare books to train models, Archive.org asking for hard drives) pulled by "archive." X returned Seedance video prompts and an MIT curriculum report. The engine flagged its own thinness up front — only 23 of 61 dated items fell in the last seven days — and demoted every cluster with entity-miss. What actually carried this reading: the web supplements, one GitHub pull request, three on-topic social items, and four sources I fetched directly to fill the gap the corpus left.

What I learned:

The capability is real, and the sharpest receipt in the window is a fifteen-year gap closing in one query. From an r/Genealogy thread titled "Anyone using FamilySearch AI feature? It is kinda stellar": "I found a marriage record using the full text that I couldn't find for 15 years. It is a perfectly fine record too, from 1849. The handwriting is a little messy, but very legible. This thing wouldn't pull up in indexed records for all this time and the full text search it just pops right up." Sit with what that describes. The document was scanned. It was legible. It was on the site. For fifteen years it was unfindable because no human had typed its contents into an index, and a name search returns nothing whether a record is absent or merely unindexed. The AI did not read anything a person couldn't. It read things no person had gotten around to.

What changed is which pile got opened, and the pile was always the interesting one. Full-Text Search applies handwriting recognition "to the vast archive of microfilmed records that were scanned but never indexed — deeds, probate files, land grants — making them keyword-searchable for the first time," which made "billions of previously unindexed wills and deeds searchable for free". Note the record types. Indexed genealogy has always been births, marriages, deaths — the vital events, because those are the ones with a name in a predictable field, which is what makes them cheap to index by hand. Deeds, probate files and land grants are where a person's life actually leaves a paper trail, and they were skipped for exactly the reason they are valuable: the names are buried in prose. Handwritten text recognition did not extend the frontier so much as invert which records are expensive.

The failure mode people brace for is misread handwriting. The one that will actually cost them is not knowing what they searched. The Family History Guide's walk-through counts six different document collections or ways to search — catalog, historical records, images, full-text, simple search, books — and states plainly that "there is no real way to determine the degree of redundancy between these separate collections," so "any search we make only reaches an unknown number of documents that have been processed and made available to the search." The consequence is the sentence to remember: "most users of the website do an unsuccessful name search and conclude that FamilySearch does not have the documents they are looking for." A negative result carries no information. The same author reports that Boolean operators do not reliably help — "I am not sure that FamilySearch's full-text search understands them because the results are inconsistent" — and lands on a verdict worth quoting whole: "relying on Full-text Search for all of your research is lamentably impossible." Comprehensive means searching six ways, every time.

You cannot correct a bad transcript, and the reason is legal rather than technical — which is the most interesting trade in the whole story. FamilySearch's own help centre says editing is switched off to prevent "problems in which edits impede our ability to follow privacy laws and respond to requests from the organizations that own the records", that they are "carefully reviewing the editing tool," and — the part people skim past — that it may stay unavailable after the current review concludes. Consider what that reverses. FamilySearch's indexed corpus was built by volunteers typing records, and community correction was the whole quality model. An AI transcript is a derived artifact the platform must be able to alter or withdraw on a rights-holder's or regulator's request, and a crowd-edited transcript is one it no longer fully controls. So correctability was traded away for retractability. The billions of newly searchable records are searchable on terms that make them permanently read-only, and it is still formally a FamilySearch Labs experiment.

The search grammar is undocumented enough that people are writing test suites against it. The one substantive engineering artifact in the window is a pull request on a genealogy agent-skill repo doing a deep dive on full-text query mechanics, and its finding is a spec drift: the documentation claimed a minimum of three literal characters before the *, while the tool code — unchanged since 2026-05-20 — only requires three literal characters per term overall. The author verified it live rather than arguing it: +Mo*ntain returns 6.29 million results with genuine "Mountain" hits, valid because the term carries seven literal characters even though only two precede the wildcard. Alongside: ? matches exactly one character, * matches zero or more, and a wildcard cannot open a term. Their eval suite runs 12–13 of 13 passing, with two negative tests failing intermittently from model-sampling variance rather than regression. When third parties maintain evals against a search box, the search box is an API nobody documented.

Attention in this window is on the institution rather than the tool, and the loudest genealogy thread is about death rather than discovery. FamilySearch's own account posted twice — a wartime family story at 27 likes, a records promo at 16 — while the highest-engagement FamilySearch-adjacent post is Church News at 150 likes, an executive director talking about "the joy that comes from it." Nothing in the window from the organisation frames the AI as the story. Meanwhile the biggest genuinely on-topic Reddit thread is "What to do with all my research?" — 140 points, 98 comments — which is a succession question, not a search question. Billions of records just became findable and the community's live anxiety is who inherits the binder.

The labour that just evaporated had a public price, and one person posted it. "I once hired on fiverr to get handwritten notes converted to digital - some 100 pages, done in about $150 or so. That's gone as well to AI" — roughly a dollar fifty a page. That was personal notes rather than archival records, so it is not FamilySearch's own cost curve, but it prices the manual baseline that a volunteer indexing corps had been supplying free for decades. For context on where the rest of the field sits, Cornell's archival research guide still points researchers at Transkribus — "an AI-powered platform for text recognition, transcription and searching of historical documents" — as the general-purpose tool, which is the one you reach for when the records are not in FamilySearch's six collections at all.

KEY PATTERNS from the research:

1. The unlock was indexing, not reading — a legible 1849 record sat unfindable for fifteen years because nobody had typed it, so the win is against a labour backlog rather than against difficult handwriting.
2. The newly-open records are the ones humans skipped for being expensive — deeds, probate files and land grants, where names sit in prose rather than in fields, which is also why they carry more life than vital records do.
3. Treat every empty result as unknown rather than absent: six collections with undeterminable overlap means a failed search proves nothing, and "most users… conclude that FamilySearch does not have the documents" when it does.
4. Search six ways or accept partial coverage — the same author's verdict is that "relying on Full-text Search for all of your research is lamentably impossible," and Boolean operators return inconsistent results.
5. Correctability was traded for retractability — editing is disabled so edits cannot "impede our ability to follow privacy laws and respond to requests from the organizations that own the records", reversing the volunteer-correction model the indexed corpus was built on, possibly permanently.
6. Learn the actual query rules, not the published ones — three literal characters per term overall, not before the wildcard; ? is one character, * is zero or more, and no wildcard may open a term.
7. Third parties maintaining eval suites against a consumer search box is the signal that its grammar is load-bearing and undocumented.
8. The org is selling the feeling and the community is discussing inheritance — official posts at 16–27 likes against 150 for a devotional interview, while the top genealogy thread asks "what to do with all my research".
9. It is still a Labs experiment, so the accuracy, the coverage and the read-only transcript are all provisional in the direction of the platform's convenience rather than yours.

Note on evidence: this is the thinnest of the day's three corpora and the shape of the thinness is itself informative. The web slot is almost entirely vendor-authored listicles — one of them, Sensefold's, ranks read-it-later apps and concludes that "Sensefold is one of the most compelling places to start in 2026" — alongside Flozic, Readless, Swifty Studio, Pickuma and a Softonic download page. The community layer barely exists: r/readwise's only two threads in the window are titled "Read" (0 points) and "Read on Kindle" (1 point), r/rss's live thread is an outage report, and the 1,074 upvotes in the footer come from an r/selfhosted homepage screenshot with no read-later content in it. Hacker News contributed RSS plumbing. The engine flagged the freshness itself — 6 of 29 dated items inside the last seven days — and demoted every cluster with entity-miss. What carried this reading: one GitHub repo with live counts, one founder losing his temper in public, one Reddit quote the web sweep surfaced, and two posts I fetched in full.

What I learned:

The sharpest thing anyone said in this window is an argument against the entire category, and it comes from the note-taking crowd rather than the reading crowd. From r/ObsidianMD, 1 September: "The archive keeps growing, and at some point you can't tell which saves were things you genuinely meant to read and which were just there to round out the collection. A vault full of unread material isn't a second brain. It's a storage unit." What makes it more than a good line is the mechanism offered next to it: "Reference material mostly gets processed on the spot. Found a good restaurant? You pin it on Google Maps immediately. A timely news article or viral post? It goes straight into a group chat or gets posted somewhere." Read that as a filter and it is unkind in a useful way — the things you actually intend to use get routed somewhere specific within seconds, so the read-later queue is defined by exclusion. It is where things go when you have decided not to decide. Which means backlog size is not a capacity problem to be solved with better tooling; it is the honest output of the sorting you already did.

The vendor concedes in its own onboarding documentation that the capture layer is lossy. Readwise's Getting Started with Reader tells new users why they might prefer the web highlighter over the app, and the second reason is the admission: "although our parsing is at the frontier of the read-it-later category, we'll never be able to parse 100% of the internet, 100% perfectly." The first reason is more interesting for being non-technical — sometimes "the original site is more pleasing," so "you can honor the OP and read as they intended." The clean distraction-free reader is the product's whole pitch, and the product's own docs tell you to bypass it on the good-looking pages and on the ones it mangles. Anything with a paywall, a heavy layout or an unusual template is a coin flip, and you find out after you have saved it, which is the worst possible time.

Pricing is muddled enough that a founder is arguing about it on X, and the correction is invisible next to the complaint. On 3 September, @homsiT: "We did not double the price, wtf are you talking about? that is straight false. there was a modest price raise in 2023 from $96/year to $120/year as both products evolved and improved. but even when we did that, we never raised the prices on existing customers, they got Reader for free and they still pay that old price. also if you don't want the read later app you can simply subscribe to Readwise Lite, which is $6.99/month now. yes, merging the apps is incredibly hard and would break workflows." Meanwhile TechCrunch's alternatives round-up prices the same thing as free for 30 days and then "a $9.99 per month Readwise subscription." So a prospective buyer meets $96/year, $120/year, $6.99/month and $9.99/month for one product family, split across a grandfathered tier, a Lite tier and a bundle the company says is "incredibly hard" to merge. That is the actual explanation for the doubling rumour: nobody is lying, the surface is just genuinely unreadable. The rebuttal drew one like.

The self-hosted answer consolidated on one project, and its appeal is explicitly that it does less. Karakeep sits at 29K stars with 707 open issues, described as "a self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text search." The write-up that circulated is XDA's, titled "It took me a year to find a real Pocket replacement, and it was self-hosted the whole time," and its verdict is a compliment shaped like a criticism: "The best read-later app I found doesn't do much, and that's exactly why it works," plus the real bar for self-hosted software — "it feels polished enough that I don't constantly think about the fact that I'm self-hosting it." Setup is Docker Compose, environment variables, start the container. Note the author's own account of why the search took a year: they dismissed self-hosting up front and kept cycling through cloud apps. And hold the 707 open issues against the 29K stars before treating this as settled.

The portability everyone points to as reassurance had an expiry date, and that is the lesson from Pocket rather than "pick a better app." Flozic's round-up notes that "Instapaper, Raindrop.io, Readwise Reader and Wallabag all accept Pocket's export format" — a genuine de facto interchange standard, which sounds like the happy ending. The qualifier is the whole thing: can you still bring your library across? "Yes, if you exported it before access ended." The format was open, the importers were built, the ecosystem cooperated, and none of that helped anyone who found out late. Export compatibility is a property of a moment, not of a file format, and the only version of it that protects you is the copy already on your disk.

Structurally, the read-later app is being demoted from destination to sink. Miniflux integrates with more than 25 third-party services including Wallabag, Pinboard, Instapaper and Linkding, speaks both the Fever and Google Reader APIs so it works with existing mobile clients, does OPML import and export including by URL, and ships to Docker Hub, GHCR and Quay with ARM and RISC-V builds; FreshRSS cuts releases every two to three months. The arrangement people are landing on puts feeds at the front door and saving behind it as an integration, which quietly solves the discovery problem the read-later app never addressed: a queue you fill by hand contains only things you already found.

The highest-engagement artifact of the month is about changing the reading surface rather than the app — and its own author never claims it worked. "I turned my RSS feeds into an e-ink newspaper to stop reading on my phone" took 228 points and 103 comments on Hacker News, the biggest number in this corpus by an order of magnitude. The build is feedpaper: pull unread posts from Feedbin's API, mark them read, generate an e-pub, and filter out what does not survive the trip — YouTube channels, JavaScript-heavy blogs, link-only newsletters. It reads on an Xteink X4, 4.3 inches, no touchscreen, no backlight. The motivation is specific and physical: he prefers reading horizontally on a couch, the phone caused eye strain, and the annoyance never produced action until a device did. What the post does not contain, anywhere, is a claim that he now reads more. A hundred people discussed a solution whose author declined to say it solved anything — which, next to the storage-unit line, is the category's whole condition in one artifact.

KEY PATTERNS from the research:

1. The backlog is a sorting output, not a capacity failure — things you intend to use get routed within seconds, so the queue collects what you decided not to decide about, and "a vault full of unread material isn't a second brain. It's a storage unit."
2. Assume the capture is lossy — Readwise's own docs say they "will never be able to parse 100% of the internet, 100% perfectly", and you discover which pages broke only after saving them.
3. Confusing pricing manufactures its own rumours: $96/yr grandfathered, $120/yr, $6.99/mo Lite and $9.99/mo per TechCrunch describe one product family, and the founder's correction drew a single like.
4. The self-hosted winner wins on restraint — Karakeep at 29K stars is recommended because "it doesn't do much, and that's exactly why it works" — but 707 open issues is the number to weigh against the star count.
5. Export compatibility is a moment, not a guarantee — four apps accept Pocket's format, "if you exported it before access ended", so the only durable portability is the archive already sitting on your disk.
6. Put the feed reader in front and the save behind it — Miniflux's 25+ integrations and Fever/Google Reader API support make the read-later app a sink, which is also the only part of the stack that brings you things you had not already found.
7. Changing the device beats changing the app, at least in what people upvote — an e-ink newspaper built on Feedbin and a 4.3-inch backlight-free reader outdrew every app discussion in the window combined.
8. Nobody publishes their read-through rate. The month's most-discussed fix carries no claim that its author read more, and no thread in this corpus reports what fraction of a queue ever gets opened — which is the one number that would tell you whether any of these tools work.
9. Discount the listicles: the web layer for this topic is written by the vendors being ranked, including one that ranks itself as the most compelling place to start.