2023-09-30, 01:43 AM
(This post was last modified: 2023-09-30, 01:44 AM by skribe. Edited 2 times in total.)
(2023-09-30, 12:20 AM)bitmap Wrote: Not even meant to be thinly-veiled, honestly. Sending folks to an outside resource that's not this community to keep discussion of those tools away. I did edit both posts to remove mention of that site, however, to better align with the standard you outlined. Still figuring it out.
Yes, those other tools exist and so do communities for them, however "Go away" seems like a poor message to send to folks who integrate Jellyfin into their ecosystem and happen to use those other tools. Particularly when some users have the knowledge to at least point somebody in the right direction. Certainly not arguing a point at all, I wanted to ask and figure out where the "line in the sand" was and this is the first opportunity I've had reason to ask.
Sorry to hijack the topic, good luck!
No, listen, you're fine. We can talk about it. I went ahead and split this into its own thread.
I think your framing is more negative than it needs to be. If this helps: it's not about telling people to go away, it's really about the fact that we're here to support Jellyfin, and these tools have their own support ecosystems. If someone seems to have issues with their media naming and organization, tell them, by all means, that sonarr is a great tool that can sort and name their media in accordance with Jellyfin's conventions, and link them to Sonarr's website if you want. But we're not here to support Sonarr. Information about how to configure sonarr to get media, or the permissions, or anything else, is better handled within their own support ecosystem. If someone has a jellyfin specific question about it like "how can I make sure that jellyfin updates the library when sonarr changes a filename?" that's fine. By all means, give them details about that. But the "right direction" to go, in general, is to point them is to the sonarr project site, where sonarr can provide them with documentation and support for the project that they understand much better than we do. And if you have a solid understanding of those tools, you can participate in their communities too.
The rules in this area have been greatly relaxed since this forum was created, btw. The old rules didn't permit discussion about them at all. Now the discussion is fine, but it needs to be limited specifically to jellyfin and not general configuration and usage. But you're free to recommend these tools as specifically relevant to jellyfin and its use. Just helpfully link users to their support communities for help with setting up all of their features, rather than doing it here. Honestly, we would want users to come here for Jellyfin support rather than seeking it in their spaces too. We're better equipped to help them.
Does that help with parsing things?