• 0 Posts
  • 62 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2024

help-circle

  • In thousands of songs, I’ve never noticed Picard doing anything to the length of the files. I tend to manually review every album by running it through Picard and letting it handle the renaming and tagging. That structure used to be Artist/Year Album/Song. I’ve been less strict about naming the songs themselves. It’s always at least track - Title, but sometimes Artist - Album - Disc # - is prepended. Eventually I ran into a situation where I had multiple versions of a release/album with different enough content to warrant keeping both, so now I throw a release ID number (if is exists) after the album name, and inside brackets, for the directory name.

    It’s a very flat structure by design, so I’m never quibbling about where I sourced something or what particular genre it is when I’m looking for it. That dramatically reduces the likelihood of duplicates too. Real metadata is better left to tags, since that’s mostly what any player will see anyway.

    If I’m having trouble getting Picard to recognize something it always because: musicbrainz.org is missing the release, doesn’t have acoustic ID, or Picard preferred the album track when I’m trying to rename and tag a single or EP. Adding the release info and acoustic ID to musicbrainz is easy and I can usually use the info before the release is even reviewed, but often in trying to add the release I’ll find the correct one and now I can help fill out the data about it.

    I treat musicbrainz.org as MY metadata database. If a release is missing or has problems, I do the work to make it better. It’s good digital citizenship and learning about their rules for releases helps me manage my server better.










  • I’m not the person you asked, but I do have answers.

    I have a French press, so I often use that. The preparation is exactly the same as a hot press except for the time and temperature; same grind, same proportions of water to coffee. Just mix the coffee and cool water and wait to plunge for several hours. It would usually be something I’d prepare the night before, leave on the counter, then plunge and pour in the morning.

    You can do the same thing with larger volumes/masses of coffee and water using a mesh bag and a pitcher. Same process just more. Also avoid squeezing the bag too much, but do let the coffee run out as you remove the bag containing the coffee from the pitcher.





  • That’s not what the articles says or implies at all. The article only refers to another article with a click bait headline. The article article summarizes Canonical stance like this:

    • Canonical will add AI to Ubuntu — but only cautiously and when it truly makes sense.
    • AI features must be mature, open-source, and run locally when possible.
    • Focus AI on accessibility (speech-to-text, TTS) and improvements, not turning Ubuntu into an ‘AI product’.

    And to be clear, including a tool or default workflow is MILES away from patronizingly forcing it on to users. It’s just the way that most distros that aren’t Linux From Scratch work.


  • The idea is to have the server safely shutdown BEFORE it loses power, so that BIOS setting wouldn’t mean anything. The server does not loose power while it it running, so it will never “restore last state after AC loss”. The idea is that you can run a low power device (the raspberry pi) for which you don’t care if power is cut abruptly and that can talk to both the UPS and the wake-on-lan of the server directly over ethernet. It being local means those WOL are much more likely to work than trying to send them from outside your network when you’re remote. It’s a lot simpler to set this up once than it is to recover a server with a corrupted file system due to power loss or lose access to your server for weeks because a thunderstorm knocked out power for 30min at the beginning of a long trip. That pi can also take care of other always on services like a pi-hole, home assistant, etc.