Keep in mind this isn't federation. It is a way to access multiple independent servers via reverse proxy.

Yep, this was mentioned in that thread and it is so impressive it deserves a dedicated topic to promote itself. Seems it has only existed for a few hours!

Question is totally on purpose, so that you'll fill in what it means to you. The intention is to get responses from people who are not using containers, that is all. Thank you for responding!

Minio has worked well for many years. Haven't had any problems with it until now, but ready to migrate away.

Oh wow, repo is https://github.com/LLukas22/Jellyswarrm Jellyswarrm is a reverse proxy that lets you combine multiple Jellyfin servers into one place. If you’ve got libraries spread across different locations or just want everything together, Jellyswarrm makes it easy to access all your media from a single interface.

Working

• Unified Library Access – Browse media from multiple Jellyfin servers in one place.
• Direct Playback – Play content straight from the original server without extra overhead.
• User Mapping – Link accounts across servers for a consistent user experience.
• API Compatibility – Appears as a normal Jellyfin server, so existing apps and tools still work.

⚠️ In Progress

• Websocket Support – Needed for real-time features like SyncPlay (not fully reliable yet).
• Audio Streaming – May not function correctly (still untested in many cases).
• Automatic Bitrate Adjustment – Stream quality based on network conditions isn’t supported yet.

🚫 Not Planned

• Admin Functions – Server administration (user management, settings, etc.) won’t be supported through Jellyswarrm.----

Apparently someone else released a Federation plugin 11 months ago. And looking at the feature request on Jellyfin end

User of 5 minutes sees:

User from an hour ago sees:

Haha, that is why it is with friends and family for people who want that. Definitely not for everyone. Cheers.

Sure, but I wanted to ask fellow Linux users

Haha, this book keep popping back up.

Oh, just wait. More about this to discuss in next episodes. Ahahahahaha :)

Will do

Do you mean within Lemmy? You click the save button (looks like a Star to me) in the menu directly below that post afaik.

Good to know. I've actually been using the tools I discuss on the show, as opposed to only naming off whatever is the newest thing without having actually used it. Good to know if that isn't clear.

Linux Prepper is related to doing everything myself with fully open tooling as much as possible. I've never seen another show do the same, so I thought it would be fun to try. Self-hosting everything, and using foss tooling for everything all the time, might not be practical, but it is a fun challenge. That is the intention.

One sentence answer: "Object storage manages data as discrete units called objects with unique identifiers and metadata, while file storage organizes data in a hierarchical structure of files and folders."

fwiw, I see object storage used as a way to manage data regardless of the file system. It is designed to scale, as opposed to the file system, in large cloud environments.

Here is a recap from Google Cloud:

Object storage, also known as object-based storage, is a computer data storage architecture designed to handle large amounts of unstructured data. Unlike other architectures, it designates data as distinct units, bundled with metadata and a unique identifier that can be used to locate and access each data unit.

These units—or objects—can be stored on-premises, but are typically stored in the cloud, making them easily accessible from anywhere. Due to object storage’s scale-out capabilities, there are few limits to its scalability, and it’s less costly to store large data volumes than other options, such as block storage.

Much of today’s data is unstructured: email, media and audio files, web pages, sensor data, and other types of digital content that do not fit easily into traditional databases. As a result, finding efficient and affordable ways to store and manage it has become problematic. Increasingly, object storage has become the preferred method for storing static content, data arches, and backups.

Jellyfin plays the media. It doesn't make/produce/edit or upload the media. Think of it as DIY Netflix service

Are you concerned about your self-hosted bare metal machine being a single point of failure? Or, are you concerned it will be difficult to reproduce?

Would you please talk more about it. I forgot about Open-webui, but intending to start playing with. Honestly, what do you actually do with it?

Did you try compose scripts as opposed to docker run

Post inception. That post was linked from this thread, hahaha.