Deluge Remote Modern - A completely rebuilt, Manifest V3 extension with Dark Mode! Chrome & Firefox

[ambipro]

I guess you can deal with the bug when you can, I'm just going to get SSL working, seems like a faster and easier alternative.

[ambipro]

Setup SSL locally for it, HAproxy and ACME certs. I think (as I said it might) the amount of torrents I have might be too big for it? It loads the pane for the plugin but doesnt display anything or respond (the drop downs for state/label/etc)...they're all just empty drop downs.

Maybe i'll load up a test container of deluge with only like 20 torrents and see if that works.


Also, when selecting HTTPS, should the port be switched from 80 to 443? Because auto filling that might be a little easier than assuming users know that SSL should be on 443 :P

[tsa3000]

https://addons.mozilla.org/en-US/firefo ... te-modern/

[tsa3000]

I will add paging to the add-on if it exceeds 20 torrents, and an option how many torrent/page.
Could you try to to filter on downloading state

[tsa3000]

Could you please try this one
https://send.vis.ee/download/6b11dff654 ... kqwJDOFB8Q

[ambipro]

Could you please try this one
https://send.vis.ee/download/6b11dff654 ... kqwJDOFB8Q

Seems to work now :)

Wondering how hard it would be to paginate it automatically, also adding a search function if it's storing the full torrent list - although you can also search with the API using terms so that might be a better way, not sure haven't measured the performance or know much about the way you're storing the torrent list.

Good work though, a few fine tuning of the setup page I recommended get done? That's not as big of a deal but onboarding is always one of the most difficult things to get right.

Let me know if you need anything else tested, more than happy to help. Also perhaps setup a github for it so others can contribute if they want?

[tsa3000]

Glad it's working now! Appreciate the detailed feedback.

Pagination: Actually shipped in v2.5.0 today — Options → Extras → "Torrents per page" (default: All). Dropdown lets you pick 10/20/50/100 with Prev/Next buttons at the bottom of the popup. Good call on whether to paginate in JS or via API — for now it's client-side since Torrents.update() already pulls the full list for global counts/filters, but if someone has 50k+ torrents the API approach would scale better. Something to revisit.

Search: Good idea. Could add a text filter box next to the existing State/Tracker/Label dropdowns that filters by name in real time. Client-side search on the already-loaded list would be fast enough for most libraries. I'll add it to the backlog.

Setup page tweaks: What did you have in mind? Happy to hear the specifics — always open to onboarding improvements. Already added the Test Connection button in v2.4.0 based on your earlier feedback.

GitHub: Already up, both repos are public and accepting PRs:

• Chrome: https://github.com/TSA3000/deluge-remote-modern
• Firefox: https://github.com/TSA3000/deluge-remote-modern-firefox

Chrome v2.5.0 just hit the Web Store (pending review). Firefox version coming next — I'm keeping them in separate repos since the manifests differ enough to make a single build pipeline messy. Feel free to open issues or PRs on either.

Thanks again for testing!

[ambipro]

I think the number of people with >10k is probably few, I have quite a bit across several clients, Deluge, rTorrent, and qBittorrent for development purposes. That one client was a middle of the road for me, figured I'd test it with something with enough to perhaps stress the plugin.

As for the setup page....

As I mentioned, switching between https and http should assume https is 443 - default http port is 8112 in deluge. You could assume that or make a note of default ports, I'm not sure if people run https on ports other than 443 - I don't personally use https for Deluge as I both use thin client and also only have local traffic. That's kind of up to you whether to do this or not.

The "badge timeout" I'm not really sure what this means, I mean I get that it sounds like it is for newly added torrents, but if you're refreshing the list at a given interval is this value something that is necessary or can it not be the same as refresh?

Debug mode - perhaps a tool tip on what exactly this is showing - maybe a console window with the actual API calls so you can see what is being sent/received by Deluge?

Context menu - this sounds like I should be able to right click a torrent and get some level of management, but there is no context menu for this.

Label support - you can get the enabled plugins by using core.get_enabled_plugins - which if label is assigned, you can then get the labels with web.update_ui by passing the label parameter included with the name/hash/etc...you can then also sort by label. Same can be done for trackers, however if the tracker is failing from startup it will show no tracker present. Sorting by Error'd torrents would also be advantageous if you're looking to manage from the plugin. I know you already have labels present in the UI, but sorting is another feature that I'm referring to.

If you need help with API commands, let me know. I wrote the Deluge integration for cross-seed so I'm pretty familiar.


Just some thoughts.

[ambipro]

Glad it's working now! Appreciate the detailed feedback.

Pagination: Actually shipped in v2.5.0 today — Options → Extras → "Torrents per page" (default: All). Dropdown lets you pick 10/20/50/100 with Prev/Next buttons at the bottom of the popup. Good call on whether to paginate in JS or via API — for now it's client-side since Torrents.update() already pulls the full list for global counts/filters, but if someone has 50k+ torrents the API approach would scale better. Something to revisit.

Search: Good idea. Could add a text filter box next to the existing State/Tracker/Label dropdowns that filters by name in real time. Client-side search on the already-loaded list would be fast enough for most libraries. I'll add it to the backlog.

Setup page tweaks: What did you have in mind? Happy to hear the specifics — always open to onboarding improvements. Already added the Test Connection button in v2.4.0 based on your earlier feedback.

GitHub: Already up, both repos are public and accepting PRs:

• Chrome: https://github.com/TSA3000/deluge-remote-modern
• Firefox: https://github.com/TSA3000/deluge-remote-modern-firefox

Chrome v2.5.0 just hit the Web Store (pending review). Firefox version coming next — I'm keeping them in separate repos since the manifests differ enough to make a single build pipeline messy. Feel free to open issues or PRs on either.

Thanks again for testing!

I know its typescript, but i'd imagine you can get the idea. If you just wanted to see some more API usage examples.

https://github.com/cross-seed/cross-see ... /Deluge.ts

Wrote this a fair bit ago, but it's obviously still relevant. Specifically, I think it might also be advantageous for you to connect the webui to the RPC daemon if it's disconnected as well. Upon restart, that may not be something the webui does automatically in some cases.

Specifically https://github.com/cross-seed/cross-see ... #L165-L199

Just another thought I had...you could even add a check to see if it's connected, then provide a connection manager - as you can connect the webui to multiple RPC daemons (not simultaneously, obviously) if there are multiple in the host lists.

[tsa3000]

I will be working on this