You can’t generalize population density across the entire continent like that. Montana and Wyoming have a wildly different population density than California or New Jersey and they’re all in the contiguous United States. Even just looking at the region east of the Mississippi to between the Mississippi and the Rockies, shows a striking difference in population density.

Also, Spain is like 1/16 the size of the US with mostly a singular population center in the literal center of the country. And, the Paris metropolitan area is comparable to the tri-state NY Metro area and a fraction of the size of the surrounding region from NY to D.C., which itself is a tiny fraction of the area we call the East Coast.

They don’t even know cron exists and you’re going to throw them to the wolves by suggesting Systemd? That’s like calling in a drone strike to swat a mosquito.

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.

deleted by creator

Very Lovecraftian vibes. Reminds me of the Great Race of Yith.

From “The Shadow Out of Time”: “The Great Race’s members were immense rugose cones ten feet high, and with head and other organs attached to foot-thick, distensible limbs spreading from the apexes. They spoke by the clicking or scraping of huge paws or claws attached to the end of two of their four limbs, and walked by the expansion and contraction of a viscous layer attached to their vast, ten-foot bases.”

Not all the colors of crayons are available in the RGB space. Some colors will always look different when captured for a digital photo.

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.

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.

The real hack is (almost) always social.

I was just saying that your own description of events made you sound like a troll. I don’t know the truth of the matter and frankly it’s irrelevant. If they are working closely with Apple, those kinds of comments on what I assume was their own public forum are an unhelpful distraction at best and potentially detrimental to their corporate relationship with Apple. You could be %100 correct about Apple and the devs could %100 agree with your sentiment, but that doesn’t mean that the social media forum they host is an appropriate place for that kind of discussion. It’s not helpful for them and only has the potential to make their situation worse. They blocked you and moved on so they could focus on the project instead of the noise. Even if your intentions were good (and I do actually believe you meant well) I understand why they did what they did.

This sounds like you were harassing a volunteer dev that had an actual direct interaction with a corporation based on hearsay and they rightfully blocked a troll that wasn’t contributing anything meaningful or constructive to the project.

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

More like by design for an LTS release.

Poetry@lemmy.world

There is a poetry community that is kind of active on Lemmy.world. They also like to post poems as images (to preserve formatting and line breaks I suppose). I’m curious to see their reaction to a post like this. It would certainly stand out.

I’d like to see ideas like this make a comeback, hopefully with some modifications this time around to protect our privacy and resist corporate exploitation.

We used to use del.icio.us and other variants to do exactly this before browsers had profiles. Back then, its primary draw was that you could take your bookmarks with you anywhere to any machine (this being before that function was baked into browsers and before web browsers could be carried in your pocket). The secondary effect was that you’d share and tag those websites with your own categories/descriptors, thus crowdsourcing a new version of the old web’s link directories using Web 2.0. You could browse through symantic tag clouds to discover new things. Del.icio.us was for websites, but people were tagging and logging all of their favorite stuff and sharing it online so that like minded strangers could filled the gaps in their cultural awareness. We tagged our books with librarything. We tagged recipes with recipe thing. Audioscrobbler (later known as last.fm) logged our music listening to automate the tagging, not by direct symantic tagging, but by relational/temporal coincidence. If other people that listened to a lot of the stuff you listened to and they also listened to some other stuff you didn’t, those became recommendations for you. That kind of relational algorithm would survive the slow death of Web2.0 to become the backbone of recommendation services like Spotify and probably even TikTok.

Ever really destroyed your server because the it needed were available? I have. It was so much worse than a boot process that froze.

If Systemd was pausing due to a network share being down, it’s only because I (or you) told it to do exactly that. There are lots of good reasons to delay the boot process until all drives the system expects to be there are actually there or the network is up. Cleaning up the mess that happens when the system does not check these kinds of things at boot is so much worse. It’s never really some nebulous thing. Like it or not, intentional or not, the machine is doing exactly what you asked it to do and a delayed boot or a boot halted until you can solve the real problem is almost always better (or at least safer) than the alternatives. I’ve experienced all the things you’ve mentioned, dealt with each of those issues, and it was so much more of a hassle to diagnose before Systemd.