timoteostewart

In a similar vein: "The Horse, the Wheel, and Language: How Bronze-Age Riders from the Eurasian Steppes Shaped the Modern World" by David W. Anthony

https://press.princeton.edu/books/paperback/9780691148182/th...

Agree with your observation. Blake and Durer both worked in printmaking. I wonder if the processes and aesthetics there resulted in some detectable affinity between their works.

site hugged to death. Wayback:

https://web.archive.org/web/20260226093719/https://www.dvd30...

At the time the blog post was written, the .torrent file was not yet posted to tug.org.

I imagine software updates might bring improved support for various media codecs, or UI enhancements, or better Bluetooth compatibility, etc.

Can’t help but think of the 2002 Ted Chiang novelette “Liking What You See” and its tech “Calliagnosia,” a medical procedure that eliminates a person’s ability to perceive beauty. Excellent read (as are almost all his stories, imho).

https://en.wikipedia.org/wiki/Liking_What_You_See:_A_Documen...

FWIW, I find the high-level overview more useful, because then I can write a script tailored to my situation. Between `bash`, `aws` CLI tool, and Powershell, it would be straightforward to programmatically apply this remedy.

Here's something quick that ChatGPT ginned up: https://chatgpt.com/share/293ea9d5-b7ac-4064-b870-45f8266aea...

Not to be confused with Adam Gordon Bell, who is still very much alive.

https://news.ycombinator.com/user?id=adamgordonbell

https://adamgordonbell.com/

It’s a small detail, but I appreciate when a command-line tool offers both short and long options for all the switches. Short so I can type them quickly for manual use, and long for when I use the tool in a script and want the command invocation to be somewhat self-documenting.

I bet you’re right. I missed the snark.

Article seems clearly about 23.04, which is indeed Lunar Lobster.[0][1]

[0] https://old-releases.ubuntu.com/releases/lunar/

[1] https://canonical.com/blog/canonical-releases-ubuntu-23-04-l...

By contrast, 24.04 is Noble Numbat.

https://canonical.com/blog/canonical-releases-ubuntu-24-04-n...

(2023)

Fascinating topic. There are two ways the user/client/browser receives reports about the character encoding of content. And there are hefty caveats about how reliable those reports are.

(1) First, the Web server usually reports a character encoding, a.k.a. charset, in the HTTP headers that come with the content. Of course, the HTTP headers are not part of the HTML document but are rather part of the overhead of what the Web server sends to the user/client/browser. (The HTTP headers and the `head` element of an HTML document are entirely different.) One of these HTTP headers is called Content-Type, and conventionally this header often reports a character encoding, e.g., "Content-Type: text/html; charset=UTF-8". So this is one place a character encoding is reported.

If the actual content is not an (X)HTML file, the HTTP header might be the only report the user/client/browser receives about the character encoding. Consider accessing a plain text file via HTTP. The text file isn't likely to itself contain information about what character encoding it uses. The HTTP header of "Content-Type: text/plain; charset=UTF-8" might be the only character encoding information that is reported.

(2) Now, if the content is an (X)HTML page, a charset encoding is often also reported in the content itself, generally in the HTML document's head section in a meta tag such as '<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>' or '<meta charset="utf-8">'. Now just because an HTML document self-reports that it uses a UTF-8 (or whatever) character encoding, that's hardly a guarantee that the document does in fact use said character encoding.

Consider the case of a program that generates web pages using a boilerplate template still using an ancient default of ISO-8859-1 in the meta charset tag of its head element, even though the body content that goes into the template is being pulled from a database that spits out a default of utf-8. Boom. Mismatch. Janky code is spitting out mismatched and inaccurate character encoding information every day.

Or to consider web servers. Consider a web server whose config file contains the typo "uft-8" because somebody fat-fingered while updating the config (I've seen this in random web pages.). Or consider a web server that uses a global default of "utf-8" in its outgoing HTTP headers even when the content being served is a hodge-podge of UTF-8, WINDOWS-1251, WINDOWS-1252, and ISO-8859-1. This too happens all the time.

I think the most important takeaway is that with both HTTP headers and meta tags, there's no intrinsic link between the character encoding being reported and the actual character encoding of the content. What a Web server tells me and what's in the meta tag in the markup just count as two reports. They might be accurate, they might not be. If it really matters to me what the character encoding is, there's nothing for it but to determine the character encoding myself.

I have a Hacker News reader, https://www.thnr.net, and my program downloads the URL for every HN story with an outgoing link. I have seen binary files sent with a "UTF-8" Content-Type header. I have seen UTF-8 files sent with a "inode/x-empty" Content-Type header. My logs have literally hundreds of goofy inaccurate reports of content types and character encodings. Because I'm fastidious and I want to know what a file actually is, I have a function `get_textual_mimetype` that analyzes the content of what the URL's web server sends me. My program downloads the content and uses tools such as `iconv` and `isutf8` to get some information about what encoding it might be. It uses `xmlwf` to check if it's well-formed XML. It uses `jq` to check whether it's valid JSON. It uses `libmagic`. There's a lot of fun stuff the program does to pin down with a high degree of certainty what the content is. I want my program to know whether the content is an application/pdf, an iamge/webp, a text/html, an application/xhtml+xml, a text/x-csrc, or whatever. Only a rigorous analysis will tell you the truth. (If anyone is curious, the source for `get_textual_mimetype` is in the repo for my HN reader project: https://github.com/timoteostewart/timbos-hn-reader/blob/main... )

Would you consider rolling your own? Python’s goose3 has worked well for me in article extraction. It seemed to be successful more often than trafilatura and newspaper3k.

Can’t help but see the affinity between this writing format and the classic Codeless Code stories and parables:

http://thecodelesscode.com

- reading an algos book (if you haven’t) might be helpful: Aho et al., CLRS, Sedgwick

- on LC, start with easy algorithm problems and sort by Acceptance in descending order. As you work the problem, talk aloud about your thought process and what you’re doing and where you’re headed. This is good practice for narrating your work during an interview

- maybe set a timer so if you’re truly stuck then you can pull up the solution and study it. Next time you see a similar problem or class of problem, you’ll be ready

- if you have a particular particular field or area you would like to work in, determine what kinds of algos or data structures might be particularly pertinent. For example, if you might work with storing and looking up strings, dig into trie structures. Or maybe it would be more suitable to dig into branch and bound strategies. Try to tailor what you’re learning to what you would find useful

Not Central Texas (e.g., Austin)

Keywords of use to you might be “mock data” “mocks” and “mocking”. There are lots of tools, even for generating specific data types (names, emails, json, location coordinates, etc. etc.).

3. Authoritative lists cannot contradict each other.

2. If a list calls itself authoritative, it is.

Coming soon:

“Falsehoods programmers believe about authoritative lists”

Wired sometimes paywalls its articles, is probably why.

I am currently in the process of setting something up for our seven-year-old. My project is to set up a squid forwarding proxy server and have the family computer in the living room utilize that proxy server as its Internet connection. As usual, I am making this whole enterprise harder on myself by configuring the squid server to be able to dynamically change which WAN connection it uses dependent on which port is accessed by the client computer on my local network. Port 3128 means WAN1 (Spectrum cable), port 3129 means WAN2 (AT&T fiber). Step after that will be setting up port 3130 means outgoing VPN interface. Currently slogging through ip tables, routes, and rules, which isn’t my wheelhouse. :-D

We have pi-hole too, primarily for blocking ads and call-homes.

(2021)

@Tomte, you may be conflating two concepts in software distribution. Yes, TeX Live is also distributed via mirrors (typically, FTP sites). But with the BitTorrent protocol, there are not mirrors in this same sense. There are just the seeders and leechers who are the clients/participants in the swarm.

In a sense, by starting to seed last night, I really was "preseeding" so that by the time the announcement is made, there are at least several seeders already available to service the many new leechers who will only begin torrenting once the official web page is updated.

If the definition of "released" is that it's on the official web page, then I agree with you. Karl can't update the web page until I give him the torrent file, and so there's a lag time between when I begin seeding it and when the official web page is updated. Initiating seeding at the same time (or close to the same time) that the web page is updated would be a level of coordination and precision across time zones and continents that is perhaps above and beyond what's needed.

That said, I'm sorry it's sowing confusion. I can see where you're coming from on that score.

The installer in the ISO that is the topic of the article installs official 2024 TeX Live. I tested it via installing it to confirm this prior to creating the torrent.

The torrent file at https://www.tug.org/texlive/acquire-iso.html at the time of this writing is still the 2023 TeX Live ISO, and so yes, _that_ installer will install 2023 TL.

They kind of threw in the kitchen sink on this one, and they admit it:

    Platforms
    The iso image again [Ed.: after a while of it not] includes binaries for all platforms. For the last several years, some binary sets had been pruned, but this year, we are not creating a physical DVD as a user group benefit, so may as well include everything again. Also, even a maximimally-pruned image is too large to fit on a single-layer DVD, so no benefit for the 2024 volunteer burners. More info.

Source: https://tug.org/texlive/pretest.html