Hey sorry, just another issue with the usenet indexing.
When you're uploading a collection of episodes, you've been using a title like this: --- [Tsundere] Kantai Collection [BDRip h264 1920x1080 10bit FLAC] [1/20] - "[Tsundere] Kantai Collection - 01 [BDRip h264 1920x1080 10bit FLAC][4AEFAE2A].mkv" yEnc (1/1900) 1458897068 --- Which, to be perfectly honest, makes a lot of sense.
The problem is, that idiots in other newsgroups (and in the anime groups a.b.anime and a.b.m.anime) tend to put advertisements before the part indicator at the start. A lot of shit gets posted, like this: [ TOWN ]-[ www.town.ag ]-[ ANIME ]-[Usenet Provider >> www.ssl-news.info <<] [02/17] - "[Pur...Innocen].Heavy.Object.-.04.[720p][8A2E0089].part01.rar" - 581,19 MB yEnc (1/137) Thankfully they didn't put their ad crap in the section enclosed by quotations, so it was easy enough to get a real title (in this case "[Pur...Innocen] Heavy Object - 04 [720p][8A2E0089]").
This means the vast majority of indexers completely ignore the section unenclosed by quotations at the start (except for the part indicator).
What this means is that your collections don't get indexed properly, even though its a smart way to format the title for collections. What ends up happening is each of the episodes you upload are seen as individual files, and don't get grouped together. Instead of being able to create one NZB for [Tsundere] Kantai Collection [BDRip h264 1920x1080 10bit FLAC], the indexers will create incomplete/unfinished NZBs for the individual episodes.
I think most posters tend to compress the collection, and split it into a number of .rar files. For example, the Kantai Collection might become: [Tsundere] Kantai Collection [BDRip h264 1920x1080 10bit FLAC] [1/20] - "[Tsundere] Kantai Collection [BDRip h264 1920x1080 10bit FLAC].001" yEnc (1/1900) [Tsundere] Kantai Collection [BDRip h264 1920x1080 10bit FLAC] [1/20] - "[Tsundere] Kantai Collection [BDRip h264 1920x1080 10bit FLAC].002" yEnc (1/1900)
My fucking soul is so broken, poor Update-kun would probably run away. I don't have any high level goldfish... need to steal some Koi somewhere. "Firstborn" *throws up* Disgusting. Stop that.
Yes, there's some hardware issues with the server and I've been waiting for the hosting provider to respond. Hopefully there won't be many interruptions from now on (I do expect some still).
Great addition with the usenet uploads. It's my #1 source of downloads, and stay alive for basically forever (2500+ days and counting). Great way to archive things.
Good point! I've implemented your suggestion, which will show up in future posts, thanks for that.
The NZBs served here will always have the complete collection. External indexers will need to rely on parsing subject lines, which should be fine most of the time, though I worry a bit about potential duplicate names. Perhaps I'll eventually put some sort of ID into the subject to avoid this.
For example: "[BakedFish] Sekkou Boys - 11 [720p][AAC].mp4" yEnc (1/150) 114529596
What I can assume from this, as far as I see it, is that I can expect exactly one file, comprised of 150 parts. When I know I have those parts, I should be able to group everything together, and create an NZB. I know exactly when the file is complete.
Instead, there is multiple parts that should be in each NZB: normally an .mkv with multiple .par2 files.
For the Sekkou Boys example there are 5 parts, but there doesn't seem to be a way to actually be certain of how many there are. I just know because I checked some other indexers that probably grouped them only by name.
I think you should include the parts, and total parts when you upload. Sekkou Boys should instead look something like this if you are including .par2 files. [1/5] - "[BakedFish] Sekkou Boys - 11 [720p][AAC].mp4" yEnc (1/150) 114529596 [2/5] - "[BakedFish] Sekkou Boys - 11 [720p][AAC].vol01+02.par2" yEnc (1/5) 3074088 etc...
It seems like most indexers are grabbing these fine, and are probably trying to group the .mkv and .par2 files by name. I can't index them on anizb though, and I don't think it is a good idea to try to.
I use usenetserver.com, which is perfectly fine for me. There is a special for it, for $10 a month on the front page of http://binsearch.info/. I also hear a lot of good things about http://frugalusenet.com/, which is $4.99 a month but only lets you download files that are less than 600 days old.
Just wanted to say thanks for starting usenet mirrors. Quality uploaders are few and far between now; it seems Ishouni has been the only reliable one for the last 2 or 3 years. ~anizb
The compression itself is fairly good, but there's no de-duplication. This is particularly bad on the batch 7z files since there's typically a lot of duplicate fonts, as you've pointed out.
You can try this out yourself when you do your test recompress - disable solid compression (set "Solid Block size" to "Non-solid") and you should get a similar size to what we serve.
Hey Animetosho, Just a small question with feedback :) "All Attachments", is the 7z compression method used by it, is different than normal? I saw All Attachments 7z file for a batch was 64mb sized, looks abnormal... I downloaded it and repacked it into 7z with normal method, then the size was less than 3mb... It is like 200%+ difference! Since text are always compressible and font files are redundant over episodes, it should be like this unless it followed a different method! (For video file, STORE is better I think!)
the entry you're referring to is 3 years old. you'll probably need to access Usenet to get the dual audio original Pretty Cure now. but dub sucks so why bother.
That being said, if you want an English dub of a recent Precure series, look for "Glitter force". I think AT has/had it.
Thanks. It does the job nicely. It passes the "scan" test in that I don't have to focus my eyes to locate these folders, and I can spot all the folders on a page instantly --This is very different from reading recognition, which by comparison is tiresome and slow.
Multi-file torrents don't necessarily contain 12 files; a torrent with 2 files is also a multi-file torrent. Formatting the size is an interesting concept though. Bold is somewhat un-aesthetically pleasing though... I'll think about it.
I would think one 12 file torrent is as important as 12 one file torrents, and the smaller text you mention is not usually a great way to highlight things. How about this: just the size letters in the right column, MB and GB, with GB in bold. That would highlight the larger torrents, including the single-file movies.
Thanks for those suggestions. Since you asked for my thoughts:
1. Multi-file torrents do have a "(... files)" text below them and don't have DDL links. Bold tends to signify importance of some sort, so I'm apprehensive on using that. I'm not against the idea of making them easier to distinguish though. Any other ideas? 2. I'll need to think about how possible this is - it may not exactly be a trivial thing to do. 3. Unfortunately the system doesn't quite work that way. There's no particular timing on when a retry will occur. Displaying a retry count may be possible though, so I'll consider that.
There previously was a homepage note about this for the Go4Up multi-hoster in general I think, toutbox being one of their hosts. As I recall, the only solution offered was to manually delete the extra bytes yourself, or not worry about the checksum.
I don't recall if toutbox shows up on any multi-hosters other than Go4Up. If it does, try that.
feedback, eh? Here are three things I think many people would like: 1. bold print to identify multi-file offerings on the homepage. I prefer the instant gratification of batch downloads instead of waiting for individual files, and it would be nice if they were easier to spot. 2. percent torrent is completed here, so we can estimate when to check back again. 3. Number of tries on Solidfiles, time to next re-try, so we can guess if it's worth waiting for. Other people may want that kind of info for other services, but I think solidfiles gets the most interest.
Thanks for getting back to me. There are separate processing queues for the various tasks, so it could be done before or after the upload. It can take a while at times - usually if a batch appears, it can hold up the queue a bit, but it should show up in the end (if it doesn't after a long time, then something may be up).
25/03/2016 09:22 — Anonymous