@Joker looks fixed on this end. Thank you

Confirmed, old items appearing as new is an issue with my news reader. If you are a RSSOwl user and want the details, you can DM me.

But in the process of digging into it, I did find something interesting about the RSS Feed.

Essentially, the feed is not sending the requested number of items based on the num= parameter, once a threshold is hit (250 items). Therefore, the ALL option is not really functional. Nor is changing the num= parameter to anything larger than 250.

Probably not a big deal when it comes to low volume categories like Vintage (which is my fav). That 250 item limit currently covers about 6 months’ worth of postings.

However, that same 250 item look back limit for categories like Bareback, which is much more heavily posted (thank you very much BTW guys), is currently only about 10 days. And catagory=Anal, only 5 days.

-donny

@kalayaan Thank you for responding. Here is the posting URL:

https://www.gaytor.rent/details.php?id=468caff0c4027e30c58bfdd4461cd7b44a1c6d1e8c1f3b55

Confirmed, old items appearing as new is an issue with my news reader. If you are a RSSOwl user and want the details, you can DM me.

But in the process of digging into it, I did find something interesting about the RSS Feed.

Essentially, the feed is not sending the requested number of items based on the num= parameter, once a threshold is hit (250 items). Therefore, the ALL option is not really functional. Nor is changing the num= parameter to anything larger than 250.

Probably not a big deal when it comes to low volume categories like Vintage (which is my fav). That 250 item limit currently covers about 6 months’ worth of postings.

However, that same 250 item look back limit for categories like Bareback, which is much more heavily posted (thank you very much BTW guys), is currently only about 10 days. And catagory=Anal, only 5 days.

-donny

@ianfontinell-0 My apologies, I should have grabbed and provided more specifics. I kind of assumed this was a known thing and I was just out of the loop.

So I'm hearing (at least from 1) you are not seeing the same behavior, at least not on the pull you are using. And the date I gave might be off a day one way or the other based on our TZ differences and when I actually noticed it.

I have already deleted the entry from my reader (RSS owl), but the next example I find I will grab the RSS file that gets downloaded from the site along with the URL that is was generated from. I use a bunch of different pulls, and then aggregate the results. I need to dig into which one(s) are doing this or if it is across the board.

I will say I have nothing to suspect my reader (RSSOwl).

Thank you for taking the time to reply.

Here is an example:
https://www.gaytor.rent/details.php?id=4e19d7e7a4e87228c58bfdd4461cd7b4fcd5d2af3802f216

Originally posted Aug'24, reappeared in the RSS feed 2/22/2025.

Does anyone else use the torrent RSS feeds consistently and if so, have you figured out why seemingly random old torrent posts will suddenly re-appear in an RSS feed? Like years old torrent posts. Is it because the posting category changed? I've yet to figure out what the conditions are but if someone knows, I would appreciate being educated as well. Thanks bunches.

-donny

Hi @suosai

It looks like it's some issue/limit with that particular navigational element, as the oldest torrents you can access are only 14 weeks old. Add any search term first to get it below that 10001 threshold and you can go back to 2007 or more.

Do note that search page does still indicate:

BETA: This view is under development. Give us feedback and tell us your opinion.

However, the link under "Give us feedback" is broken (points to a non-existent host), so a work in progress for sure. Feels like it just needs some more Web DEV time. I would imagine the domain change threw a real wrench in any dev roadmap that is still being worked through (just my opinion based on how these things evolve).

Also note the "old" search views navigation bar works as intended. Accessed via menu item Torrents > Search (old)

-donny

@ianfontinell - Thank you for that hint. It worked for me.

-donny

@kalayaan Thank you for responding. Here is the posting URL:

https://www.gaytor.rent/details.php?id=468caff0c4027e30c58bfdd4461cd7b44a1c6d1e8c1f3b55

I usually never have an issue with using the Reseed Request button on posts, but this one has me puzzled. When making a request, the returned result is:

Request failed - 0 PM's send! [sic]

Does this mean the "Request process" has possibly fixable issues sending PM's and I just need to open a Support request, or that there are zero active accounts meeting the criteria to send a PM to? Both are possible ways to interpret this message.

Thanks a bunch

Happy Pride!

-Donny

@Joker looks fixed on this end. Thank you

Same issue here. Started about a week or 2 ago, give or take. and it's not all the categories.

I use RSSOwl and I have broken out about 12 individual feeds based on category, and there are 2 URL's are failing currently with an "Invalid or Malformed feed" which is really just a generic failure message in RSSOwl.

This one is very specific (cat 12)
https://www.gaytor.rent/rss.php?num=99999&cat=12&passkey=xxxxxxx

And this one is like a "catch all" for the feeds I didn't need to break out, so it could be any one of the categories that is the issue**:

https://www.gaytor.rent/rss.php?num=99999&cat=1,7,63,32,35,38,40,65&passkey=xxxxxxx

**If i remove category 35 from the above URL, it works fine.

So a least 2 categories seem to be broken (12 and 35), but not I don't pull feeds for all categories so there could be more.

(passkey has obviously been edited for this post)

As BigJohyn noted, plugging each into FF simply prompts to save the file rss.php, which if I do and edit, looks like XML as expected.I have not run it through an XML parser to verify it is valid XML, which might be a next step.

My guess based on my experience of what can go wrong in XML, a torrent in the feed(s) has character(s) that are problematic. (aka, improper un-escaped special characters, etc). I say that because I had a third feed that failed for just a few days in the beginning and then resolved itself, like whatever it was angry with had worked itself though the aging process.

Thank you
-Donny