Cold Case Season 17 COMPLETE HDTV XviD
Annegret Mclean
I added this torrent as a favorite and utorrent set the filter to "Scrubs VTV" and began downloading? Where is the big difference? It should work also without the additional keyword for the release group.
Another example: There is a show with torrents like "Being.Erica.....". I tried to manually add a filter with filter set to "Erica". No matches. It has to be added with the filter set to "Being Erica" otherwise it won't match. This makes no sense.
Another example. RSS entry "Private.Practice. ... .[VTV]". After some testing i found out, that the filter has to be exactly set to "Private Practice VTV" like utorrent enters it automatically, otherwise nothing will be downloaded.
The normal user would expect that the Downloader would catch any RSS feed depending on the filter string. But is nowhere clear, that the full name of the show has to be entered or that even the release group has to mentioned.
Wildcards. For Scrubs try using "Scrubs*" as a filter. That way text after Scrubs won't matter. Helps out if someone gives the episode name too. For Private Practice, same thing, stick a * at the end, so "Private Practice*". Or for even better matching, "Private?Practice*". The ? in this case will match a space or a . or anything else they stick in there. For more complicated ones, like your Being Erica example, put a star on both ends. So "*Erica*". That should catch all those pesky additions like HDTV/VTV/DIVX/Episode Title.
The release group does NOT need to be mentioned, you just need to put a wildcard in. If you want a specific release group, you simply add that back in using whatever naming convention that group uses.
Had you read the RSS guide linked from the uTorrent website, you would have seen all that I've just explained. Or had you even punched in "uTorrent RSS tutorial" or even "uTorrent RSS help" into Google. Which means RSS implementation isn't "broken", you just failed to read the documentation, made a poor assumption, and then failed to attempt to find the solution to your problem before calling something "broken".
Now the hinky part when you click the "?" as listed you get 1 return the h264 torrent but if you check the "Filter matches original name instead of decoded name" you get both the Xvid and h264 versions.
Hmmm. I added the RSS feed to my uTorrent and set up your same filter, same thing happens to me. If you want even more fun, take out the Eclipse part altogether, and just use "To Aru Majutsu no Index" as a filter and hit ?, then you just get the XVid one. haha So it seems like on the Xvid version, uTorrent doesn't see the [Eclipse] part in the reformatted name, but picks it up fine in the original name.
Filtering should be easy for the user and it is not. Imagine a file search in windows where you search for "day" in the filename and it wouldn't find "best.day.jpg". Or that you have to use wildcards all the time when you search through your emails.
The problem is that there are the names of the feed items on the one hand and there is the filter on the other hand. The normal user would think that he can edit the filters and then gets matches from the list of item names. But this won't work.
The problem is that utorrent has its own internal scheme how to handle the names. And you have to adjust the filter to this internal scheme which you can't see. You can only see the name which is put together by utorrent. And the filter doesn't work on the displayed name, but on the internal representation. Then everything makes sense.
So, if the name of the show consists of several words, you always have to use space. Even if there is a dot between the words, dots in the filter won't work. And then you have to add all he crap that comes after the codec, no matter what kind of parentheses are used. Or also, if there are no parentheses at all. Just add all the crap separated by dots or spaces or it won't download. You even have to add that "torrent" to the filter, just "Being Erica eztv" won't match anything.
Oh, and the documentation is bad. There is one point about the wildcards and no explanation, that you also have to use it in the cases described above. Of course, you can always say "RTFM" and blame the user. But IMHO it is better to have a good filtering mechanism which can be used easily.
You want Scrubs to catch everything with the name Scrubs in it somewhere. That's great. But maybe someone doesn't. Maybe they want only a torrent with the name Scrubs in it and nothing else. Something their friend uploads maybe. By forcing you, who wants to match against everything, to put in wildcards, like * and ?, it enables them to get what they want and you to get what you want. I guess you don't use search engines much, the usually drop punctuation. I assume that's what happens here. So a search for Being.Erica is viewed as BeingErica. "Being Erica" also ignores the punctuation in matching I suspect which is why it works with Being.Erica, but "Being?Erica" guarantees that should any matching methods change, it will still work. Again, this is user error, not a "broken" system. Something being non-intuitive to you doesn't mean it's non-intuitive to everyone else. You just failed to RTFM. Take someone who's never seen a car and throw them into it. It's not intuitive. Or put them in a plane and ask them to fly. Or do math. Very few things are intuitive. They're intuitive because of our experience, they're "familiar". That's one of the basics of Software Engineer: make it look like something else so it's familiar. If you used search engines like Altavista back in the mid-80's, this would be VERY familiar to you. If you're a younger generation that's only ever used Google, you're used to searches being completely rewritten by Google to find what you meant instead of what you typed. Things are ONLY intuitive if you understand how they work. In this case, matching requires exact phrases. So you need wildcards. It's very intuitive once you accept that and RTFM.
Space is not a wildcard, but a wildcard will match to space. In your Being Erica example, the following will catch ALL of them, only 1 filter. "Being?Erica*". You won't need 3 separate filters. This will also filter out torrents like "Why I Hate Being Erica" (no wildcards before in the filter so it won't match to it), or "Being Someone Other Than Erica". You could catch all those as well with "*Being*Erica*". The downside is, you will also catch things like "Being Erica Really Sucks". But alas, it's attempted to filter everything unwanted instead of randomly matching to everything with the words "being" and "erica" in them.
The way YOU think it should work, makes it difficult in many situations to get what you want. Your suggestion would have everyone wanting "House" to get "Desparate Housewives", "This Old House", "Little House on the Prairie", "Full House", "Run's House", etc. Go to TV.com, punch "House" in the search, then look at the "Shows" tab. 755 results. Your logic would have uTorrent matching to at least 100 of those. So now instead of adding 1 wildcard and a few "not" filters, people wanting "House" need 99 not filters. 99 not filters because you don't want to have to enter a * somewhere?!?! That seems pretty selfish of you, don't you think?
I'm sorry it's not "convenient" or "intuitive" for you to use *'s and ?'s, but it happens to make things A LOT easier for pretty much everyone else and by forcing you to RTFM and learn how to use it, it will save you headaches in the future as well. The guide shouldn't have to say "You need to use wildcards to match everything" because that's what the term wildcard means. It's not going to define each word. There's also Google that turns up really great tutorials if it doesn't make sense. Had you attempted to find an answer before coming here to call things broken, you would've seen that. You use EZTV torrents from your Being Erica examples, their tutorial is VERY well written, lots of detail about wildcards. In addition, there's a bunch of posts in the forums that talk about RSS and wildcards.
"Being Erica" will match "Being Erica", "Being.Erica", "Being.Erica.HDTV.Xvid", Being.Erica.1x03" and so on. It knows about episode numbers and it knows about (most) compression methods. If you want it to match any release group with any possible naming convention (which not everyone will and that's why it doesn't work the way you want it to), you add wildcards. So you can stop saying "you have to add all he crap that comes after codec, no matter what kind of parantheses are used", because you DON'T! You just put a * after your filter!!! And you can stop you shouldn't have to, because as I've shown with my "house" example, that's a really terrible way to do it as it makes life VERY difficult for everyone else.
The way it is works best for everyone, not just you. So yes, I will continue to say RTFM and blame the user because I don't want to see myself needing to add hundreds of "not" filters to stop getting things I don't want. Some of us have a few dozen RSS feeds and dozens of RSS filters. Some of those would easily match to 15 or so results if your method is implemented. I don't think that to make your life easy, I need to add 15 NOT filters to 60+ RSS filters. That's 900 more words I need to add into "NOT" so you can get away with easily getting 1 show and not have to use wildcards? I don't think so. RTFM and figure it out.
And, sure, every search is unintuitive if you have never seen a computer. But assuming that a user can use Google, a file search or a word search, this filter is still not intuitive. It would be if it would behave like these other common filters.
You can set a filter to be greedy or not to be greedy. utorrent does the latter which is uncommon and does it in bad way by obscuring the way the names are stored internally. There are disadvantages for both options, so both should be included.
If you use "Scrubs*" instead of "Scrubs" as your filter, it won't matter. It will continue to work. If you use you're inane method of "Scrubs VTV" it certainly will. But why are you doing that when I've repeatedly told you that you should use "Scrubs*"?
b37509886e