Transmission

livings124 wrote:I was about to write a long response to each issue, but I realize that anything I say that you do not agree with will get me called arrogant. I am not going to waste any more time with this issue.

Sorry, that was a little harsh. My point, though, was that you didn't seem even interested in understanding how it was being used... which is frustrating because the people using it and asking for it's return were using it as designed. The why and how is implicit.

The "why are you doing that" should be directed at the folks who were using it improperly and breaking it. But I guess killing the feature is easier than re-educating such folks. So be it. I can live with that. As I said, losing this is frustrating but not a deal breaker.

livings124 wrote:It shouldn't be Transmission job to track around a file it has no need for.

You know, I agree with that logic. Until this discussion, I didn't realize Transmission was internalizing the torrent files.

My new understanding is that Transmission takes an initial torrent file and imports it into an internal database, making the initial file redundant and deletable. So, Command-S will export that information back into a .torrent file? Which I can then pass to another client, if needed?

phydeaux wrote:

livings124 wrote:I was about to write a long response to each issue, but I realize that anything I say that you do not agree with will get me called arrogant. I am not going to waste any more time with this issue.

My new understanding is that Transmission takes an initial torrent file and imports it into an internal database, making the initial file redundant and deletable. So, Command-S will export that information back into a .torrent file? Which I can then pass to another client, if needed?

That would be useful. I didn't even know that existed. In fact, until this discussion, I didn't realize Transmission was internalizing the torrent files.

That's exactly what's happening.

livings124 wrote:

phydeaux wrote:My new understanding is that Transmission takes an initial torrent file and imports it into an internal database, making the initial file redundant and deletable. So, Command-S will export that information back into a .torrent file? Which I can then pass to another client, if needed?

That's exactly what's happening.

Would it make sense to include a statement as such related to the "trash on add" option? Parenthetical, or a hover/tooltip? Maybe if it were clearer that Transmission had no further need of the file, those of us using the files for more than Transmission would have a better handle on managing them.

I think the fact that the option to auto-delete exists implies it is no longer needed.

I, too, just came here to see what had happened to the "remove torrent file" and "remove all files" options, as I, too, used to use them as a part of my torrent management process.

Without wanting/meaning to wade into what appears to be a bit of a shit-storm, and not meaning any disrespect, I'm curious where I can find some documentation on how Transmission actually works, and how I can use it effectively to manage my torrents?

I've spent some time looking through the web sites and forums and docs, and haven't found anything to help me.

Did I miss something, or do they not exist?


TIA


...nettdata

Another person looking for a REAL reason for getting rid of the Remove Data File/Remove Torrent File functionality. I understand that you want to change the default to be remove torrent and ignore the original, but surely there's some kind of halfway house. Judging by the amount of people coming here looking for this it's clear I am not alone in this.

What about only maintaining that link while the file is where Transmission thinks it's supposed to be, if it's moved then it doesn't care any more. Just because you found it didn't work 100% of the time shouldn't mean you remove the functionality, maybe just change the implementation?

Once added, Transmission no longer cares about the torrent file, period. There is no reason for you to keep it, there is no reason for Transmission to "own" it. I have yet to hear a (valid) reason why this option is needed with the existence of the "save torrent file" option.

livings124 wrote:Once added, Transmission no longer cares about the torrent file, period. There is no reason for you to keep it, there is no reason for Transmission to "own" it. I have yet to hear a (valid) reason why this option is needed with the existence of the "save torrent file" option.

Because it adds steps to how I manage my torrents.

I download torrents into a folder from various apps I've written that do so while I'm not home, kind of like TED.
Transmission automatically adds those torrents once they've been detected in that folder.
Data file is then downloaded/seeded.
Once I see, WHILE IN THE TRANSMISSION GUI, that it's downloaded, and been seeded, I want to delete that torrent file, because I don't care about them any more.
Previously, I could right-click, delete torrent file, and I was done.

I now have to open a finder window, find the torrent, and delete it.

That's a PAIN IN THE ASS.


As an end-user, I prefer to do it the old way. It may not be how you do it, or how others do it, but please don't consider it to be an "invalid" way of doing things.

If you don't want to do it that way, then fine, that's your prerogative. But that's how I've been doing it, and it's worked well for me.

The new, "valid" way of doing things is enough of an annoyance that I took the time to come here, create an account, and begin this discussion.

And just so you know, I've been contributing to various Apache projects for over 15 years, so I get the whole "be happy with what you get" headspace, so it's not like I'm trying to appear ungrateful or anything... I get where you're coming from.

I just hope that you can see that "because end-users like to do it that way" is just as valid a reason as any to keep a feature. Never mind the fact that it already exists, and should be quite painless to re-instate.


$0.02

Now, if there's another way to accomplish what I'm trying to do, I'd love to hear about it.

Like I said earlier, I've looked around some of the documentation, and don't see anything that mentions anything like that.

You sidestepped my question completely. Why do you need the .torrent file while it's downloading and seeding? If you need the torrent file for whatever reason, why can you not obtain it through Apple-S?

That's just it... I don't need the torrent file at all. i don't want the torrent file. I want to delete the torrent file.

You mentioned earlier that you don't need the torrent file because it gets inserted into an internal DB, so great, I don't need it at all.

Other than (previously) right-click-delete-torrent-file, or using the finder, what other options are there?

It'd be great if there was a "delete torrent file as soon as it's loaded into transmission" option... that would be ideal.

nettdata wrote:It'd be great if there was a "delete torrent file as soon as it's loaded into transmission" option... that would be ideal.

Preferences -> Transfers -> Trash original torrent files

Awesome! I'm an idiot. And I had no idea that was there.

THAT makes sense.

That's all I needed to know, but didn't until now.