The Lab Leak

As you all know, I’ve been obsessed with the origins of COVID-19 and what is clearly the cover-up arising from it. To me, there are two main components to the story. The first is the malfeasance of the press, which swallowed whole the nonsense served up by the Chinese, the Government, WHO, and people like Peter Daszak and relegated the idea that maybe we should investigate the possibility of a lab leak to the domain of the tinfoil hat brigade making it impossible to even be discussed. Most infuriating of all, the press spent a whole year patting themselves on the back for “fighting disinformation” while they were the principal purveyors of it.

Tablet has an excellent article on the press’ disastrous coverage of the controversy. At every turn they chose to support those saying the cause was zoonotic dismissing any other explanation and ignoring the vested interests of those they were quoting. They’re still doing it today and show no signs of admitting that maybe they were wrong. Tablet makes out a pretty good case that their coverage was politically driven and it wasn’t until the change of administrations that it became permissible to even speculate on an alternative explanation.

The second issue is more serious. Everybody now admits—although the government and Fauci denied it for a long time—that the NIH was funding gain-of-function research. As Tablet points out in another article, the term is a euphemism for something that could better be described as “Viral-deadliness enhancement”. Sensible people—including many virologists—are asking why anyone would do such a thing let alone fund it. The usual answer is that will help us fight future pandemics but as the second Tablet article makes clear that hasn’t happened and is unlikely to happen because virus mutations are unpredictable and are unlikely to match what the researchers are ginning up in the lab.

The main takeaway from all this for me is that we need a strong moratorium on gain-of-function research. The last year and a half should have taught us at least that.

Posted in General | Tagged | Leave a comment

Rethinking Email

Everyone seems to have a love/hate (for some, a mostly hate) relationship with email. Some even speak of it in terms of punishments appropriate to the ninth circle of hell. I don’t get that exercised probably because I’m parsimonious about giving out my email address and don’t have a lot of spam to deal with. Others aren’t so lucky.

Lars Wirzenius says that while he may get 5 legitimate emails a day, he also gets about 400 spam emails a day. Because he’s involved with open source projects, he often gets legitimate email from people unknown to him so he can’t just delete email from anyone not in his address book. Clearly things are out of control for him so he’s considering what can be done. He has a nice post that rethinks email and how it should work.

The TL;DR is two part:

  1. Emails would be digitally signed
  2. A digital stamp, provided by the recipient would be required before an email would be accepted.

The first of those suggestions has been around for a while and suffers from what such schemes always suffer from: key control. How do you issue key pairs, make the public key generally available, and ensure that they are from whom they purport to be.

The second suggestion is new to me but, apparently, has been around for a while. The main feature of a digital stamp is that they’re completely under the control of the recipient who issues them. They can be revoked, they can be one-time-use, or even restricted to specific days or time. It seems like a good idea and easier to implement than giving everybody one or more key pairs required by the digitally signed email proposal.

Read the post for the details. I’d like to see at least some of Wirzenius’ ideas implemented. I’d especially like to see all emails signed and encrypted but besides the problems with key control there’s the fact that the big players, like Google, have no interest in allowing their users to keep information private.

Posted in General | Tagged | Leave a comment

An Emacs Build Script for macOS

Colin McLear (mclearc) has a script for building Emacs on macOS. He uses it to build Emacs on the M1 MacBook pro running Monterrey 12.0.1. I see lots of requests from people asking where they can find an Emacs binary for some particular operating system/machine. When the machine is a Mac, the most usual advice is to use Homebrew, which is a good solution but for those who want to build from scratch so that they get exactly what they want, it’s good to have a script for the build. Even if you need to adjust some of the build parameters for your use case, once you do, you can easily build updates or install Emacs on a new machine.

The script comes with some (5) patches that you may or may not want to apply. It’s easy to omit the ones you don’t want. Similarly, it’s easy to change the configure options if you want to add or delete from the set the McLear chose.

There’s a lot to be said for the strategy of writing a script to build Emacs. For some reason, I’ve never done that and always have to look up my notes to remind me of the magic incantation. With a script, you just have to run it to build a new Emacs. I’m going to take McLear’s script and adopt it for my particular environment. I can’t quite think why I haven’t done so already.

Posted in General | Tagged | Leave a comment

Emacs 28 Pretest 1

Stefan Kangas writes to tell us that Emacs 28.0.90, the first Emacs 28 pretest, is available at the usual places. That’s good news because it means that Emacs 28 is within sight.

If you can, be sure to try it out and let the developers know of any problems you find. As usual, thanks to all the selfless engineers who are donating their time and talents to the Emacs development effort. These guys are heroes and we all owe them. There’s lots of good stuff coming in Emacs 28, including native compilation, so this should be a “big” release.

Posted in General | Tagged | Leave a comment

Red Meat Friday: See? This Is Why We Needed The Revolution

As a nice coda to yesterday’s post, Liam Proven offers this bit of heresy:

Spaces around em-dashes? Reason enough to split from Great Britain.

Actually, this is interesting. I didn’t realize em-dash spacing was a British/American thing. I sometimes see spaces around em-dashes and it always looks wrong to me. It seems like it negates the whole purpose of the dash. Of course, it’s not a moral question. Folks are free to put spaces around the em-dash if they like. Even if it is blasphemous.

Posted in General | Tagged , | Leave a comment

Em-dash, The Video

Family obligations are intervening today so all I have to offer you is this video paean to the em-dash. If you’ve been around Irreal for a while, you know I’m a big fan but not nearly so much as Alexis Gay.

Thanks to John Gruber for the link.

Posted in General | Leave a comment

Emacs Dev Update 2021

Another talk in the 2021 EmacsConf program is John Wiegley’s video on what’s coming in Emacs. Almost all of the talk is about new features in Emacs 28, of course. The talk is only 7 minutes, 17 seconds long so you should watch it if you have any interest in Emacs and where it’s going.

Here’s a list of the features Wiegley covers, cut from the talk transcript:

  • Native compilation
  • Build with Cairo by default
  • New mode, but off by default: context-menus
  • Tab-bar and tab-line received many enhancements
  • A command can marked as specific to a mode
  • Transient input methods
  • show-paren-mode is enabled by default
  • We now have a Non-GNU ELPA
  • repeat-mode
  • project.el has dozens of new commands
  • Shorthands for Lisp symbols

Again, if you’re an Emacs user, you should definitely spend the time to watch this.

Posted in General | Tagged | Leave a comment

Orgdown

This is another post that discusses a talk from EmacsConf 2021. This one, by Karl Voit, is about the Org-mode markup language. Org markup is superior to its competitors—sorry Markdowners, you know it is—but suffers from the fact that it’s strongly tied to Emacs. Part of the problem is that the name “Org-mode” is used both for the markup language and for the implementation of the Emacs package that includes the language and much more.

Voit’s suggestion, as discussed in his talk The use of Org mode syntax outside of GNU/Emacs, is to consider the markup language as a separate entity and rename it to Orgdown to avoid confusion between the language and its implementation in Emacs. In addition to his post about Orgdown, you can watch his EmacsConf talk about it.

He has more to say, of course, than just, “Hey, let’s rename the Org-mode markup language.” His proposition is well thought-out and already supported by a repository on GitLab with documentation. His video is just over 12 minutes and definitely worth watching if you have any interest in the Org-mode language even if you aren’t an Emacs user. It’s also enjoyable to watch because it has excellent production values.

There has been some pushback on his proposal but most of it seems to be borderline ankle biting about his choice of name, “Orgdown”. There’s a lot more to his proposal than a name, of course, so be sure to read or watch what that proposal is before you make up your mind about it.

As an Emacs user, none of this is vital to me but I do think it’s a good idea and that it could provide a much needed standard lightweight markup language. Markdown, of course, was intended to fill that roll but it has splintered into several dialects. Voit’s suggestion is intended to avoid that.

Posted in General | Tagged , | Leave a comment

Org Executables

Over the weekend, the 2021 EmacsConf took place and presented a slue of great talks. Irreal will mention at least a couple of them starting with Tom Gillespie’s astounding talk on how to make Org files executable.

The first question is what does it mean to make an Org file executable? The TL;DR is that you add some boiler plate to the Org file so that you can call it as if it were a shell script. The resulting file works under all the common shells including, even, powershell. That turns out to be harder than you might think but happily Gillespie has made the process essentially turnkey.

He has added a package to Melpa to initialize an org file with all the needed boiler plate so that all one has to do is add the code block to implement whatever the script is intended to do. You can get all the details from the video of the talk or from the transcript of it. Both are available at the above link.

The video it short—only 7 minutes, 9 seconds—so it should be easy to fit in. People are always asking how to make Elisp programs executable without explicitly calling Emacs. Gillespie’s package lets you do this almost automatically. Take a look at the video; you have nothing to lose but seven minutes.

Posted in General | Tagged , | Leave a comment

V7 and the History of Unix

Among Unixheads, the Seventh Edition (V7) holds a special, almost mystical, place. Many consider it the best of the various Unix versions. In his Minix book, Tanenbaum remarks, “It is sometimes said Version 7 was not only an improvement over all its predecessors, but also over all it successors.” The source code has long been available and I have always found it the easiest to read and learn from.

Chris Siebenmann has a blog post with his own take on the importance of V7. He agrees with most of what I’ve written above but notes that V7 is historically important because it is the base from which (almost) all subsequent Unices are derived. If you understand V7, you’re well on your way to understanding everything that came afterwards.

Siebenmann goes further and says that V7 was the last pubic release from the CSRC (the Bell Labs researchers who invented Unix) and thus represents the last release made by those who really understood the Unix way. Those who came later, Siebenmann says, brought their own sensibilities to table and lacked the appreciation and understanding of Unix that its originators had.

If you like Unix and are interested in its history, you should definitely take a look at Siebenmann’s post. It’s interesting and reasonably short.

Posted in General | Tagged | Leave a comment