|
2013-03-01 07:04:04 GMT
|
I came on to grab a show tonight for the first time in a few days, and with some time away then coming back, it seems that the site still doesn't work as well as it should.
- A 91 minute old release in a.b.teevee still hasn't shown up on the indexer. This mean that clearly the new 5 minute parsing engine (https://nzbx.co/forum/topic/id/169) really isn't working. Maybe it will show up by tomorrow morning, but for me at least, this means nzbx isn't useful for SickBeard. Every other indexer, including the free SickBeard Index and Womble's Index have the release already. Of course binsearch and nzbclub et. al and such 'have' the release as well, but they don't count for SickBeard.
- NFOs still don't work. This is completely 100% broken (except on old releases). I don't buy that it's Newznab's fault, considering all other Newznab indexers I have access to are parsing NFOs just fine.
- Why are releases showing as incomplete? I understand it's been said in the past that this is due to the USP, but again I don't buy it. No other indexer has anything approaching the broken completion on here. At this point, the site may as well not have a completion meter. This is completely 100% broken. Related to the new Python parsing engine which isn't smart enough to detect that a release has changed? i.e. it scans when the release is 78% uploaded then never updates to 100%
These are all software problems and a switched to owned hardware shouldn't fix any of them. Is there any plan to continue development on the site to fix these outstanding issues?
|
|
2013-03-01 11:35:22 GMT
|
- A 91 minute old release in a.b.teevee still hasn't shown up on the indexer. This mean that clearly the new 5 minute parsing engine (https://nzbx.co/forum/topic/id/169) really isn't working. Maybe it will show up by tomorrow morning, but for me at least, this means nzbx isn't useful for SickBeard. Every other indexer, including the free SickBeard Index and Womble's Index have the release already. Of course binsearch and nzbclub et. al and such 'have' the release as well, but they don't count for SickBeard.
Without more information on what release you are referring to, there is not much I can do in regards to this.
- NFOs still don't work. This is completely 100% broken (except on old releases). I don't buy that it's Newznab's fault, considering all other Newznab indexers I have access to are parsing NFOs just fine.
You can refuse to buy it all you want, sadly - it's a fact. NFO processing is now at the top of the priority roadmap. We have not processed NFO's on all but 2,135 releases, so I would hardly count this as 100% broken.
- Why are releases showing as incomplete? I understand it's been said in the past that this is due to the USP, but again I don't buy it. No other indexer has anything approaching the broken completion on here. At this point, the site may as well not have a completion meter. This is completely 100% broken. Related to the new Python parsing engine which isn't smart enough to detect that a release has changed? i.e. it scans when the release is 78% uploaded then never updates to 100%
The completion is in direct relation to whether articles have been removed from the USP. In case you are interested, the Newznab shadow install is showing the exact same completion rates.
At the end of the day, if you prefer the Newznab platform - you might be better suited going and using a Newznab indexer and leaving this one behind you. |
|
2013-03-01 11:47:00 GMT
|
Following on from the above, I've now removed the Newznab NFO processor and replaced it. This was pretty much the last of the remaining components.
|
|
2013-03-01 17:09:38 GMT
|
It's unfortunate, I really like the site and believe it has serious promise. The only reason I care enough to post is because I want it to succeed. That said, you're probably right. I'm probably better off with Newznab/binsearch/for the moment.
The release is this:
https://nzbx.co/d?e6c599dcc158ba3947ea73e822dbf7c8
I'm sure you have data on when it was actually added to the index, since it wasn't there when I posted.
I just checked the completion on a variety of Newznab indexers:
http://imgur.com/a/ZaaD5
I'm sure you're not lying, I'm sure your Newznab shadow install (good idea, I didn't know you had that!) is reporting < 100% completion. That said, it is _wrong_. It's broken! I couldn't even guess as to why the completion is incorrect on your end, but the issue is on YOUR END. Every other indexer (and non indexer, binsearch [https://www.binsearch.info/?server=2&b=big.brother.canada.s01e02.dsr.x264-2hd&g=alt.binaries.teevee&p=prime%40time.tv+%28autobot%29&max=250]) reports the correct completion as does NZBClub [http://www.nzbclub.com/nzb_view/27870165/129131_FULL_a_b_teevee_Big_Brother_Canada_S01E02_DSR_x264_2HD].
mega.nzbx.co would have been more effective than nzbx proper last night (which I guess is implied, since it searches nzbx so it will always be >= nzbx).
For what it's worth, I don't prefer the Newznab 'platform'. I prefer this open idea where comments and such are viewable without an account. I think it encourages participation and a more accountable usenet. I also like your sharing is caring mentality with VIP for all.
On the other hand, I do think basic copy-pasted cookie-cutter Newznab installs with no personality... I think they WORK better. If all I want to do is get from wanting a file to having that file on my local disk, it appears that a Newznab install is the better option. But it's not the whole picture, which is why I'd love it if I could have my cake and eat it too. A reliable and functional usenet indexer (in the manner of Newznab) with the community spirit of nzbX.
|
|
2013-03-01 22:14:53 GMT
|
It was added to the index at 0517, but for some reason it wasn't added to the search cache. I will look in to this is a matter of urgency.
In regards to completion, we're now using a rotating circle of USP's and choosing the one with the highest completion - if you check the browse page, this should be more apparent.
|
|
2013-03-02 17:55:06 GMT
|
Thanks Lemon. Completion and NFOs look to be back up and running :)
|
