(2013-03-13, 16:47)olympia Wrote: 1. This is a general policy. We do not support p0rn. Period. This is not up to discussion.
Point taken.
(2013-03-13, 16:47)olympia Wrote: 2. In addition to the above mentioned policy, because you don't see how a configurable option can cause problem: just imagine the situation when your children will be facing with offending content while this configurable option is enabled due to failed/wrong scraping e.g. if the title of a p0rn movie on TMDb was closer to the file/folder than the disney cartoon they wanted to scrape.
Making my next point may be moot, given how curtly you've responded to my request just for info on how the decision to disallow adult titles came about. However, I feel the point should be made nonetheless -- even if change isn't likely to occur.
Contrary to what you think, I /do/ see how adult content scraping could be a problem for some people. /But,/ the option I'm proposing wouldn't change the current situation at all for those people.
The option would be to /not/ include adult content by default. Don't want adult titles? Don't turn it on. Don't want it turned on? Use the xbmc parental controls to lock down the config. I think most parents who care /that much/ are used to parental controls.
The /current/ TMDB situation (/without/ my proposed change), already has the "risk" to incorrectly scrape the wrong title -- and an adult title specifically. How? A title could be added to TMDB, and simply just isn't labeled as adult. Suddenly, Little Timmy can accidentally get info for an adult title in XBMC. Or, even "worse," Little Timmy could want to scrape a movie with the word "pirates" in it. "Pirates" was the name of a recent, popular adult title which was popular enough to spawn a Rated R recut of it. Sure enough, "Pirates" the R-Rated version is currently scraped properly by XBMC. The cover and plot are same as the NC-17. This current vector for adult content doesn't seem to bother the XBMC project. Why is this risk ok but a configurable option (with parental control to lock down configs) is considered too "risky?"
It just all seems very arbitrary to me.
(2013-03-13, 16:47)olympia Wrote: 3. Hint: the default TMDB scraper doesn't get updated so often that this should block you to modify it every time or just create a fork which then will not be updated
I'll keep this in mind; I may choose this option.
(2013-03-13, 16:47)olympia Wrote: 4. Put your adult oriented movies into a separate folder and set your adult scraper on it.
Thanks for the suggestion. I do prefer to keep all of my movies in one folder, but I can get over that. Also, I do like TMDB as a service and they are my movie DB of choice, which is why I've been so insistent on making sure that the XBMC project really is this set against adult titles. You've cleared that up nicely by being so unwilling to explain XBMC's position. It takes a strong viewpoint to not even want to discuss a topic.
Despite some of our sparring, I do appreciate you taking the time to respond. It is nice to get some feedback from someone "in the know" in the XBMC group.
---Alex