maratc

Street bumps are much more efficient in lowering speed than either "automated controls" or "manual controls". You (plus neighbours, probably) could petition your council to put one (or several) on your street.

Indeed, this route would be about 13,250 km, or about 2,000 km longer than the one TLA suggests.

http://www.gcmap.com/mapui?P=10%B0+24%27+41.4%22+N,+14%B0+31...

Or, using nearby airports: https://www.greatcirclemap.com/?routes=gucy-vmmc

My actual argument is that the theory that he's a puppet being pulled is not a serious one. Much like a chocolate for hunger, it's just an intellectually lazy explanation for people who look for intellectually lazy explanations.

I'm confused. Is he a Putin's puppet or Netanyahu's? He can't be both: these two don't align.

For those out of range of DCF77 and others, there are apps that simulate it on the phone, or this: https://timestation.pages.dev

±10 seconds per year would be quite an expensive quartz movement. To be that reliable anywhere it should be thermocompensated, too. This is the range of Grand Seiko 9F, Citizen Chronomaster, or Bulova Precisionist.

You might wanna take a look at Casio AE-1500WH.

Yet half of the recommendations here are self-hosted this and self-hosted that.

I feel like something is missing from your list of "classic CI vendors" but can't exactly jput my jfinger on jit.

On screens every US government agency already uses sans-serif, as required by "Americans with Disabilities" act[0]. This is not in any way affected by neither previous change from TNR to Calibri, nor by this change from Calibri back to TNR.

[0] https://digital.gov/resources/an-introduction-to-typography

But would associate with "pragmatic" and "efficient"?

The reason almost all books and newspapers use serif typefaces is exactly that: serifs help with readability. It could be argued that serifs help our eye by making each letter more unique, or it can be argued that our eyes have been trained since childhood to read serifs -- by almost all books and newspapers we've consumed. Whatever the cause and the consequence is, serif fonts have advantage on the readability front when we talk about printed communication.

Not going to argue about personal interpretations, and everyone's entitled to have one — including people who have interpretations that we personally disagree with.

Having said that:

    *stately*
    
    adjective
    
    a stately procession. dignified, majestic, ceremonious, courtly, imposing, impressive, solemn, awe-inspiring, regal, imperial, elegant, grand, glorious, splendid, magnificent, resplendent, important, august, formal; slow-moving, measured, deliberate.

Georgia is nice, but rather recent. Garamond, Baskerville, Bodoni, Caslon, Century are all centuries old. If we're talking about the US State department, it would probably be fitting to look at the fonts that were used for US printing and communication (and are still used.)

It's hard to explain, but serif typefaces have centuries of history behind them, with practically all the books (in Europe and America) using some variant of serif since basically the invention of movable type. You can add most of newspapers to this list (notably "Times" part comes from a font being cast for the British newspaper The Times in 1930s.) The Roman Empire is a source of these (just look at the inscription on the Pantheon[0]), so that's for the "Roman" part. Using serif fonts signifies "tradition". Using sans-serif signifies "modernity". Being "stately" is more about the former than the latter.

Interestingly, the building that houses the State Dept[1] has its style defined as "Modern Movement" and "Stripped classical", which is interesting, because it's somewhere in the middle between modern and classical, while not being quite any of them. To me, it looks mostly bland; I'd much rather have an office in Congress building, or Supreme Court building, or the White House, all of which are strictly classical.

[0] https://en.wikipedia.org/wiki/Pantheon,_Rome

[1] https://en.wikipedia.org/wiki/Harry_S_Truman_Building

In a choice of either Times New Roman or Calibri, I would think that Times fits the US State Dept better. Calibri is a relaxed, modern typeface, while Times is classical and majestic. (The word "stately" also comes to mind.)

It would probably be better if State Department would get their own typeface -- as opposed to picking one from MS Office defaults -- but even then, I'd argue for Antiqua style (serif). SCOTUS, for one, is using Century Schoolbook.

P.S. I don't care at all about Rubio, Dem-Rep divide, "diversity" vs "wastefulness" debate, or any of the arguments brought from either side in 2023 (when they changed Times to Calibri) or 2025 (when they switched back).

You seem to not have any answer to my question.

I don't think it matters whether Chrome can add keys to TPM/Secure Enclave (as the article argues) or if it can only read the keys already in TPM/Secure Enclave (as you argue). In my understanding: both ways the key (either new or existing) could be attributed to the hardware owner, and not even an OS reinstall will help. Hence, my question.

From the article:

> The new Chrome protection is known as device-bound session credentials (DBSCs). The measure stores a unique encryption key in a silicon-resident fortress that’s built into the device running the browser. On Windows machines, this fortress is called a TPM, short for Trusted Platform Module. On macOS and iOS, it’s known as a secure enclave. Other platforms have differing names. Recently released versions of Chrome for Windows and macOS generate a key that’s stored in this fortress.

If Chrome can write into TPM/Secure Enclave it's like the best fingerprinting ever?

Gruber himself has written a number of posts critical of Apple, some of them scathingly so.

This whole affair seriously undermines Terry's credibility, however it needs to be said that his take on how RSS readers should work is genuinely new and -- to some audiences -- interesting.

It's as if real people are not all good or all bad, but can do good things, and bad things too.

Now let's count their mortgage debt.

I've tried that and I've got only 2900 errors -- which weren't errors at all just yesterday.

You can set your clock with an iPhone app or a computer with a pair of speakers. https://timestation.pages.dev

I find it kinda amusing that we seem to have an endless and useless discussion on "what version of ruff to use" now when you kinda implied that you have some sort of a solution to these endless, useless discussions -- in a form of "just use ruff."

> upgrade whenever it is convenient

In my codebase, and with my environment, the best answer is never. We'll have to pick a second-best answer though.

I find it hard to look at ruff as at "other dependencies."

First, my other dependencies usually deliver something of value to the customer (and so I deliver my other dependencies to the end-user installation.) Second, when I need to change code to accommodate other dependencies, it is usually limited to a couple of files, sometimes to a couple of modules; this change will touch much, much more than that. Third, my other dependencies at least play nice by implementing semver and bumping a major release on a breaking change.

Nothing of that applies to this change.

> fix issues

Which weren't "issues" at all just this morning.

> many people have a single quotes obsession

Not my problem. My problem is that I want to use them both, as I've been able to for many years.

I'll always use double to surround "can't" and single to surround '8.5" x 14"'. I'll use a context-appropriate pair when adding to existing code. But for all the other cases, I don't want to expend any energy on this. It's a complete non-issue.

> ease of typing them on a US keyboard layout

On both the US and European keyboards single-quotes are easier: no need to press Shift.

So to the practical question: what we're gonna do today in CICD and/or precommit? "Default configuration is always the way" but which one: `ruff<0.16.0` or `ruff=0.16.0`?