WebTorrent Desktop 0.23
github.com
github.com
I don't get why the desktop app still doesn't allow you to select specific files. Am I the only one who wants to do that? It's a pretty standard feature in every other torrent client. Now that libtorrent supports WebTorrent protocol, I don't know what the value proposition of the WebTorrent desktop app will be.
Put some gloves on and help out. Maybe you could get your features on the roadmap.
A lot of people in your situation hire a developer to add custom features. If your skill level isn't as high as the work required it could take forever (making you homeless). In your case (low skill/custom requirements) it is best to invest with a professional developer who can make your dreams a reality.
If it's the latter, it's not going to work because the torrent needs to be seeded via WebTorrent(i.e. WebRTC). The desktop version of WebTorrent can download both regular torrents and web torrents because it's not limited to WebRTC for peer connections(whereas a browser is).
I've personally been working around this using a custom fork that messes around with the simultaneous connections settings of the webtorrent library, and it seems to help a bit, but I still get freezing from time to time when I download a large number of torrents simultaneously.
I wonder if an alternative Webtorrent implementation (not Webtorrent Desktop) in Rust on top of WASM might make those kinds of issues easier to avoid with its safeguards around concurrency and just generally making more efficient use of resources.
(Slightly edited repost from an earlier thread about Webtorrent, feels a lot more relevant on this one)
* https://github.com/anacrolix/torrent (Golang)
* https://github.com/arvidn/libtorrent (C++)
An implementation in Rust would be amazing, but there is a quite a bit of work to make that happen in pure Rust though! If you want to use FFI/unsafe code it is totally do-able :)
Though your point is partially valid now that libtorrent has recently added support for WebTorrent protocol.
The ephemeral nature of tabs discourages reciprocity, so I don't think supporting browser use is good for preserving content availability.
WebRTC uses DTLS, and ISPs blocking it is a pretty high blast radius. Also with conferencing being so important makes it much easier to hide. Tor's Snowflake did some good writeups on this also.
WebTorrent doesn't require a browser to use either anymore, so you could see lot more peers if you use both!
https://github.com/webtorrent/webtorrent-desktop/issues/1807
In-case anyone has the same issue... downgrading alone is not sufficient to fix, as the issue seems to be with the configuration stored in .config/WebTorrent Once you remove this and install 0.21 or less VLC will launch again.
https://github.com/standard/standard/issues/1381
https://news.ycombinator.com/item?id=20786981
i love javascript.
The premise is stupid and incorrect.
I'll just move on, this is nothing.