I love beets - the one thing I can't figure out is how to set the genre very wide.

I like having a small number of broad genres - Rock, Hip-Hop, Jazz etc - but the tagging comes up with hundreds of distinct genres :(

I have this problem too. I find it completely useless to have tags like genre=Post Rock Jazz Fusion" or whatever with basically one band in each genre.

The other thing I've never quite got right is how to deal with classical music and popular music with multiple pressings. A lot of the tagging structure seems oriented around popular music with just one pressing. But I have like 10 different recordings of The Planets and several versions of Red Hot Chili Pepper's Californication, for example.

I assume lastgenre with canonicalization[0] enabled is what you need, along with count=1 if multiple genres are an issue.

[0] https://beets.readthedocs.io/en/stable/plugins/lastgenre.htm...

I think I'm using that already.

Limiting to one genre I don't think will fix it - what I want is to define the allowable values for genre, and then limit to one.

It's probably better with the limit one though!

Set whitelist to a file path and then add a file with each genre that you want to keep on a new line. You can use the top-level genres in this file to base it off (except the whitelist isn't YAML, just a genre per line): https://raw.githubusercontent.com/beetbox/beets/master/beets...

Be sure to enable canonical so it converts the specific genres into their parent genre.

There's a whitelist option. Just read the docs, really, lastgenre is very configurable.

I use lastgenre plugin with a short whitelist.

I use Make with GNU Stow for dotfiles targeting different operating systems, with a Nix Flake for shell tools: https://github.com/ADGEfficiency/dotfiles/blob/main/Makefile

It works fine - most of my time is still spent in configuring Neovim ^^

The cynical thing is to interpret something that talks about monetization as negative - it's a good thing Datasette is finding a way to make money.

Great tool that fills out the SQLite ecosystem well - I always have a server running when I'm working with applications with SQLite databases.

The Softbank line was definitely a joke.

> I use AWS EC2 for Waitlist's backend python webserver, RDS for the postgres database, S3 for file storage, and an Elastic IP. I use T2 and T3 instances. My AWS bill would be $200-300 a month

My guess is that RDS is eating up the cost here?

I've been using Litestream on datasciencesouth.com - it has flaws but if you can get away with it, it's much cheaper than RDS.

The thing about RDS is that you’re paying for database backups and failover etc to be someone else’s problem. Given that the data is often an extremely critical art of the application and the high chance that you are probably not doing it right if you’re not an expert it’s often worth it to pay for managed db. RDS is a pretty raw deal in that space though. Someone else rightfully pointed out that you can get Supabase managed db for $30 USD per month which is significantly cheaper

Rds starts at $15/month so how is $30 significantly cheaper?

This is actually possible - if you have a biased dataset, then more data is bad.

More data will fix variance problems, but not bias.

This is also why it's a bad idea to read propaganda outlets to "stay more informed".

> Avoid wrapping the whole response in backticks.

I have often been asking Chat GPT to output things in backticks to avoid formatting of Latex that I want to copy into Markdown.

I appreciate this prompt is for Copilot, not Chat GPT, but it does highlight the curious situation where we want to overwrite the system prompt in a legitimate way.

The next evolution of a product like Chat GPT or Copilot should allow the user some ways to customize the system prompt in legitimate ways.

In this case a simple toggle that changed the system prompt makes more sense that the user prompt contradicting the system prompt.

The other toggle I wish I had was to stop Chat GPT writing a summary at the end of a message.

The Hypermodern Terminal Toolbox is a collection of tools I use as a terminal first developer:

- Kitty for a GPU accelerated, highly customizable terminal, - Zsh for a shell & Prezto for Zsh configuration, - Neovim as a text editor, - Tmux for managing multiple terminals, - Starship for a pretty prompt, - Ripgrep for searching text files, - fzf for fuzzy searching, - Exa for listing files, - Bat for viewing files, - Sad for find and replace in text files, - jq for working with JSON, - zoxide for navigation, - Tig for viewing Git history, - direnv for environment variable management, - Lazydocker for Docker, - Markserv for previewing Markdown, - ngrok for exposing local servers to the internet.

I'm interested in this - I've just installed.

Is there a way to import all my existing history from `.zsh_history`? It's a real pain to have to start from scratch.

I’m trying to compare this to mcfly, which does that, and also uses a sqlite db

https://github.com/cantino/mcfly

apparently it’s `atuin import`

I've skimmed up and down and read some sections a few times - I'm still not 100% sure what the main conclusions are. A summary section would make the article more accessible and valuable to others.

My understanding is that the main point here is:

- some problems require reasoning through many steps of computation, - transformers have limited depth, so cannot solve problems that require many steps.

Am I missing anything else?

My personal note taking system is based on Markdown, Vim, grep and Git.

I have a private repo for personal notes, including a `todo.md` file that I use as an GTD style inbox - I have an alias `todo='$EDITOR $HOME/personal/todo.md'` which takes me there quickly.

For some topics I use other repos - for example for programming notes, I use https://github.com/ADGEfficiency/programming-resources.

Works great, fast, cheap and I don't have to put up with any of the nonsense I used to put up with when I use Evernote.