Droolio

Suppose one way around it would be to rent a cheap VPS in the UK and piggy back off the connection?

Otherwise, there’s a s2 ‘NORDiC’ version going around which is actually in English audio - just with various scandiwegian soft subs, so it’s defo out there. DM me if you still struggle to find it.

More people should use BiglyBT and its Swarm Merging feature. You get the ability to seed or download chunks from peers across separate torrent files.

It’s a shame because if more people used it, the BiglyBT devs might add hash-based merging (with v2 torrents) instead of just size-based. Hybrid/v2 merging is still possible, but file size is less reliable and caters to files only larger than 50MB.

Some kinda auto v1/v2/hybrid private<->public torrent maker plugin for BiglyBT would be… bigly.

If qBittorrent/qb-nox is bound to your VPN interface, then 1) your VPN needs to support port forwarding, and 2) forwarding a port on your router is pointless and unnecessary. Your only way around it is to switch VPN or don’t use VPN and then port forward.

Actually, ufw has its own separate issue you may need to deal with. (Or bind ports to localhost/127.0.0.1 as others have stated.)

The next best alternative would be BiglyBT’s Swarm Merging feature (which works similarly, and amazingly well on v1 torrents considering it only stores a precise file size instead of a hash in Vuze/Bigly’s own DHT). I’ve been able to ‘complete’ numerous separate torrents where availability was <1.

BiglyBT already supports v2 but dunno if Swarm Merging works with such torrents yet.

Thank you for posting this, hadn’t heard of it before.

Yes, I also work in IT.

The paid GUI version is extremely cautious on the auto-updates (it’s basically a wrapper for the CLI) - perhaps a bit too cautious. The free CLI version is also very cautious about making sure your backup storage doesn’t break.

For example, they recently added zstd encryption, yet existing storages stay on lz4 unless you force it - and even then, the two compression methods can exist in the same backup destination. It’s extremely robust in that regard (to the point that if you started forcing zstd compression, or created a new zstd backup destination, you can use the newest CLI to copy data to the older lz4 method and revert - just as an example). And of course you can compile it yourself years from now.

The licence is pretty clear - the CLI version is entirely free for personal use (commercial use requires a licence, and the GUI is optional). If you don’t like the licence, that’s fine, but it’s hardly ‘disingenuous’ when it is free for personal use, and has been for many years.

IMHO, Duplicacy is better than all of them at all those things - multi-machine, cross-platform, zstd compression, encryption, incrementals, de-duplication.

Wouldn’t you be on CGNAT though? How are they blocking it - at the DNS level? Have you tried a CNAME record that points your own domain to the actual duckdns domain? Just curious how/why they might be doing this.

If they’re supposed to be binary-identical data (same file checksums), you can use BiglyBTs Swarm Merging feature - without manually copying (which isn’t as reliable due to the start/end of the files not bordering on the chunk boundaries.

If they’ve been modified in any way though, this won’t work. However, you might be able to use its Swarm Discovery to find other torrents with the same data and complete with Swarm Merging.

It’s no different than any other client, and looks like the torrent is healthy so should just work.

As with all BT clients, you get better connectivity by forwarding the designated port. Does it say NAT OK at the bottom of the window?

Have heard ppl used it with that many but not tested myself.

Yea qBittorrent, chosen as was meant to be lightweight so runs in a docker container on a Raspberry Pi 4 (but often eats all 8GB available RAM - could be just a problem with the docker imagine tho.) Haven’t used Transmission so can’t compare.

Compared to the memory footprint of web browsers, a Java BT app is pretty tame on modern computers these days. Nor do you have to faff around with installing JRE manually. It just works.

Resource usage is pretty good tho and it can handle hundreds of torrents with ease.

Towards the end of its life, Vuze started adding crap like ads in the sidepanel and spyware in the installer. Plus a bunch of useless features like DVD burning and ‘content network’. My guess is the two main devs got involved with some investors at the time of the Azureus rename and didn’t like the way it was heading, so forked the project and rebranded to BiglyBT so they could go it on their own. Since it was open source, and mostly their own code, they couldn’t really stop them. Edit: More info at TF.

Sad thing is, many people are blissfully unaware of the history and still running Vuze to this day - when it hasn’t been touched in 6+ years. Amazingly the site is still up but nobody’s home, so its very risky to be using an out-of-date client like that with a spyware-laden installer - with the very real possibility of the binaries being switched out. (Their SSL cert has lapsed several times.)

The good news is, if anyone’s still running Vuze, BiglyBT is a straight swap-out.

If anyone’s unfamiliar with this client, it’s been around a long time, and was previously named Vuze (and before that: Azureus)!

Tis been under active development by the two main devs for all these years. The adware crap was removed from day 1 of the fork and it’s a really solid (and featurefull) client. Highly recommend. Also does I2P.

The absolute best feature is Swarm Discovery and Swarm Merge, which lets you find identical large files across different torrents and cross-seed and merge said torrents while downloading both. With Swarm, I’ve been able to download torrents with <1.0 availability - completing both torrents and become the seed hero. And this was before it supported the v2 BitTorrent spec (which gives you individual file hashes).

I still use qBit for my *arr automation but BiglyBT is always there for everything else and as a great backup client.

Well your account is on lemmy.world so how d’ya know the issue isn’t with your own access to the front end?

Many don’t interact with the lemmy.world directly, so we might only see delays in post propogation (if there is such an issue on the backend - I don’t see any but could be wrong).

I agree picking the biggest instances isn’t great from a scaling perspective, but s’gonna be hard to move any community once established.