What’s the issue for issue tracking multiple-home-units for cabal? I couldn’t find any on Issues · haskell/cabal · GitHub _Is`—enable-multi-repl` equivalent to multi-home-units?_ If, then, given `—enable-multi-repl` and `—repl-no-load` (here) exist now, is it only that cabal needs to be changed to support `—enable-multi-repl` in conjunction with `—repl-no-load`, which is tracked by this issue? What is the user scenario like for mid-sized and large Haskell code bases? How is the invocation different, specifically?

On July 10 2026, a life insurance company called TruStage had a "cybersecurity incident". According to an update posted five days later, when they revealed the incident, they are "continuing to work carefully and urgently to understand the facts, and the company will communicate appropriately as its understanding of the situation evolves." This work, according to their outage page (last updated on September 11th, at the time of this writing), _is continuing_. Every major business function is listed as "partially available". They have some text explaining that they can't simply turn the system back on, because safety. They don't know what data was compromised. They don't know when they'll have everything back up. As of mid-August they had gotten so far as setting up a "clean" environment that they could start migrating services to. The only good news is that some of their services are supplied to credit unions for banking, and those were on different systems, so only their insurance packages were compromised. I also suspect the fact that they serve credit unions is the only thing keeping the business afloat, because failing to handle transactions for _months_ seems like a terminal event for most businesses. Obviously, this also means they're embroiled in an ever growing number of lawsuits from a variety of parties. It also highlights something about how insurance works: it's middlemen all the way down. TruStage will issue policies, but their connection to the actual policy holder will likely be routed through a number of different partners. Like, for example, Ethos. Ethos uses "AI" to "democratize" insurance. Feed your data into their AI, and in minutes they'll pair you up with a policy. Which, while using machine learning to do things like assess insurance risk seems like a pretty reasonable idea, in this age of AI hype, one has to wonder how this actually is implemented and how it works in practice. But Ethos isn't the end of the chain! Other companies live downstream from Ethos, for example, Family First Life. A customer might reach out to FFL to get a policy, FFL reaches out to Ethos (or one of many other partners), and Ethos reaches out to one of its partners (TruStage being one of their largest), and boom: an insurance happens. Like I said, it's middlemen all the way down. But now, here's the problem: TruStage issued a bunch of policies, and then stopped being able to do business. They stopped being able to do even vital things, like process payments. And you know what happens when payments aren't made on a life insurance policy? It lapses. It goes away. You no longer have insurance. And the agents who sell those policies are often paid a commission based on the value of the first few months of the policy's life (since life insurance is expected to be a long term investment). If the policy lapses, those commissions vanish, companies like Ethos (or downstream partners like FFL) get chargebacks on the value of those failed policies. This makes some people, like FFL's President, Shawn Meaike, very unhappy. What we have here is a pretty egregious failure of cybersecurity and disaster recovery on the part of TruStage. It's an embarrassing and potentially terminal event for them. It's awful for the customers who bought insurance policies to give themselves peace of mind, only to discover their policies lapse because TruStage _can't take their money_. It's creating mild chaos in the entire industry. That's all interesting, but not why I wanted to write an article about this. I wanted to write about _the incredible cringe_. In this clip from an insurance industry conference, Meaike brings up all of their partners for a "carrier panel". He then proceeds to line them up from stage right to stage left, ranking them as "weakest" to "strongest". Ethos, who sells TruStage policies, is labeled as the weakest. "You have the weakest leg," he says, pointing at the reps from Ethos, to laughter from the audience, and then indicates the other side of the line represents "the strongest leg." Meaike hands the microphone to an Ethos employee, Dylan Cummings, "We'll start with you." "I want to start out by thanking everyone," Cummings says. Meaike cuts him off. "Hey, hey, hey, hey. I'm gonna help you. Why don't you start by saying you're sorry." The crowd yells out, "Yes!" and applauds this idea. "Say 'We have a carrier that's shut down'," Meakie continues, "'and I'm mother-freaking sorry.'" Yes, he said "mother-freaking", on stage. So let's recap. An insurance company gets pwned so hard they can't run operations for _months_. People's policies lapse, simply because they can't _give their money_ to the insurance company. Which 100% sucks for those customers, though at least with life insurance we expect very few of them are missing their payout- hopefully! This chain cascades through the network of partners, until it culminates in the president of one company publicly humiliating the senior account manager at a middleman company, during an industry conference. Nobody comes off looking particularly good here, obviously. Meakie is a jerk. TruStage is institutionally incompetent. Ethos is in a bit of a rock-and-a-hard-place situation, and Cummings is trying to do his best to tap dance his way out of oblivion, but it seems like the AI driven insurance startup just isn't a good partner even _before_ their main issuer died. All in all, it feels like a Tim Robinson sketch, or perhaps a Nathan Fielder bit. We're one step away from Meakie calling Cummings a "Wizard of Loneliness." [Advertisement] **Plan Your .NET 9 Migration with Confidence** Your journey to .NET 9 is more than just one decision.Avoid migration migraines with the advice in this free guide. **Download Free Guide Now!**

From Zack Labe > **The average global temperature so far this year (for the January-August period)_is now up to the 2nd warmest on record since the start of this dataset..._ ** > > ** > ** > > **This data is using NOAAGlobalTempv6.1.0:www.ncei.noaa.gov/products/lan...** [Relative to 1900–2000 averages]

_tl;dr:_ "American democracy depends on the census. Trump is undermining it"_is my new op-ed at the Guardian. Check it out!_ For census geeks, this summer has been one eeeek after another. Planks of the Jenga tower keep getting pulled out. First, the White House announced

After shipping two browser extensions this year — Reverse Image Search Anywhere and Stackpeek — I still could not answer the simplest question about a listing: _is it working?_ Both stores tell you how many people installed the thing. Neither tells you the number that decides whether anyone installs it at all: where you appear when someone searches the words they would actually type. The Chrome Web Store developer dashboard has no notion of search position. Firefox's is no better. So the honest answer to "did last week's title change help?" was to open an incognito window, type the keyword, and count down the results with my finger. In three languages. So I built ExtensionDash. It scrapes both stores nightly and records installs, ratings, category rank, keyword positions, competitors and listing copy — and keeps the history. ## The decision that mattered Not the scraper. It was making the agent a first-class reader rather than an export button. `POST /mcp` speaks the Model Context Protocol over stateless HTTP, authenticated with a per-user token. Fifteen tools; eleven read, and the four that write cannot delete recorded history. Everything the dashboard renders, an agent can read. That part mostly just works. What took actual thought is that **an agent needs absence to be legible** , and a web page does not. A human seeing a blank cell reads it from context: still loading, new row, or genuinely nothing. An agent gets a JSON document with a `null` in it, and a `null` is a wonderfully confident thing to summarize as a zero. "Your extension does not rank for this keyword" and "nobody has looked yet" are opposite facts, and a tool that returns the same shape for both will get one narrated as the other to a user who believes it. So three states stay distinct: never scanned, scanned and found, scanned but absent. `add_keyword` reports whether a fetch was actually enqueued and names the tools to poll. `list_scrape_runs` surfaces a _failed_ fetch as a failure rather than as a position that silently never arrives. Same instinct behind the field I am most attached to: every position travels with the depth it was scanned to. #1 of 9 and #1 of 50 are different results. Reporting "you rank #12" while omitting that the scan stopped at 50 is how a tool lies by arithmetic rather than by mistake. ## History you did not pay for Every nightly keyword search already scans fifty results, so all fifty are recorded. `add_competitor` promotes one — which earns it a listing fetch, and therefore a description, installs and a rating — but the ranks are already there. A competitor you add today arrives with rank history going back to the day you started tracking the keyword. You get to ask "when did they pass me?" about someone you had not thought about until this morning. Stack is unremarkable on purpose: Rails 8, Postgres, Solid Queue with browser work on its own single-threaded queue, Nokogiri and Ferrum for Chrome, the public AMO API for Firefox. Kamal from a laptop. ## The beta Open, free, no card, at extensiondash.com. Limits are three extensions per account and fifteen keywords per extension, because a keyword is a nightly browser session in perpetuity — not because there is a paid tier behind them. What I would most like people to try is the part I cannot evaluate alone: **connect it to your agent and ask it something real.** claude mcp add --transport http extensiondash https://extensiondash.com/mcp \ --header "Authorization: Bearer <your token>" The token and a ready-to-paste command are on the Help page. Then ask your agent why an extension slipped last week, or what a competitor changed — and tell me where it stalls, what it guesses at, and what it reaches for that is not there. I designed those fifteen tools by reasoning about what an agent would need. Reasoning about it is not the same as watching it happen. Anything else you find, I want too: anton@kopylov.net.

It’s the crossover event you’ve all been waiting for: _Reply All_ ‘s Super Tech Support takes on an annoyingly specific technology problem involving _99% Invisible_. Ben loves podcasts, but he has a problem. When he tries to listen to 99% Invisible in particular, his car stereo completely breaks. This week, Alex, PJ, and the team at Reply All try to solve one of its strangest cases — Roman Mars versus a 2016 Mazda sedan. _Reply All _is hosted by PJ Vogt and Alex Goldman and is a part of Gimlet Media. If you’re experiencing the same in-car playback issues with _99% Invisible_ , you can find the Mazda-friendly version of our feed here!

There is a very specific, almost poetic flavor of digital closure that occurs when you go to block someone on social media, only to discover they already beat you to the punch. It’s the online equivalent of both people turning around and walking in opposite directions at the exact same moment. No hard feelings, no lingering debates—just two people silently agreeing that neither needs to perceive the other ever again. Naturally, as someone who spends entirely too much time thinking about social graph mechanics (and relational data structures), I couldn’t just let that remain an occasional serendipitous discovery. I wanted to map it. Enter bsky-mutual-blocks: a lightweight browser client designed to check your Bluesky graph, cross-reference block lists, and reveal when the antipathy across the timeline is 100% reciprocal. ### the beauty of open protocols (and why this works) On traditional siloed platforms, attempting to figure out bidirectional block states is an exercise in futility. The APIs are locked down, rate limits are punitive, and internal moderation tables are treated like state secrets. Bluesky and the AT Protocol flip the script. Because user repositories on ATProto are publicly discoverable collections of structured records (including app.bsky.graph.block records), you don’t need privileged platform access to inspect the public topology of the network. A block on ATProto isn’t a magical black hole inside a proprietary server; it’s an explicit signed record living in a user’s public data repository. If Alice creates a block record pointing at Bob’s DID, and Bob has a block record pointing at Alice’s DID, the overlap exists in plain daylight—you just need something to crawl the edges and do the set intersection. Photo by Luis Gomes on Pexels ### how it’s built I wanted the tool to be fast, client-side, zero-maintenance, and entirely transparent about authentication: #### Pure Browser OAuth (@atproto/oauth-client-browser) Nobody should have to trust third-party web apps with their main credentials or app passwords just to inspect graph data. By utilizing ATProto’s browser OAuth flow with public client metadata, the user authenticates directly against their own PDS (Personal Data Server). The access token stays in the browser session, performs the lookups, and is discarded when done. #### Fetching & Graph Traversal The client fetches your active block list via the ATProto graph lexicon, paginating through blocks to resolve subject DIDs. From there, it inspects the target profiles to identify whether a reciprocal block record exists back toward your account DID. #### Vite + Cloudflare Pages Deployment The stack is minimal: TypeScript, Vite for bundling, and deployment via Cloudflare Pages (`wrangler.jsonc`). Fast load times, zero server infrastructure to baby, and no persistent databases caching personal graph records. Photo by Kevin Ku on Pexels ### key technical takeaways **Handling PDS Federation & Resolution:** Resolving handles to DIDs and querying decentralized repositories requires graceful fallback handling for federated nodes and deleted/tombstoned accounts. **Batching & Rate Limits:** Crawling hundreds of profile records sequentially in the browser will quickly trigger API throttling. Splitting queries into controlled concurrent batches keeps response times snappy without angering the endpoints. **Client-Side Privacy:** By doing all comparison logic directly in the user’s browser, there’s no backend scraping, logging, or storing anyone’s block relationships. ### wrap-up Building on ATProto is a refreshing reminder of what building for the web used to feel like—open schemas, verifiable data, and the freedom to build small, fun tools just because you’re curious about network dynamics. If you want to poke around the source or check your own mutual block count, the project repository is open source on GitHub: schwegler/bsky-mutual-blocks.

_This preview of_**Strange Creatures** _is for Beat members at the_ prototype level_and higher. Once I've played this game more and can do a proper preview, I'll post that publicly._ ### This post is for subscribers only Become a member to get access to all content Subscribe now