Learning what? One can definitely not be lazy and enjoy anime, so I wouldn't agree with you on that one. If you watch too much, well that's another story, though "too much" is quite subjective also.
Fair enough. Well, as it's largely automated, the volume doesn't really make much of a difference, although, honestly, maintenance and development does take out a large chunk of my free time. Hence, I actually don't watch much at all.
Is this a playback issue or a problem with this website's listings? If the former, it's either an issue with your computer's setup (you need to fix this yourself) or the file was authored with problems (you'll need to check the source links and report it to the submitter). If the latter, please give examples.
Would it be possible to fetch <http://www.nyaa.se/?page=view&tid=515801> "[ReinForce] SHORT PEACE (BDRip 1920x1080 x264 FLAC)"? It's without subs (there are subs in <http://www.nyaa.se/?page=view&tid=530518>), but I would really appreciate it! It's by the director of Akira, among others.
Most links on TokyoTosho actually link back to Nyaa. TT does have the added benefit of a magnet link, which the server does try to resolve, but I'm not sure of the success rate. So in short, having a posting on TT gives a higher probability of it working.
The issue appears to be gone now anyway - probably was some weird temporary routing issue.
Then if that happens then shouldn't the sever still pick it up if it gets placed on Tokyotosho or it won't cause of Nyaa's not being accessible at that moment for some reason. Since the torrent got posted on Nyaa's to being with.
You can try Jdownloader 2 (beta) for the time being until IDM updates. Try hosts like HugeFiles, direct downloads from MultiUpload.nl, or BillionUploads, those who have good speeds for anon people. Just test out some other hosts. Some the links I provide should give you a good speed too.
For some reason, my IDM cannot grab fichier file. Anyone have any idea or other file sharing that give download speed like fichier for 500mb file and over?
15:xx GMT+1 -> site wasn't loading at all, now 15:41 GMT+1 it's working again. The strange part is that it loaded the certiicate, and showed as connected, but with a blank page.
Well if anyone doesn't mind putting the effort to do all that, has reasonable design sense, has some CSS + Photoshop skills, and doesn't mind learning a few procedures, I don't mind delegating the task of making new themes to someone else.
I have no idea how a weekly theme would work in combination with style selector, and the image is supposed to be from the current season, which is a bit limiting, but I suppose something could be worked out as long you meet the above criteria...
I think someone would have to be really bored to go to the effort of obtaining the server's private key. Whilst theoretically possible to obtain, it's not a trivial task. And there's nothing particularly interesting to steal here anyway - there's no sensitive information here, and no-one's performing any critical task.
As you're somewhat pointed out, in the absolute worst situation, we're no worse than most other websites out there that don't use HTTPS.
If you don't care about that you might just as well not use SSL at all...
I'd have to disagree with you there however. You don't know whether the certificate is compromised, and even if someone did do so, it's probably not publicly available.
Though the primary benefit of HTTPS here is more to do with referrer hiding as opposed to encryption. I may do it eventually, but I don't really see it as particularly necessary...
Thanks for the information though.
Comment in Feedback 21/04/2014 02:49 — Anonymous: "Anonymous (but not OP)"
Yes! If your server was running any vulnerable OpenSSL version in the past then you have to get a new certificate after upgrading to a non-vulnerable OpenSSL.
Quoting heartbleed.com "Leaked secret keys allow the attacker to decrypt any past and future traffic to the protected services and to impersonate the service at will. Any protection given by the encryption and the signatures in the X.509 certificates can be bypassed. Recovery from this leak requires patching the vulnerability, revocation of the compromised keys and reissuing and redistributing new keys."
If you don't care about that you might just as well not use SSL at all...
18/05/2014 19:24 — Anonymous: "admin"