Transmission

Here's the link: https://rnelson.xyz/apps/monitor-for-transmission

Thank you.

A 1.0.2 version is pending approval, here's the changelog:
- Another (somewhat) less ugly icon
- Fixed a bug that prevented user preferences to be saved
- You can now swipe left on a download to delete/pause/resume it
- Download errors now show
- ETA doesn't show anymore when the download is finised
- Smaller Bugs squashed
- Aesthetic improvements

Sorry for the existing icon, here's the new one:

App works great, thank you and well done!

What are your plans for it? New features? Monetisation?

Cheers.

triage wrote:App works great, thank you and well done!

What are your plans for it? New features? Monetisation?

Cheers.

Hi. I plan to add queue priority management and download settings (including trackers and files and folders)

hi Rui,

The app works great and it's been great seeing the pace of updates these last days. Thanks a lot for freely sharing this with us.
Would love to pitch you a few €€ if you put up a donation link or make the app non-free on the store.

A small feature suggestion : sorting torrents by groups

Cheers

meego wrote:hi Rui,

The app works great and it's been great seeing the pace of updates these last days. Thanks a lot for freely sharing this with us.
Would love to pitch you a few €€ if you put up a donation link or make the app non-free on the store.

OK

A small feature suggestion : sorting torrents by groups

Cheers

Could you explain? Like adding them a tag/color? Please check if you're with the latest version (2.0.0)

Monitor.app wrote:

meego wrote:hi Rui,

A small feature suggestion : sorting torrents by groups

Cheers

Could you explain? Like adding them a tag/color? Please check if you're with the latest version (2.0.0)

Yes, exactly that.



In my case, i use Transmission's Groups to group torrents by tracker.

meego wrote:

Monitor.app wrote:

meego wrote:hi Rui,



Could you explain? Like adding them a tag/color? Please check if you're with the latest version (2.0.0)

Yes, exactly that.



In my case, i use Transmission's Groups to group torrents by tracker.

Ok, I'm going to plan it.

But mind you that those tags are client-only, meaning they won't sync with Monitor.

Monitor.app wrote:

meego wrote:

Monitor.app wrote:

[...]

Ok, I'm going to plan it.

But mind you that those tags are client-only, meaning they won't sync with Monitor.

Ah indeed. Forget it then, doesn't seem worth the trouble. Thanks the open ear though

Could you change the way in which servers/hosts are added? I use a reverse proxy on the server that hosts my Transmission client so I don't have to open up ports to the outside. i.e. I can go mydomain.com/transmission in my browser and it'll connect me. Adding the /transmission to the custom path does not work in this type of situation. The path really needs to be in the hostname so the only change that you would need to make is to allow paths in the hostname/IP input field. I can just set the port to port 80 manually in the port input field.

payeco wrote:Could you change the way in which servers/hosts are added? I use a reverse proxy on the server that hosts my Transmission client so I don't have to open up ports to the outside. i.e. I can go mydomain.com/transmission in my browser and it'll connect me. Adding the /transmission to the custom path does not work in this type of situation. The path really needs to be in the hostname so the only change that you would need to make is to allow paths in the hostname/IP input field. I can just set the port to port 80 manually in the port input field.

Hi.

The path is the RPC path, not the WebUI path

Try with /transmission/rpc path to see if it works. It should.

Monitor.app wrote:
Hi.

The path is the RPC path, not the WebUI path

Try with /transmission/rpc path to see if it works. It should.

I know this connects to the RPC path but that method won't work. The path has to be in the hostname and the way you have it set now paths can not be added to the hostname. When my server sees traffic to mydomain.com/transmission it redirects that traffic to <myserverip>:9091. The way you should probably is add servers is not having separate fields for hostnames/IPs and ports. Ideally they should all all just be added in the same field. If someone is using a custom port it would just be added in the hostname field as <serverip>:xxxx. (i.e. 192.168.0.23:9595). That way you can also allow people using reverse proxies to add them. Typically with apps like this that is how it works.

payeco wrote:

Monitor.app wrote:
Hi.

The path is the RPC path, not the WebUI path

Try with /transmission/rpc path to see if it works. It should.

I know this connects to the RPC path but that method won't work. The path has to be in the hostname and the way you have it set now paths can not be added to the hostname. When my server sees traffic to mydomain.com/transmission it redirects that traffic to <myserverip>:9091. The way you should probably is add servers is not having separate fields for hostnames/IPs and ports. Ideally they should all all just be added in the same field. If someone is using a custom port it would just be added in the hostname field as <serverip>:xxxx. (i.e. 192.168.0.23:9595). That way you can also allow people using reverse proxies to add them. Typically with apps like this that is how it works.

http://mydomain.com is the same thing as http://mymydomain.com:80

And https://mydomain.com is the same thing as https://mydomain.com:443

All HTTP traffic is TCP, and all TCP traffic has a port, just because you don't specify the port, doesn't mean there's no port. The default port for HTTP is 80 and HTTPS is 443.

Try http://www.google.com:80 for example...

I think it still hasn't been approved yet....

Also would like to request the ability to save downloaded files into the iOS device.

Regards.


Update: working now... looks like the price was being updated.

desimaniac wrote:I think it still hasn't been approved yet....

Also would like to request the ability to save downloaded files into the iOS device.

Hello, that's one possibility that I ruled out. Please use another App for downloading the files to your iOS device, I suggest Transmit by Panic!, Documents5 by Reedle or Infuse by Firecore.

If you want to return your App, please do it at https://reportaproblem.apple.com

mariad_10 wrote:Will download the app today for sure, and check how it works.

Thank you!

Monitor.app wrote:

payeco wrote:

Monitor.app wrote:
Hi.

The path is the RPC path, not the WebUI path

Try with /transmission/rpc path to see if it works. It should.

I know this connects to the RPC path but that method won't work. The path has to be in the hostname and the way you have it set now paths can not be added to the hostname. When my server sees traffic to mydomain.com/transmission it redirects that traffic to <myserverip>:9091. The way you should probably is add servers is not having separate fields for hostnames/IPs and ports. Ideally they should all all just be added in the same field. If someone is using a custom port it would just be added in the hostname field as <serverip>:xxxx. (i.e. 192.168.0.23:9595). That way you can also allow people using reverse proxies to add them. Typically with apps like this that is how it works.

http://mydomain.com is the same thing as http://mymydomain.com:80

And https://mydomain.com is the same thing as https://mydomain.com:443

All HTTP traffic is TCP, and all TCP traffic has a port, just because you don't specify the port, doesn't mean there's no port. The default port for HTTP is 80 and HTTPS is 443.

Try http://www.google.com:80 for example...

I understand all that. Are you familiar with nginx and/or apache reverse proxies? Because that is what I'm using and the way your app works does not work with reverse proxies.