Wait. I still export NFS mounts from my TrueNAS server and make them available to all other machines on my LAN (music, books, documents, photos, etc). The article and comments here give me the feeling that NFS is outadated and shouldn't be used anymore. Am I doing things wrong?

I do exactly the same thing, and it works beautifully. We can't really be doing it wrong if it's working!

Very skeptical that this would work for me. None of the topics that Kagi chooses to "cover" in their seven or so stories for the day resonates with what I'd want to read. That's exactly why we have feeds that you can tune to your tastes and so on. Getting rid of endless scrolling and such might be a good thing though.

There's also the pass-otp extension that generates OTPs!

https://github.com/tadfisher/pass-otp

The pass android app is really nice too

https://play.google.com/store/apps/details?id=dev.msfjarvis....

It also works in termux

The Android Password Store application by msfjarvis was archived last year. It was forked and greatly updated by agrahn. There are APKs on GitHub Releases and F-Droid, but not Google Play Store.

https://github.com/agrahn/Android-Password-Store

Thank you for sharing. My solution has been to dump small scripts like this in ~/bin:

    #!/bin/sh
    
    set -eu
    
    k=$(pass ARG)
    oathtool -b --totp "$k"

> This app isn't available for your device because it was made for an older version of Android.

And no, those apps don't work great, because they involve some clunky GPG app.

The app in the Google Store is no longer maintained, hence the warning.

It is however available in F-droid [1], and the newer versions don't need the secondary app and do everything internally.

[1]: https://f-droid.org/packages/app.passwordstore.agrahn

Agreed, GPG is not the most intuitive tool, but once you are familiar enough with it, it opens some doors.

For me termux and pass (from F-droid) have solved my password management for many years. I never have to struggle finding passwords. The security aspect of it is the least I care about, it's the convenience and simplicity of it.

Since the passwords are all just files on a disk inside a directory tree, you can use any old file system tools to find your passwords. Same for MFA. I store the base32 string inside pass and that's the end of it.

I prefer a more "physical" explanation - you have two carriers: sin(wt) and cos(wt), and you're modulating bits I and Q onto the two carriers and adding them up before transmitting. Now, mathematically, that's the same as representing the two bits as I+jQ and multiplying it with cos(wt)+jsin(wt). Demodulation is simply multiplying that output with the complex conjugate cos(wt)-jsin(wt), which in physical terms translates to mixing with a local oscillator output and low pass filtering.

Why would you want two carriers?

Twice as much information.

My go-to for I/Q is: Having two allows you to represent negative frequencies. With a normal, real signal, this is of course impossible (negative frequencies will automatically mirror the positive ones), but if you have a signal centered around e.g. 1 MHz, there's room for above-1MHz and below-1MHz to be meaningfully different. And _that_ allows you to get a complex signal (I/Q), once you pull the center down to 0 Hz for convenience of calculation.

I have only two peeves with typst.

1. They should have carried forward the latex standard as-is for math, instead of getting rid of the backslash escape sequence, etc.

2. There is no way to share a variable across a file's scope - so can't have a setting that is shared across files - not even with state variables.

Other than this, typst is solid, and with the neovim editor and tinymist lsp, is great to write with.

Regarding point 1: I'm so glad they didn't keep the math syntax, there's finally progress in math text input! E.g. we can now write

  $
    ZZ &= { ..., -1, 0, 1, ... } \
    QQ &= { p/q : p, q in ZZ }
  $

  $
    a = cases(
      0 & quad x <= 0,
      mat(1, 2; 3, 4) vec(x, y) & quad x > 0
    )
  $

instead of

  \begin{align*}
    \mathbb{Z} &= \{ \dots, -1, 0, 1, \dots \}, \\
    \mathbb{Q} &= \left\{ \frac{p}{q} : p, q \in \mathbb{Z} \right\}
  \end{align*}

  \[
    a = \begin{cases}
      0 & \quad x \leq 0, \\
      \begin{pmatrix}1 & 2\\ 3 & 4\end{pmatrix}
      \begin{pmatrix}5\\6\end{pmatrix} & \quad x > 0
    \end{cases}
  \]

Regarding point 2: you can put your settings in a file `settings.typ` and import it from multiple files.

> Regarding point 2: you can put your settings in a file `settings.typ` and import it from multiple files.

Let's say I have 3 flavors of settings and 10 different typ files - normally I'd just have 3 flavors of top.typ (top1.typ, top2.typ, top3.typ) with the correct settings for each flavor with settings proagated to all 10 files. Compiling top1/top2/top3 would then create flavor1.pdf, flavor2.pdf, and flavor3.pdf

Now how do I do it with settings1.typ, settings2.typ and settings3.typ? I have to go into the 10 different files and include the appropriate settings file! Or employ hacks like creating a common settings.typ using bash in the Makefile and including the common settings.typ in the 10 different files.

Edit: This is an actual use case - I'm helping with a resume, and have 3 different resume styles - a resume, a cv, and a timeline - and different files like education, work experience, honors, awards, publications, projects, etc and the level of detail, style, and what is included or not in each is controlled by which resume style is active. In latex I did this using \newcommand and the ifthenelse package.

In typst, I have had to resort to passing these global settings as arguments to functions spread across these different files, so each resume item (function) instantiated from the top file has a bunch of parameters like detail_level = 1, audited_courses = true, prefix_year = false, event_byline = true, include_url = true, etc., which make the functions unweildy.

Just have a master settings.typ that you import in top1.typ, top2.typ and top3.typ?

Alternatively, you can pass global settings at build time with `typst c --input name=value`

Maybe I misunderstood though, if you can link to an actual example (gist or something) I'd be happy to try and give a concrete solution.

> Just have a master settings.typ that you import in top1.typ, top2.typ and top3.typ?

Yes, but each included file (like education.typ, publications.typ, etc) should also get these settings propagated from top - which typst doesn't allow - the appropriate settings need to be included in each of these files.

> you can pass global settings at build time with `typst c --input name=value`

This is something I did not know - will check.

You can import settings.typ in top.typ, and then import top.typ in education.typ. This way the variable/function definitions will propagate.

Or you can import settings.typ in all files that need it (education.typ, etc.).

What doesn't work is to have a file like top.typ contain

  import "settings.typ": *
  import "education.typ": *

and hope that this will make settings available in education.typ. Because each .typ file is "pure" in the sense that it only knows the variables/functions that are defined in the file, or imported. This way you don't have a file magically affecting the bindings available in another file, which is nice.

It's true there are cases where you'd like something like the above. Currently you can do something like that using states and context (basically putting the "settings" into the document and retrieving that) but it's not so nice. In the future the plan is to make this nicer by allowing custom type definitions (and having show rules and set rules work with them as they work with built-in types).

Agreed. I’ve done a far bit of math in both and typst’s choices are way more memorable and ergonomic.

It’s not like keeping the syntax would really gain typst anything besides folks not having learn new things.

You could use unicode-maths?

Looks very good. Was looking to replace ltex (which is really slow), but for some reason the nvim-lspconfig filetype setting for harper doesn't seem to have (la)tex listed as a default, although markdown and typst are listed. Anyone knows why?

Harper maintainer here

We've had some contributors have a go at adding LaTeX support in the past, but they've yet to succeed with a truly polished option. The irregularity of LaTeX makes it somewhat difficult to parse.

We accept contributions, if anyone is interested in getting us across the finish line.

CCTV capture of complete takeoff: https://x.com/ShivAroor/status/1933165937399648447

I'm told not to speculate, but I'm going to do it anyway because this video clearly shows there was an issue going to full thrust. It's an extremely rare dual engine failure or pilots' error not calling up full thrust to keep it flying. Very possible this is the famous bird strike issue Capt. Sullenburger experienced in 2009.

But doesn't seem like a bird strike issue here, right? And given the rarity of a dual engine failure, seems to point to not calling up full thrust? But seems to me that this kind of error would be more common without any technical safeguards?

It's interesting that up to about 30s in the video you can see the plane climbing normally, then it loses power and starts falling, about 10s after take off.

Apparently the pilot radioed "Mayday…no thrust, losing power, unable to lift!” 11 secs after takeoff.

It would seem to fit with a bird strike on both engines. Or contaminated fuel I guess. The stuff about flaps seems irrelevant.

Quite likely this and Jeju Air crash in Korea and Sully landing in the Hudson were all caused by bird strike taking out both engines.

There is a lot of dust at the 20s mark, I’d assume that there shouldn’t be dust on normal takeoffs at busy airports.

It’s possible they had to use part of the runway that most other takeoffs don’t need to extend to. Just pure speculation.

Is it normal to have human operators pointing the camera around like that? It almost look like they expected something to happen.

It's not uncommon, people like planes.

Extremely slow takeoff. The engines appeared to have both quit. And the plane did a slow descent and crash.

Those slow seconds of falling must be psychological torture. If I'm in a plane crash I want it to be instantaneous.

It looks like it was fast enough that most people on board probably didn't realize they were about to crash, or they crashed within seconds of the realization. As torturous as that must have been, it was thankfully very very brief.

Apparently, there's a survivor.

https://x.com/sidhant/status/1933160167816007842

“Thirty seconds after take off, there was a loud noise and then the plane crashed. It all happened so quickly,” said Ramesh, speaking to the Hindustan Times. He said he “impact injuries”, including bruising on his chest, eyes and feet but was otherwise lucid and conscious. https://www.theguardian.com/world/live/2025/jun/12/air-india...

Seat 11A. That's interesting, typically most survivors are located in the back, this one was in the front-center.

The plane seemed to come down tail down so I guess that end would have absorbed the shock more. 11A is front left by the way.

I meant the section of the plane was between front and center, behind business class.

Someone on the r/aviation thread speculated 11A would be right above the gear assembly and is hardened.

I cannot comment on this specific point, but /r/aviation in general is terrible after an accident.

11A was next to the emergency exit. There was a comment on Reddit suggesting he actually bailed just before impact.

That doesn't make sense. 100+mph into terrain is going to go way worse for you out of a seat than in it.

You ~cannot~ don't want to "bail just before impact"

A plane at takeoff is pressurized, and that pressure holds the doors closed, as well as the physical locks. You cannot open it.

Don't believe random reddit comments. Average people know less than nothing about planes.

Speaking of random people knowing less than nothing: I believed that at takeoff and landing, planes were slightly overpressurized to increase airframe rigidity. I think I got that impression from a very old pilot, so either it used to be true or it was never true and I'm just wrong.

This person probably did not bail out of the plane in order to survive, but maybe you COULD open the doors at takeoff and landing, not that you want to.

Additional edit: I've actually flown a few times while running the barometer on my phone for funzies. I might be able to find a log of data to confirm or deny my mistaken belief! It's fun to do because you can see the pressurization increase signalling that the pilots are preparing for descent even before they tell you!

The pressure inside is not more than atmospheric pressure at the ground. In fact I think they only maintain the pressure of around 1000m or so. There would be absolutely no point pressurising the cabin higher than atmospheric pressure at sea level and if they did you'd feel it before the plane took off.

They redact some part of the text on the ticket, but leave the scancode unredacted, which contains all of this text and more :P

I call bullshit.

Looking at the "mock" document (https://github.com/iamgio/quarkdown/tree/main/mock) which is supposed to be a comprehensive and detailed guide for all visual elements, I don't see ways of getting anything other than basic markdown tables. How do you get merged cells? Cell formatting? Typst has some nice ways of implementing sophisticated grids and tables.

Also how do you implement things like different page numbering for front matter content and the main content? In general, the "simplicity" of markdown seems to be taking away a lot of granular control that people use LaTeX and Typst for.

...accessed through Obsidian (esp on mobile) -- On Android, you can "Open folder as vault"

Or neovim with FzfLua (on laptop)