You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently BitTorrent magnet link in AirDC++ WebUI 2.11.0 looks like:
As you see, such link is not parsed as magnet link and is showed as a whole.
Please use human readable representation of BitTorrent magnet links. They follow the same magnet URI scheme as magnet links for DC and may be parsed in the same way.
For example, the same magnet links in EiskaltDC++ 2.4.1 look like:
EiskaltDC++ does not have support of BitTorrent protocol and opens such links in external application which is registered as BiTorrent client in the system. And this is normal behavior which is expected from DC client.
In FlylinkDC++ r6xx BitTorrent magnet links look the same way:
But FlylinkDC++ has embedded support of BitTorrent protocol and it opens links inside itself.
The text was updated successfully, but these errors were encountered:
Currently BitTorrent magnet link in AirDC++ WebUI 2.11.0 looks like:
As you see, such link is not parsed as magnet link and is showed as a whole.
Please use human readable representation of BitTorrent magnet links. They follow the same magnet URI scheme as magnet links for DC and may be parsed in the same way.
For example, the same magnet links in EiskaltDC++ 2.4.1 look like:
EiskaltDC++ does not have support of BitTorrent protocol and opens such links in external application which is registered as BiTorrent client in the system. And this is normal behavior which is expected from DC client.
In FlylinkDC++ r6xx BitTorrent magnet links look the same way:
But FlylinkDC++ has embedded support of BitTorrent protocol and it opens links inside itself.
The text was updated successfully, but these errors were encountered: