biglysoftware / biglybt-plugin-xmwebui Goto Github PK

hi there,
really just started with this - trying to build my own UI for this already amazing torrent client, but I believe i have read the rpc-spec file now a few times already. Whatever I try i always get the full list of torrents in my result set (3000+ at this time).

So this is the body of the POST call:
{
"method": "torrent-get",
"arguments": {
"fields": [
"id","sizeWhenDone","name","hashString","dateCreated","status","activityDate","uploadedEver","peers","comment","downloadDir","isPrivate","peersConnected","creator"
],
"ids": "recently-active"
},
"tag": "fake-tag"
}

so the question is about the "ids":"recently-active" part. How do i get a short-list of those torrents that are currently connected to peers AND getting or sending any data.
is this really supported, same is in Transmission?
thanks

@TuxPaper
Not really sure if this is intentional design but authentication settings are ignored if(?) you don't "pair" using an access code which seems really odd in several ways.

• Adding a new access code and hitting "Connect" button results in:
  Pairing details unavailable for 'remoteaccesscode': Access code 'REMOTEACCESSCODE' unknown
• There should be no requirements of using a 3rd party service to add authentication
• Always on without an option to disable the plugin (webui frontend) seems a bit odd and potentially a security issue

Hi folks,
Good job with BiglyBT, loving it on my Shield TV setup.

I did run into a small bug when accessing BiglyBT via the remote client. On Chrome v91 running on MacOS v11.5, using touchpad right click causes the context menu to first appear briefly on the correct spot - at the cursor - after which it immediately jumps to top left.

Digging further, touchpads seems to trigger a mouseEvent first, followed by a taphold event. The jQuery taphold event doesn't seem to have the pageX / pageY props for positioning, so the context menu jumps to the default position.

This can be reproduced with any taphold action, e.g. by pressing a mouse button for 1s+ on top of a torrent.

This can be fixed by using the original event (which does have the coords) instead of the jQuery one.
Adding the following invocation to context menu options in transmission.js does the trick:

$("ul#torrent_list").contextmenu({
    // ...
    position: function (event) {
        // Use originalEvent positioning for better taphold support on touch devices
            return { of: event.originalEvent }
        },
    // ...

As it is becoming easier to get legitimate certificates, can we get the ability to use our own cert.pem & private.pem file for our certs? might need chain as well?

Hi,
This is a follow up on 3. I'm trying to get some skins to work for biglybt, I tried transmission-web-control but it fails to retrieve some of the skin files

XML Parsing Error: no root element found
Location: http://localhost:9091/tr-web-control/lang/_languages.js?_=1517553460210
Line Number 1, Column 1:
_languages.js:1:1
XML Parsing Error: no root element found
Location: http://localhost:9091/tr-web-control/lang/default.js?_=1517553460209
Line Number 1, Column 1:

I digged more and found out the problem is that the server that comes with xmwebui doesn't allow get request parameters
so this fails:

http://localhost:9091/tr-web-control/lang/_languages.js?_=1517553460210

while this works

http://localhost:9091/tr-web-control/lang/_languages.js

I tried to modify the requests using a proxy and got the skin to load but not function so this might be a step in the right direction to get it working
Also, another problem is that the web server is not redirecting requests with double slashes
so this fails

http://localhost:9091//rpc

I suspect that these can be easily fixed and implemented, unfortunately, i don't program in java so I hope someone can fix them

This is similar to the #3 which was closed by the OP.
The problem is that some frontends that provide webui for transmission are not playing well with Biglybt
The webui I tested and didn't work is transmission-web-control

Other improvements related to this issue is we should have the possibility to override the default frontend files, Transmission has multiple ways of doing this:

First, it checks if the environment variable TRANSMISSION_WEB_HOME is set then it will use it as a path for the frontend files.
then it checks for a user directory ~/.local/share/transmission/web/, more specifically it checks for ~/.local/share/transmission/web/index.html and if it exists it will use that path as a frontend.
if all these don't exist it will fallback to the default directory ( /usr/share/transmission/web/ on Linux)
I think we should have a similar mechanism to override the default path since copying the files to ~/.biglybt/plugins/xmwebui/transmission/web is not very elegent and the files will probably be overwritten when the plugin is updated(haven't tested that), maybe also have a setting in the plugin to specify a custom path.

if you select an active torrent and push the 'Remove Selected Torrents' X button, the torrent file is untouched, so the torrent will restart at 0.

Can we get it to rename the torrent file to .torrent.deleted or something.

According to https://wiki.vuze.com/w/Vuze_Web_Remote this plugin aims to be at least somewhat compatible with Transmission's RPC procotol however trying two different frontends shows that it's barely at best. It would be a great enhancement to BiglyBT if played nice with software that supports Transmission.

There are more around but I tested two and neither worked.

https://github.com/transmission-remote-gui/transgui (fails to add torrents/magnet links)
https://code.google.com/archive/p/transmission-remote-dotnet/downloads (outdated but can add torrents, magnet links doesn't work)