I've never used Resolve primarily so I don't have a good feeling of how they compare, but I have experienced a couple of unexpected, mid-work crashes in Resolve as well. I believe these were tied to my working on a machine with an Intel iGPU, which at least at the time seemed to be... discouraged, I'll say, by the Resolve community due to known stability issues. Possibly the root of evil with Premiere as well, but again, doesn't seem to be a major problem for kdenlive.

What I will say is that I personally prefer Shotcut to kdenlive. Both are basically graphical frontends to MLT, the actual media toolkit/editor (driven by XML files). Shotcut has a simpler, more user-friendly UI than kdenlive and also seems to be a bit more stable/performant. kdenlive is more featureful. I think most people should try both because it probably depends on your workflow which is more convenient.

What might confuse things a bit is that this incident happened hours before ICE agents started reinforcing TSA at checkpoints and seems mostly unrelated, other than establishing the general principle that ICE will arrest people at airports based on tips from TSA's flight booking records.

Still, it is rarely a problem in practice, because anyone relying on addresses to establish these legal details will have to look at where the address is actually located---not just the city written in it. Keep in mind that quite a few people live in ZIPs where they could write multiple city names in their address.

When it comes to the unusual case of spanning states, it might help to note that the City State Database the postal service uses to validate addresses does not actually differentiate between city and state. "NEW YORK NY" is a single string. The state is really just part of the city name. The fact that USPS implemented it this way indicates the extent to which it does not matter in operational reality.

A sibling comment points this out, but it might also help to explain that in the US, it is very common for people to have mailing addresses in cities they do not actually live in. That's because of suburbs. City lines are often surprisingly arbitrary and reflect complex political histories. Many people consider themselves to live in [major city] but, in legal actuality, live in [unincorporated county that contains major city]. Many of the upsides of living in the city, sans some of the property taxes and voting in city elections! Yet another reason that people understand that mailing addresses are not definitive reflections of political boundaries.

If you ever work as an election clerk you will find this a LOT---people indignant that they cannot vote for the mayor, to whom you will have to explain, somehow for the first time, that they do not actually live in city limits. This tends to be more obvious if you get a property tax bill but a lot of people are renters and never really think about that aspect.

That said, the ZIP DB is indeed not very large, so you can find copies of it. You won't generally find complete copies of the City State file but I wouldn't be surprised if there is one out there.

This does mean that you might autofill a city name that is "wrong" in the view of the person completing the address form, but much of the bulk mail they receive probably uses that city name anyway.

Technically speaking ZIP codes are not "supposed" to span states but, in exceptional cases, some do. In this case USPS handles it the same way: the state of the preferred city is the preferred state for the ZIP code.

The preferred city is almost always the location of the post office serving the ZIP, which makes this situation fairly intuitive. You can find some interesting edge cases where a post office in located in a suburb city, resulting in a ZIP that includes part of a major city having the suburb as its preferred city name.

You can look up the city name and alternates for a ZIP here: https://tools.usps.com/zip-code-lookup.htm?citybyzipcode and the Domestic Mailing Manual covers this, although it's scattered across several sections and mostly part of how the City State database (the database used for validating city and state names in addresses) works.

Unfortunately the state of payphone-related records is extremely poor, with many ostensibly-active PSPs having quietly gone out of business, other PSPs reorganized without reregistering, and states themselves keeping PSP records very poorly. Throw in small-scale COCOT operations and the result is that there really isn't any authoritative database of possible payphones, so this website's map is going to be missing some. It will also include many that are nonfunctional, as today's PSPs seem to do close to zero maintenance and out of service phones stay that way for years.

Some of the nation's largest PSPs have become ghosts, with the phones still operating and able to accept payment, but the PSP completely unresponsive to efforts to contact them. It's a very strange afterlife.

Of course everything around cameras has come down in cost tremendously since then, so palm imaging is probably reasonably priced now, but it lacks a clear enough advantage over better-established methods for anyone to switch over. Besides, just the fact that you have to position your palm the way you do makes it difficult to install them in most practical door situations. Fingerprint sensors turn out to be very compact and fairly intuitive to use.

I scoured Amazon's sales materials around Amazon One very closely, because I found it fascinating that they were seemingly trying to revive the technique. I was surprised they were doing it as a payment device, but it made more sense when I found materials (I think old FCC filings) that suggested that it was originally designed as an access control product and perhaps "pivoted" to payments later. The strangest thing about it though was how unconvincing the sales materials were, it felt like they were really grasping at straws for a reason to select it over other options.

From what I could find it doesn't appear to have been an acquisition; the regulatory paperwork was all filed under some LLC but it seemed to just be a front company for Amazon which is fairly common for that kind of thing. So my best guess is that it was a pet project of someone influential enough to burn some R&D on it, and maybe pivoting to payments and putting them in Whole Foods was thought to maybe be the hail Mary that would turn it into a real business.

The actual integration with the PoS in the stores was clumsy too, they Velcro'd an NFC antenna to the side of the credit card terminal to use to make payments by proxy card. I originally got obsessed with it because I was trying to ID the suspicious device Velcro'd to the payment terminals at Whole Foods!

Amazon was even trying to sell the technology for access control applications, but their sales material were remarkably devoid of any reason to choose it over other biometrics.

Now, you might contend that this is not a list of first-world countries exactly (but rather I sampled the largest countries). You must keep in mind that the use of electronic tabulation in the United States is mostly a response to the very limited budget on which elections are carried out; electronic tabulation is much less expensive than significantly increasing staffing. As a result, globally, electronic tabulation tends to be most common in poorer countries or countries with newer election systems, while hand tabulation is most common in wealthier countries with long-established election procedures.

For this reason, the countries you might go to for comparison (like France and Germany) have largely manual election processes that have often seen few changes since the Second World War.

The Help America Vote Act (2002) had a de facto effect of making the United States a country with much newer election processes, as HAVA requires strict accessibility measures that most European election systems do not meet (e.g. unassisted voting for blind and deaf people). Most US election systems didn't meet them either, in 2002, so almost the entire country had to design new election processes over a fairly short span of time and on a shoestring budget. Understandably, election administrators leaned on automation to make that possible.

It's also important to understand that because of the US tradition of special-purpose mill levies and elected independent boards (like school boards), the average US ballot has significantly more questions than the average European ballot. This further increases the cost and complexity of hand tabulation, even ruling out entirely the "optimized" hand tabulation methods used in France and Ireland.

In the 2026 election, only 1.3% of voters were registered in jurisdictions that use direct-recording electronic machines without a voter verifiable paper audit trail (https://verifiedvoting.org/verifier/#mode/navigate/map/voteE...). 67.8% of voters are registered in precincts that primarily use hand-marked ballots, and the balance mostly use BMDs to generate premarked ballots.

I might allow them more credit if the article wasn't in such an obviously LLM-written style. I've seen a few cases like this, now, where it seems like someone did some very modest technical investigation or even none at all and then prompted an LLM to write a whole article based on it. It comes out like this... a whole lot of bullet points and numbered lists, breathless language about the implications, but on repeated close readings you can't tell what they actually did.

It's unfortunate that, if this author really did collect this data, their choice to have an LLM write the article and in the process obscure the details has completely undermined their credibility.

Most stations can also receive this programming over the internet, another reason for the satellite system is that it provides a completely redundant path for programming delivery. This is important for general reliability but especially so in an emergency.

Historically, radio networks distributed their programming over leased telephone lines. Satellite took over because it was cheaper. That gap has probably narrowed as terrestrial communications infrastructure continues to expand, but the internet struggles with low-latency real-time media, and an arrangement like leased fiber wavelengths to member stations would still be more expensive than the satellite system. There's a lot of member stations in a lot of places, satellite reaches all of them at once.

Unfortunately radiation medicine is pretty complicated and the report gives us very little info, presumably mostly because they don't have very much info. It will take some time and effort to establish more.

What we do know is that they measured 300 CPM at the person's hair, which was probably where they expected the highest count due to absorbed water (likely clothing was already stripped at this point). CPM is a tricky unit because it is something like the "raw" value from the instrument, the literal number of counts from the tube, and determining more absolute metrics like activity and dose requires knowing the calibration of the meter. The annoying thing here is that radiation protection professionals will still sometimes just write CPM because for a lot of applications there's only one or a handful of instruments approved and they tend to figure the reader knows which instrument they have. Frustrating. Still, for the common LND7311 tube and Cs137, 300CPM is a little below 1 uSv/hr. That wouldn't equate to any meaningful risk (a common rule of thumb is that a couple mSv is typical annual background exposure). However, for a less sensitive detector, the dose could be much higher (LND7311 is often used in pancake probes for frisking because it is very sensitive and just background is often hundreds of CPM). Someone who knows NRC practices better might know what detector would be used here.

That said the field dose here is really not the concern, committed dose from ingesting the water is. Ingesting radioactive material is extremely dangerous because, depending on the specific isotopes involved, it can persist in the body for a very long time and accumulate in specific organs. Unfortunately it is also difficult to assess. This person will likely go to a hospital with a specialty center equipped with a full body counter, and counts will also be taken on blood samples. These are ways of estimating the amount of radioactive isotopes in the body. In some cases tissue samples of specific organs may be taken.

I believe that the cavity pool water would be "clean" other than induced radioactivity (activation products from being bombarded by radiation). Because water shields so well the pool should not be that "hot" from this process. Most of those products have short half-lives which, on the one hand, means that they deliver a higher dose over a shorter period of time---but also means they will not longer forever and are less likely to be a chronic problem if they are not an acute one.

I suspect this will get some press coverage and we will perhaps learn more about the patient's state.

Another way we can get at this question is by the bureaucracy of the notification. An 8-hour notification as done here is required in relatively minor cases. Usually for a "big deal emergency" a one-hour notification is required. The definition of such an emergency depends on the site emergency plan but I think acute radiation exposure to a worker would generally qualify.

The root fault with this article, and the resulting discussion, is the extent to which it generalizes over one of the larger organizations in a very complex part of the defense industrial complex. Many parts of KCNSC's operations are absolutely not exposed by this incident. Other parts absolutely are. Determining which fall into which category, and to what extent that is acceptable, keeps quite a few people employed.

As for why you didn't see similar constructions in other cities, this was definitely an unusually large telephone office for the time. In the US, a city exchange of the late 20th century would usually have just hundreds of lines, many of them multi-party. Telephone companies scaled up by building more exchanges, rather than a single very large one. When they got into these kinds of subscriber numbers at an exchange, the F1/F2 cable scheme was in use to avoid this kind of wiring. It does seem to be the case that telephone adoption was unusually rapid in Sweden, I find one (poorly sourced) claim that there were some 4,800 telephone subscribers in Stockholm in 1886 which would very likely make it the most telephone-rich city in the world. The situation of the tower seems to have developed in part because its builder, Allmänna, was consolidating the Stockholm telephone market through acquisitions and made a decision to centralize the many acquired customers onto on exchange.

What I'm a little confused about here is the lack of cables. The other big reason you didn't see constructions like this in the US, even in places like New York City, is because subscriber loops were quickly moved into lead-sheathed, paper-insulated multi-pair cables. These could contain hundreds of pairs. Cables were pretty much reaching maturity when this tower was built. I am curious as to the reason that multi-pair cables were not adopted more quickly in Stockholm, but it may be as simple as the considerable investment in this tower making open wire the preferred option for its short lifespan. In any case, the common claim that underground cables obsoleted the tower rings hollow to me, or at least misses an important detail, as aboveground cables were already in use in the 1880s. I suspect that modernization to cables was just deferred in Stockholm until it happened to also make sense to move to duct or pipe systems. In the US, it was more common that telephone exchanges switched to overhead (aerial) cable to manage exactly the wire sprawl issue that this tower exemplifies, and then only later (if ever) started to bury cables.

This article has more photos of the tower, but unfortunately not much more technical history: https://rarehistoricalphotos.com/the-stockholm-telephone-tow...

And this includes some photos of other parts of the Stockholm telephone network. The tower was not the only impressive construction required to manage this many open-wire pairs: https://thehistoryinsider.com/when-the-sky-over-stockholm-wa...