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.

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 an argument to be made, but I don’t believe that is true at all. Sending one car to check on the safety/welfare of one active threat seems an entirely reasonable balance of risk. An unverified active threat is not at all the same as a confirmed active threat. That should be obvious simply by the existence of “swatting” as a common term and act these days.

It is not the duty of police to protect people from eminent harm, they have argued this themselves in court. Their job is strictly punitive, again an argument they have made in court many times. They only pretend to “protect and serve” when it suits their agenda of justification for their over inflated budgets. This isn’t a public safety issue. It’s a class warfare issue.

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.

I disagree on ever single point you’ve said here.

Sounds like a skill issue. Good translation is hard and is rarely a literal one to one mapping of syntax and diction. It’s an interpretive art.

Sounds like a skill issue. Bad translations are bad because they don’t find good ways to translate these kinds of things. As you say, translation isn’t just about the words, it’s about cultural context. But, bad translations aren’t inevitable just because good translations are difficult.

You’ve just traded down votes for the report button.

I say they are two different use cases. There is often a very wide gulf between a comment that I feel does not contribute to good discussion and one that is so heinous that it needs to be removed. Most of your comments for instance: pretty naive and banal adding little good to the discussion overall, but I don’t feel that you’ve said anything hateful, obscene, or aggressive enough to warrant total removal. Usually I just downvote and move on, especially when I don’t want to hear that person’s bad take reply on my own point of view. I’ve made an exception here for you simply because you are trolling all over this thread, seemingly inviting downvotes. But, I’m going to block you and move on because you’ve killed any interest I have in this thread or the larger discussion. I still don’t think your comments rise to the level of reporting.

Reports and blocks aren’t a replacement for downvotes and if your instances doesn’t federate downvotes you shouldn’t use them that way.

Yes. I’m assuming your just some dude and not a telecom with teams of lawyers.

COVID bump

This needs to be copypasta’d as a reply to every comment suggesting that opening up jellyfin to the internet is easy and everyone should do it to get away from Plex.

Self-hosting is inherently not low effort. This isn’t memes or shitposts. This is people helping people that are trying to help themselves, a.k.a. people making an effort. Communities rely on the discretion of mods and rules specific to the community focus. If this community didn’t have some kind of bar to meet for low effort posts it would drive away participants and contributors more interested in higher effort and more interesting topics. It gets real old seeing people ask and answer the same basic questions about Plex, Jellyfin, *arrs, and docker all the time. Worrying about if this rule will be abused seems premature. Besides (as others have pointed out) there are other communities with similar interests, if you’re that concerned that your spammy no-context YouTube video got deleted, please go try your luck elsewhere.

AI engagement bots like OP.

You want mpd to server and play the music, connected with a web front end (there are a few to choose from) accessible on the private store wifi. You should probably serve this frontend only to a certain machine on the network (like the managers computer in the back) and lock everything else out. The last time I ripped CDs on Linux I used whipper, which I believe was the successor to morituri. This is all only legal if the CDs they have already included the licensing fees to play them publicly or are themselves freely licensed. There are sources of freely licensed music out there that you can play publicly without paying.

That’s not very helpful for connecting family, friends, and especially grandma.

Jellyfish cannot to setup to securely and safely be exposed to the Internet. It is only safe to access through a VPN. That rules it out as an option for sharing with friends, family, or even my own spouse. You call it phoning home to the mother ship; I call it paying Plex to manage user authentication for me. Until Jellyfin’s security holes are patched and it becomes clear that the Jellyfin developers actually care about security, it stays locked down to my LAN. Setting up a VPN is difficult for the average user on a good day, impossible in some circumstances on even the best of days, and is not access I want to hand out (and support) to all the people I share my Plex with anyway.