Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#4602 closed Enhancement (invalid)

In JSON-RPC, arrange torrent IDs on date added

Reported by: czarkoff Owned by:
Priority: Normal Milestone: Sometime
Component: Daemon Version: 2.13
Severity: Trivial Keywords:

Description (last modified by jordan)

As far as I can get, currently the torrent IDs exported by JSON-RPC are arranged somehow randomly. As the names of torrents may be somehow misleading, I often find myself searching for the several last torrents with transmission-remote -t N -i.

It would be useful to arrange the IDs on date the torrent was added to provide an additional mechanism for identification of torrents.

I could make a diff, but it will take some time to make myself home in transmission source, while the diff must be fairly trivial.

Change History (2)

comment:1 Changed 10 years ago by jordan

  • Description modified (diff)
  • Resolution set to invalid
  • Status changed from new to closed
  • Summary changed from In XMLRPC arrange torrent IDs on date added to In JSON-RPC, arrange torrent IDs on date added

Hi czarkoff, thanks for making this suggestion and helping to make Transmission better.

Your suggestion would make sorting by date happen automatically, but there are many ways to sort the torrents, and IMO that's an arbitrary choice that should be handled by the client rather than by the torrent IDs.

comment:2 Changed 10 years ago by czarkoff

Well, as I get it, the thing I wanted to change is the default sorting. That would be of use to clients that don't support sorting (like transmission-remote, which I am using).

May be I would better ask for change in transmission-remote then? But as I get it, all sorting happens on client side, so the clients that already have the sorting features (like WebUI and nearly everything else) won't notice the change, while those minimalist clients that don't do sorting at all (like transmission-remote) would.

Note: See TracTickets for help on using tickets.