Old content

Mon, 02 Nov 2026 10:12:42 +0000

Old content

This is the content that was being served before I configured a proper static site generator.

Anki

It is recommended to enable FSRS.

For sorting cards (Review Sort Order), if you are up to date, no order is best because you are going to see all the cards anyway (as of Thu Jul 16 01:47:52 AM UTC 2026, FSRS uses the day as the unit to mark due cards). But if you have a backlog, the current best order is Descending Retrievability.¹

Currently I’m trying a random order because the other orders were showing me siblings next to each other (I’m not using sibling burying or spacing).

If you use Filtered Decks to handle backlogs, you should obviously choose Descending Retrievability.

Other

Someone on Discord suggested using Ascending Retrievability and setting a Maximum Reviews for Day to the true number of cards you want to study per day (you should also disable New cards ignore review limit). This way, you have a small backlog that can help with FSRS parameter training, and you always have a predictable daily load. I haven’t tried this.

Also, I was thinking of setting new cards per day to three times my target review count during the first days, then, 5 or 3 days later, setting new cards per day to my true target review count. This way, the initial momentum is used, I start with the predictable load right away, and then the true target value keeps the load stable.

Chromium

When I switched my desktop environment from KDE to UWSM Hyprland, Chromium started behaving abnormally. It opened normally, but no page loaded; the UI was not frozen, but pages stuck loading forever (even when there was no Internet connection, so pages saying there was no Internet also were not showing; it was just loading). The exception was system pages (like the ones for flags and configuration), which loaded instantly.

Another symptom was that Chromium wasn’t detecting that it was already the default browser (so the prompt to set it as default was appearing). Shortcuts like <Ctrl+Shift+T> were opening new windows instead of new tabs. Also, the UI was being drawn with another font.

For some reason, if I set the environment variable KDE_FULL_SESSION to true (on Hyprland), all these problems were fixed.

After a long debugging session (about two days), I found that Chromium was waiting for the secret storage to load (and on Hyprland my secret storage wasn’t showing a prompt to unlock it). When I set it to KDE, Chromium used KDE-specific methods to load it, so it was able to bypass the prompt and load normally.

Ultimately, if you are switching desktop environments, the solution is to pass the flag --password-store=<your-impl> to Chromium so it loads consistently. The value --password-store=basic uses plain-text encryption but gets rid of all the problems.

Another symptom of this is that whenever Chromium loaded normally, it would clear half of my cookies (signing me out of most of my accounts) every time I started it on a different DE.

UPDATE: --password-store=basic clears cookies on each browser start, so you are forced to use a secret manager; pick your poison.

Rclone

Use rclone config to add remotes interactively. Those remotes can be mounted (in a FUSE layer) or accessed with commands like copy.

Remotes can be layered: you can create a crypt remote and point it to another remote, so you can encrypt your files on the remote.

The command rclone test info can tell you which file-naming scheme the remote supports (run it on the root remote, not on the crypt layer), so you can use larger filenames when configuring the crypt remote (e.g. base32768).

tadashi's notes

Old content

Old content

Anki

Other

Chromium

Rclone