Object storage is indeed a specialized filesystem in a trenchcoat.

Object storage is typically (but not always) associated with non-hierarchical key-value lookups, as opposed to the directory tree pattern most file systems use. Object storage systems are also typically (but not always) designed with sharding and distribution in mind.

This is a Jellyfin problem; not a beets problem. You can easily solve it with beets config if you’d like to, though.

The distinction between what you want vs. what you’re getting is that Jellyfin is grouping by the “Artist” tag instead of the “Album Artist” tag. I haven’t touched Jellyfin in years, but look for a builtin setting or alternative view to group by album artist - you’ll almost certainly find it.

If you want to solve it in beets, you can do that through a custom script, the FtInTitle plugin, or a combo of the inline + advancedrewrite plugins. Remember to run a re-import on the Jellyfin side after making your tweaks to the beets pipeline to make your changes show up without duplication.

I was hoping to play around with the dataset over the weekend to toy with some text-embedding techniques, but they’ve pulled the cord on the download links.

Anyone have a copy of the full archive they’re willing to share, or a magnet link?

That makes total sense. Tyvm for the transparency <3.

@admiralpatrick@lemmy.world The spam ban on the OP of this post seems heavyhanded (at least from the outside). Can you review or offer additional context?

E: this seems to (maybe) be the reason for anyone else wondering https://lemmy.world/post/29949200/17158534

This is brilliant! You can even let the front truck pull all the others tied behind it so you need fewer working engines.

What if you added guide rails to the lane so the trucks didn’t have to steer?

There is a massive functional difference to anyone with two braincells to rub together.

The core devs can (and should) step in front of a bus (or tank) tomorrow; the core project will just fork, and LW and the other non-triad instances will do fine without them. I’ve had no issue on Lemmy blocking .ml client-side.

The only reminder of the triad’s existence is infiltrator trolls who make alts on other instances to post bad-faith arguments glazing the core devs.

You misunderstood the pinned post; it’s soliciting donations for core Lemmy development, not for the .world instance.

The core devs use donations to the project to fund their tankie .ml instance, which is why they’re getting pushback. There is zero comparable pushback among the community towards funding .world or other instances.

If you’d like to give away any free toasters with hackable embedded microcontrollers to prove your point here, I’m a willing recipient and will attempt setup of a searx instance.

You didn’t start by asking a question. You needlessly trashed a helpful suggestion from a place of ignorance, then asked a naive question defensively to mask a lack of knowledge.

That is rude and trollish behavior.

Since it seems like you don’t know much about bash at all, I promise the book will help you.

You can be someone who actually knows what they’re talking about instead of making embarrassing, snarky comments that expose your lack of education on the topic at hand.

Bash has had some nice minor features and syntax sugar added, but the fundamentals are entirely the same. All the examples in the book work just the same today as they did when it was written.

What was added in 4.X or 5.x that you can’t live without? What do you think has changed that merits inclusion?

It’s a 36 y/o language, mate. I still reference my copy all the time, and found it to be a great definitive resource when I was learning.

How many bash 4/5 features are you seriously using on a regular basis? What do you think is out-of-date?

I highly recommend O’Reilly’s Learning the Bash Shell in paperback form: https://www.oreilly.com/library/view/learning-the-bash/0596009658/.

The other responses you’ve received so far don’t offer much insight into the historical background and underlying mechanics of the shell, which are crucial to understanding the "Why?"s of command-line quirkiness.

Synology runs a proprietary OS OOTB that’s had multiple sloppy vulns exposing full remote access to users’ files. Putting your data in the hands of fuckups who have and will continue to leak it is the opposite of total control.

It’s completely trivial to store any data you want to in a cloud provider 100% securely just by piping it through openssl before uploading.