It's also useful to wrap/tag IDs in structured types. That makes it easier to avoid errors when there are multiple type parameters such as in the Microsoft graph API.

The text doesn't use an `f`. If you copy from e.g. the 1700 passage you get `ſ` not `f`.

Probably people are confused by ligatures. Indeed it is a long S.

hmm you're right, I guess my eyesight is worse than I thought

This is correct. And if you don't like that font's long-s, you can fix it with

document.body.style.fontFamily = "Baskerville";

Baskerville has a nice long-s. TNR is also not bad. Garamond is passable.

thanks for the Baskerville recommendation.

on edit: liked the Garamond better, since the font is a bit thicker, checked it on "ſpake" and was obviously a long S whereas on the thinner Baskerville still looked like an f to me. Although the original text was perhaps too thick for me.

I can comprehend most of the text back to 1300, if slower than Modern/Present Day English. It helps to know the old letter forms, and some of how Shakespearean (Early Modern), Middle, and Old English work. It also helps sounding it out.

Past that, I'm not familiar with Old English enough to understand and follow the text.

Knowing that W is a late addition to the alphabet and would have been written UU or VV suddenly makes uuif obvious.

I could intuit the pronunciation but I didn’t make the connection from “wif” to “woman” in general. In hindsight I should have, after all we have words like “midwife” which doesn’t refer to a person’s actual married partner.

"Wif" meant woman at the same time that "wer" meant man and "man" meant person.

Man changed to mean only a male person, and we lost wer except in the word "werewolf".

I’m a native English speaker and I think this is an easier jump if you know other Romance languages. In Spanish and Portuguese “woman” and “wife” are often the same word, “mujer” and “mulher” respectively.

Also French femme. It isn't limited to Italic languages either. There's also German Frau, Dutch vrouw, Irish bean.

Czech žena

Simon Roper has a spoken equivalent for Northern English -- https://www.youtube.com/watch?v=90Zqn9_OQAw.

He has a spoken one that isn't Northern English specific too: https://www.youtube.com/watch?v=842OX2_vCic

"From Olde English to Modern American English in One Monologue"

LOL I'm from Northern England and I tapped out ~1850.

I remember my father and I having to enable the subtitles for Rab C Nesbitt when I was a kid. There are areas of Scotland (especially the isles) which are probably still unintelligible to most of the British population I would wager.

for a very specific dialect of Northern English. I struggled to understand much beyond 1950, and I had a good ear

Mistral have small variants (3B, 8B, 14B, etc.), as do others like IBM Granite and Qwen. Then there are finetunes based on these models, depending on your workflow/requirements.

True, but anything remotely useful is 300B and above

That is a very broad and silly position to take, especially in this thread.

I use Devstral 2 and Gemini 3 daily.

Devstral 2 is 123B parameters. Thats less than 300B, but its still much larger than the 3-14B models GP was talking about.

I'm using gitolite + cgit for local repositories. I tried Gitea for a while but didn't like the forced user/repo flat structure inherited from being a GitHub clone, and didn't need the additional features that Gitea/Forgejo provide.

Cannot say. Saying, I would know. Do not know, so cannot say.

There are several stand-out episodes in season 1 and 2, as well as several stand-out scenes; plus the second half of season 2 is not mediocre. You also miss out on character and world-building that happens in those episodes that help contextualize a lot of the later seasons.

Plus, many reactors now have liked season 1 a lot better than when it initially aired.

From [1] "Forgejo was created in October 2022 after a for profit company took over the Gitea project."

Forgejo became a hard fork in 2024, with both projects diverging. If you're using it for local hosting I don't personally see much of a difference between them, although that may change as the two projects evolve.

[1] https://forgejo.org/compare-to-gitea/

It can depend a lot on different factors like:

- familiarity with the accent and/or speaker;

- speed and style/cadence of the speech;

- any other audio that is happening that can muffle or distort the audio;

- etc.

It can also take multiple passes to get a decent transcription.

You missed a giant factor: domain knowledge. Transcribing something outside of your knowledge realm is very hard. I posted above about transcribing the commentary of a motorbike race where the commentators only used the slang names of the riders.