

Where’s the coconut water going to be this time? With the water? With the juice? With the fake juice and sports drinks? With the soda? With the international foods? No, none of these sections are adjacent to one another.


Where’s the coconut water going to be this time? With the water? With the juice? With the fake juice and sports drinks? With the soda? With the international foods? No, none of these sections are adjacent to one another.


His family name was actually Drumpf. His immigrant grandfather Americanized it on or shortly after arriving in America.


Fun fact, North Dakota (home of the idiot cop and criminally evil prosecutor) has a fewer people than the city of San Francisco in about 150,000 times the acreage. Put another way, there are about 268,000 people per electoral vote in North Dakota compared with about 728,000 people per electoral vote in California and about 670,000 people per electoral vote in Tennessee (home of the grandmother).


Hey now. Hillbillies are a proud Appalachian cultural tradition. The grandmother, being from Tennessee, might have been a hillbilly. And it might not have been an insult for her to self apply that label. The idiot cop and asshole prosecutor were in North Dakota.


deleted by creator


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:
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.


According to the article it was royalty free and published open standards, but they do not make any claim to this being an FOSS system.


Could they not think of an original name? Calling it YouTube-dl is just unnecessarily lazy and confusing. This appears to be mostly a docker image of yt-dlp, which is itself a fork of youtube-dl.
So much safer to go one album at a time using Picard. Picard makes it easy to go down the list of a disorganized directory, identify most things automatically, allow in depth review and modifications to what Picard came up with, and standardize file naming. I’ve tried to let programs like Lidarr and beets automate it, but they always ends up causing more and more complex problems to discover and solve after awhile. Music releases are complex and sources are diverse, using distinct standards of form and format. It’s not a problem that can realistically be solved for my entire music library without the guiding hand of a librarian. I could listen to my library for over six months without repeating, even 1 album out of a 100 mis-tagged or misidentifyied could take me years to discover.
I do like to automate the less critical and more machine oriented library tasks like adding genres tags, replaygain, and lyrics as you do. Just not things like the metadata tags, file naming, or album art (embedded or otherwise).
Wow, if the demo was too much for the developers to maintain that doesn’t inspire confidence in my patience to maintain it on my machine.


Not OP, but I have similar feelings and they have nothing to do with the client or plugins. If I can’t easily and securely share my Jellyfin with the Internet beyond my LAN without resorting to a VPN, then Jellyfish is not going to come close to replacing Plex. Sharing my library securely with tech illiterate family and any browser I have access to, without modification, was the one and only reason I moved away from XBMC/Kodi and installed Plex in the first place. Jellyfin is fine inside my LAN and for my personal use, totally fails at hosting.


deleted by creator
That’s my point. Your judgemental “speaking your truth” is antithetical to the entire point of the post. To be sure, it is a paradox of tolerance, but that’s no excuse.
Given how hung up you are with what other people enjoy (it’s sooo gracious of you to not complain to them directly) and your judgement of the “quality” of that enjoyment, maybe you should try a little more of that introspection you seem to admire. As long as they’re not hurting anyone else, their hobbies are theirs. Not everybody needs to be a philosopher for their hobbies to have meaning to them. This post isn’t about YOU approving or accepting of other people’s weird hobbies. It’s about admiring people because of their enthusiasm, regardless of you or anyone else thinks. Focusing on your own judgmental attitudes about those hobbies totally and completely misses the point.
Complimenting people can feel like a shameful act. But, I’ve tried to learn to not be ashamed about being genuinely complimentary as long as I’m not being a creep or intrusive about it.
I like to just drop the genuinely positive truth bombs and walk away like a geriatric crop dusting the early bird special. They (the target of said compliment) should not feel obligated to acknowledge reciprocate in any way. This suddenly feels shamefully long winded. Be cool to each other.
FTFY: I have pan in both my legs.
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.