Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54698 readers

379 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

[email protected]

125

Why so many *arr services? Why not 1 service that works with all media types? (lemmy.dbzer0.com)

submitted 1 year ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

I am almost done building my first self hosted streambox through Docker. That's a total of 16 instances, each fulfilling 1 specific role.

As I'm new to the *arr world, could you please help me understand why it is standard to deploy multiple *arr services for each media type (ex: readarr1 for books + readarr2 for audiobooks) instead of using 1 that does multiple media types?

Thank you.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago)

Yes, I understand that you can just add more services to integrate your other services together. I just think that it would be far more convenient to have a single service that does all of that in a smart way. Each service could instead be its own plugin that you could opt into. Each plugin would have its own dedicated UI/UX for handling that media type.

Basically it should have a design similar to that of Plex or Jellyfin (which handle multiple media types in a smart, cohesive way). Of course, that would take a lot of coordination and funding, but man it would be such a better overall experience for the vast majority of people.