I think it would be a great feature if we had a filter that adds a column "date" to the search results, so we can get to sort the swarms by newest to oldest.
Thus, avoid wasting time by going through the search results already returned by previous ones.
Search new swarms by date (sorting column)(5 posts) (3 voices)
I think it would be a great feature if we had a filter that adds a column "date" to the search results, so we can get to sort the swarms by newest to oldest.Posted 2 years ago #
If some dev is ever going to see this...
Do you mean the date the swarm was created?
I was thinking something like the date the swarm "initially entered the 1S network".
What I mean by that is: all possible ways, excluding the download of swarms from 1S's F2F network. (so that the date doesn't get overwritten each time a swarm is downloaded by someone)
For instance, this "initial date" would be set if a swarm is downloaded from a private traker and then added to 1S F2F.
Or if a swarm is created from the content of an external drive for instance.
But NOT if its downloaded from 1S's F2F network because it would obvioulsy already have been there.
This would help browsing through the search results of generic terms such as 'MKV'. A way to keep the newest swarms on the top.
But now I think an easier way to do this would probably be to save the hashes of the previous searches made through 1S interface in a temp file, and just putting the new swarms identified by hashes on top of the list.
To my understanding, each swarm has a (modified?) torrent file generated before any files can be shared, which is transferred between clients before download begins. I would imagine that it's possible to look up the time and date the file was created, and share that between clients when the torrent is being shared. It wouldn't be especially reliable information, but since the network is decentralized, that's probably the best you can do.
Community servers do keep track of how old the published swarms are, if they allow publishing that is.
You must log in to post.