I have no intention of culling at this point, as I don't see any need.
Torrent entries take up very little space in the end; storing the actual attachments would take up significantly more space (about 35x more at current estimates).

Just to mention a potential issue on the re-torrenting for subs idea, does admin intend to retain a database entry for every torrent that has ever been downloaded here over the years, or would the db be culled at some point to, say the last 2 years or something?  For performance issues, cost, and such.  Is there any point in extracting subs for db entries that would be gone a few months later?

Thanks for the advice.
At this point, I'm not sure whether I want to get really involved in it, or basically just put up what's needed to integrate with the updates server and see what someone else comes up with. I haven't exactly thought about it too much at this point, and I'm not even sure there's a lot of interest, so trying to stay flexible for now.

AT conceptually has two parts: an updates script (pulls torrents, uploads to hosts etc) and the website (what you see here).
The website is a fairly standard LNMP stack (Linux, nginx, MariaDB, PHP) and Sphinx is used for search.
Regardless of what technology stack is chosen for a rewrite, the database will still need to be MySQL-ish, as updates are sent via MySQL replication. I'm otherwise not too fussed on the technology, although it should be efficient (deal well with low RAM environments with slow disk I/O), not be a pain to administer and probably something that's relatively well known.

I'm not sure what would count as a "mistake". The code isn't well structured, but I knew that when I started - it was something I compromised on to get something working.

Ehh because I had to reload the site I didnt replied to the anonymous this time :c

The website looks quite old i.e like websites in the 90s looked like but with colors. Of course this is better than a flashy website and a simple design is favourable.

The good thing about the Material Design is that it looks simplistic, is not going to be garbage when "flashy" is modern again and has great visual feedback.

Of course I don't mean that the design should change completly, but with the material design the file entries could be a little bigger and when the user click on it instead of opening a new URL, make it appear from the entry click with a smooth transition for example.

Once you've got a script running, you can just leave it running in the background, using spare available bandwidth (does depend on where you run the script though).
Of course, the script would not only have to retrieve the torrents, it would have to extract and package up the attachments.

To get a project like this started, you'll ultimately have to plan it out, inform people what needs to be done, and give them a place to collaborate on it. Creating a design document in an easy to find place, where people can contribute suggestions, would be a good place to start. Do you have any preference for code hosting? If not, Github is a good choice.

I'd also be curious to know more about how the current site works (what programming language is used, how the databases are set up, etc.), and what works well and what does not so we can learn from mistakes.

Nah, the site looks fine the way it is. The current simplistic design has and will stand the test of time, whereas going with whatever appearance is trendy right now will mean the site will look outdated in the future.

Ah, so the issue is taking the time to write a script to retorrent the uploads, not the bandwidth involved in doing so?

I believe a fresh Material Design would fresh up the page :)

Googles Material Design Lite should work fine for this site^^. Sadly I don't have time currently :(

I probably didn't make it clear that I was more interested in a script which would automatically run through a lot of torrents and extract from them (in the end, it would need to match up with AT's database so that I could host it).

Try the comment above for another archive, and I'd recommend uploading subtitles there if you wish to share them (as they accept user submissions).

Thanks for the thorough reply, and I do agree with all your examples (and intend to actually keep it that way).

I should probably expand on some of the things that I was somewhat interested in (although didn't really want to force things towards a strict direction):
- I think the design could be improved a bit. Note that this does NOT mean adding a lot of fancy graphics/banners etc - I want to keep it lean like it is now. I'm not really a designer, so can't really come up with any particularly good ideas, but stuff like the colour coding of items isn't exactly intuitive, or the dump of links when you click into a torrent (source links, article, series information, downloads etc) could probably be organised better
- an API would be nice, as a commenter mentioned
- perhaps better feed (RSS) management, better search capabilities etc
- perhaps make better use of the AniDB metadata that gets attached to torrents (like the episodes page, for example)
- I don't really like to make changes to the current codebase due to it being quite messy
- Performance issues: some parts put an unnecessarily high amount of load on the server.  I'm also somewhat stingy and try to run things on low spec servers to save costs, so performance improvements are always welcome (and there's plenty of scope to improve this)

1. I do want to keep the same feel of Nyaa/TT on the homepage - that is, fairly light and simple.
2. I'm not a fan of chatboxes either. But if it ever happens (quite a bit if), it'll probably be a completely separate page, not something that gets embedded in the sidebar or other distracting variant.
3. I have mused with the idea of a forum, but only as a replacement to this feedback page. I don't intend to actually manage a forum community, so it would be minimal at most. The forum just makes finding stuff a bit easier (it's pretty hard to find a particular post on this feedback page, for example). There are plenty of other anime related forums out there, and I don't see any point in joining in.
4. There's plenty of other streaming sites out there, no need to duplicate functionality. I have been considering compiling a list of external resources for each torrent (for example, other sites which host downloads/streams etc), which might come in handy for someone.
Loss of file hosts: ultimately can't do much about it as I've got no control, so ignorance is the only real option here. From experience though, there's usually something else that pops up.

Hope that addresses your concerns and thanks again for the feedback! :)

Yes there is.  It's pretty much all fansub:
http://bit.ly/1HjgFAW

(I hid it because some don't like the site to be mentioned publicly.)

If the website ever gets a rewrite, I would be interested in putting in an API, so that applications such as streaming clients and auto downloaders could be implemented. Just something to get metadata about series, episodes, and the links to them, nothing too complex.

That's too bad, because there really isn't another website that archives fansub scripts.

I might go through what I have downloaded and extract the attachments.

When a site gets over 4 million pageviews per month and yet gets so few user comments as AT does, it tells you something very important: The users are very satisfied with how things are at your site.  They come to AT, get their anime and go.  Any new features you add to this site might not be the same as progress.  For example:
1. The AT webpage is Spartan (lean, simple) and fast loading.  Adding slower loading fancy rotating banners or graphics = progress?  Maybe not.
2. If you added a homepage chatbox, people will use it.  But progress?  Check out some anime/fansub chatboxes.  
3. Adding forums: It takes a lot of dedicated people with nothing better to do, to keep a forum alive.  Progress?  Maybe it's better if people who want a forum to go to the fansub sites.
4. Adding streaming playback?  Not why I do or would come here.

Based on the user comments I've seen, I think the number one actual user concern would be: What if AT lost Solidfiles or Userfiles?  And with 75GB uploaded to each file service every day, and the long list of fast file services previously lost to AT, that is a worry.

For anyone who happens to see this: is there anyone out there who's willing to help with developing stuff for AT?
With limited spare time, I'm musing with the idea of trying to open this project up a bit more (to contributions), but firstly need to gauge the interest.

Unfortunately AT's codebase is somewhat messy (never really expected AT to stay around for so long, so never initially put much effort), has some odd requirements and, as a free project, there isn't really much in the way of reward (except for personal achievement perhaps), so I've been a little reluctant to reach out. But since we've been around for a while now, and I hope for that to continue, perhaps some of you out there may be interested in implementing stuff you wish AT had (for example, the comment above this one).

Main thing I'm interested in would be improvements to this website, or rather, a complete rewrite of it. I've wanted a rewrite for a while, but have balked at the amount of work required for it. I'd like the rewrite of the website to be open source, as it may help with getting more people involved (and satisfy those who've been pushing for it to be open), although it won't be particularly useful to anyone else without the updates script.
As for the updates script, I intend to continue working on it by myself for now, although I can be flexible.

So is there anyone interested? If so it would be great if you could mention what you'd be interested in helping out with (e.g. website designs, writing the code for a particular feature etc). Again, only trying to see what interest there is out there - there's absolutely no commitment and it may never eventuate.

Not particularly likely as we don't have copies of the original files any more.

Maybe one could re-torrent what's still available and process them, but it's very low on my priority list (read: 99.9% won't happen) unfortunately.
If anyone's interested enough to put the effort in to do it themselves though, I don't mind the idea of hosting it.

Is there any chance of having dead links for MKV attachments and subtitle scripts reuploaded on Animetosho? I noticed they are now being hosted on AT's own servers instead of on external sites.

That's alright. I think I'll just use it and start my own archive of anime I minisize for myself.
Who knows, maybe someday I'll build up a large enough archive to be of use for people looking to find this stuff later on. Although, I'm only actually likely to do this for DVD/Blu-ray releases. Of which I have a lot saved up already. Running out of space so I need to condense it down!

Thanks for the suggestion.
500GB actually isn't as much as you think; unfortunately, the average size of episodes is probably a lot higher than 350MB*, thanks to 1080p rips that often lean towards 1GB or sometimes 2GB per episode.
* My speculation, haven't tried adding the figures to see what the average is

TT/Nyaa probably aren't really good candidates for archiving if you want to be selective. Something like BakaBT would probably be better, though they likely have a decent amount of seeds on most things.
And if you're being selective, I suppose you could exclude those 2GB per episode rips too.

If you mean just extracted subtitles (not including video/audio), AT's been storing those for over a year now.
If you mean just fansub material (including video/audio), as the above commenter notes, we only fetch those, (minus the occasional spam torrent, which, size-wise, are generally insignificant) excluding dubbed content.

AT's 75GB/day are English sub/dub

Storage is always expensive, but it really just depends on how much you want to store. I've found deals for 5.99 euro/m for 500GB of storage, which is actually a lot. With that amount, at an average size of 350MB per episode, that is still enough storage for over 1,300 episodes.

That said, not really a good option with auto uploading of 75GB per day. It would be more for selective archiving. Say, just for english subs for example. And only one copy of each episode.

thanks

Have yet to see something like that (without other drawbacks) unfortunately.
Storing large quantities of files is problematic due to costs etc.

I do like the idea of an archive, but can't see how to do it feasibly.
If you do have suggestions though, I don't mind hearing them :)

np, I just wanted to know. I'll get the show out of usersfiles for the time being

Right now there's a backlog of about 50 shows for Solidfiles.  Solidfiles has been pretty reliable lately, although they have some history of occasional problems.  All the links should eventually get thru.  Sorry about that.

is solidfile overloaded / has massive backlogs? new link aren't appearing.
not all of them, some do appear. just asking.

Well, the 75GB per day is the killer for me, hah. My hoster doesn't do all that bullshit stuff to try and force people to buy an account, so not worried about selling accounts since nobody buys them anyway. No reason to.

Little support, I think.  Most of us are looking for the fresh new releases of anime, not another archive of the old stuff.

Keeping an archive would be very expensive as well.  AT downloads 75GB of new anime releases every day.  Then you would discover the next leg of the attack after dmca is to disable any sources of revenue for such a filehoster, like paypal.

What kind of support would there be for a filehost made to be immune to dmca, just to have a place to upload anime without it being deleted shortly after? I currently have my own filehost site, but as of right now it has only been used for my own website's purposes. As a means to stop having to deal with dmca trolls. Been pondering the possibilities of expanding the use for this website.

Sorry man, maybe I'm a fool but I do know my ISP quite well, both with consumer-type and company-type contracts/basis.
It's true that an ISP has a lot of power, expecially when monopolistic or de facto controlling the market, but it's not godlike, at least here it's not (and it's basically monopolistic here, at least if you need real BW).
They can be smart and powerful, but depending on the situation you can outsmart them.
Anyway they can't block shit without a court order, and the proceding here take quite a long time, seen that a lot. Maybe not paradise, but not hell yet. ;)

You should check your Terms of Service.  It generally eviscerates any rights you think you have.  ISP's can do anything they want, including terminating your service and reading all your traffic.  Court orders are only required to force them to do what they don't want to do.

Fool's paradise, buddy.

As far I know my ISP can force the use of their DNS only if you have their hardware (AP), but I got mine.
Also, if they were to really enforce it they would just do plain IP blocking and don't care about user DNS.
But for both of those they would need a court order.

Ah I see - thanks for your input! It looks like Tibb is also posting FF links (thanks Tibb!)

Thanks Tibb!

Sorry to trouble you tibb sir, but I was just wondering if you would beable to provide solidfiles/usersfiles links for this anime? (Puchi Eva: Evangelion@School)

https://bakabt.me/torrent/153135/puchi...tertheblog

It would be much appreciated.

*sites

1. go4up used to post news info every couple of weeks, but the last update was May 9th -not a good sign
2. reviewing HS 720p Fairy Tale for last 4 eps, about half of the download locations have that error.  It may be go4up's way of rotating featured sights.

There's another anime site that uses only Filefactory and Rapidgator, as a supplementary resource for FF
http://www.anime-sharing.com/forum/new...leases-77/

How come most Go4Up links are no longer working? I tend to use the Filefactory links, but noticed they're always showing "error occurred" as of recently...

Tibb-sama could we get http://www.nyaa.se/?page=view&tid=302087 and http://www.nyaa.se/?page=view&tid=404285 on yukino please^^? Would love to watch it after the UTW one is over^^.

Good that they didn't take too long.
Thanks for the update!

OpenDNS fixed it. Maybe a lot of ppl let them knew.

I have to say that there's a number of things I don't agree with with OpenDNS.
They used to hijack NXDOMAIN responses for ads (good that they don't do it any more), and now this. Never mind that modern browsers already have phishing site blacklists and all that, there's no reason for a resolver to do this in my opinion.

Google's DNS doesn't do any of this, and hence, seem to be a good alternative.

Thanks for the info!

I assumed you knew and posted the link for any interested.  

the ISP thing - as I recall, they can block or revert attempts to change the DSN without the user's knowledge.  but I haven't looked into such stuff recently.

probably your ISP one, as most modem defaults to that.

I know how to change my dns, and it's not my ISP (which has its own DNS).
I just posted to make it known.

p.s. solidfiles isn't blocked by whatever DNS my auto setting is accessing.

you probably know about changing your DNS:
https://developers.google.com/speed/pu...docs/using

but it may depend on your ISP also.