Admin, please delete all contents from animotvslash. They do not intend to share content to torrents, but seek traffix containing g*mbling ad* and malwar* from popup adz. and block keywords "Animotvslash" to prevent them from being available to animetosho. https://animetosho.torrentbay.st/search?q=Animotvslash
I have no idea if this is just my browser (Opera), although it's never happened before this week: right now if I click to display the full set of preview images, open any of the images, and hit the back button to return to the episode page, I see only the two base images, without the extras OR the option to unhide them. The only way to get the three additional images back is to refresh the page and hit the unhide link again. (If I open one of the two base images without expanding the set first, the unhide link will still be there when I hit the back button.)
Has anything changed in the coding that might cause this?
This situation really highlights the benefits of going upstream for some issues. Sorry about that! Also, I did report one torrent over at TokyoTosho because it wasn't Japanese media .... but now I don't remember what it was ... lol Thanks for looking into it!
Hey! Hope you're enjoying your long weekend Admin!
Real quick gotta say when I step and think about you first conceiving and building this "mirror" (it's so much more to us users!) and now maintaining this gem I find myself humbled. Just a quick shout out and thanks for your work and also your patience. 😉
On the series page (https://animetosho.torrentbay.st/animes) is there a way to filter skipped entries in the same was as old entries? (I tried filter_skipped=1 just in case it was undocumented, but it didn't work.)
If not, would it be something you'd be willing to consider adding?
its weird to use a gmail address for business when you "work" for a "marketing company". why not use your own domain for emails. getintoway looks suspicious and that link is unsecure according to chrome.
https://adfinity.buzz/blog/navigating-...actices/82 is the latest blog post from 2023 and it looks like ai-generated nonsense or just a stolen photoshop tutorial that has nothing to do with the title or the "business"
I see, but wouldn't it make sense to discard the cache if the oldest item in the feed is older than the cached items? And if it's newer, the next page of the feed should be fetched, as there could be better entries that have been missed. Basically, the only case where I see the cached entries making sense is if a feed doesn't support paging (which isn't an issue here).
If renaming or deleting NZBs isn’t viable, please consider blocking downloads of deleted release NZBs for clients with Sonarr, Radarr, Prowlarr, or NZBHydra2 user agents
Unfortunately this has the same issue. The 'deleted' flag is present on the webserver (animetosho.torrentbay.st) whilst the NZB is hosted on a secondary server (storage.animetosho.torrentbay.st). The two servers are disconnected from each other, so there's no way for the secondary server to know that the entry has been marked as deleted.
Unfortunately, there's just no easy solution to to invalidate the original URL in any way (other than deleting the file, but I don't want to do that).
03/05/2025 14:49 — Spark90