For future reference for invites there's also
brickfrog
joined 1 year ago
May also want to try !seedboxes@lemmy.dbzer0.com and !seedboxes@reseed.it
Whatbox (and a few other seedbox companies) offer seedboxes in the US. How can they do that without being immediately shut down? Do they have some kind of restrictions that could cause problems with using a US-hosted seedbox?
AFAIK they do honor DMCA removal requests so if you happen to load a public torrent there & receive a notice Whatbox staff will ask you to delete that data. You could contact their support on that if you're not sure on their procedure.
How safe is paying via your real payment details?
I've only used crypto for those things. But presumably if you find a pre-paid credit card they accept you could buy it with cash & then pay the seedbox provider with that.
How safe is connecting via your real IP
The seedbox service itself is essentially a VPN so you either trust it, or you don't. You could just as well ask how safe is it to connect to your VPN, or if you need to use another VPN to connect to your VPN :P
One thing to keep in mind is that seedbox services probably do log more data than the typical no-log VPN.
For any of this to make a difference you should disable µTP in your torrent client, or make it prefer TCP over µTP.
Just as a caveat, people disabling/throttling µTP may want to manually set appropriate global rate limits (upload/download bandwidth) otherwise it's possible the torrent client will actually hit the maximum upload/download limits of the ISP or router forcing everything else on the network to slow down/time out during other internet usage. You're obviously more advanced so you already know all this :)
Mainly it's extra info for noobs messing around with their settings, often times noobs mess around with settings, disable things, etc. & then wonder why their torrent client keeps "crashing" their internet :P Making changes to µTP should be more of a last resort IMO.
µTP itself is a pretty big topic, there are a fair amount of people testing different settings in the qBittorrent / Libtorrent Github Issues but I'm not sure there's even a consensus on a proper default setting. e.g. qBittorrent's devs specifically chose different µTP defaults vs the Libtorrent library's own defaults. qBittorrent defaults to having µTP enabled with preferring TCP (throttles µTP), Libtorrent defaults to having µTP enabled with peer_proportional (does not throttle µTP). The qBittorrent default is reasonable though I wonder if the Libtorrent default is the more "correct" approach but that's certainly up to much debate. In both cases µTP is never disabled completely.
With my own testing I tend to keep settings at Libtorrent defaults just to observe behavior, with mainly private tracker peers I've noticed at least ~60% of my incoming connections are from µTP peers so at least for me it seems reasonable to keep it enabled.
There's very little info to work with so it's unlikely you'll receive any specific advice.
But mainly you do want to be fully connectable (port forwarded) so check that. Go to any port test website (https://www.canyouseeme.org/, https://www.yougetsignal.com/tools/open-ports/, etc.) and enter your torrent client's incoming connection port there. (for qBittorrent that is in Tools / Options / Connection / Listening Port)
If that test fails then you need to figure out what is blocking your torrent client's incoming connection port.
- If you're using a proxy that's the issue, won't get an incoming connection port via proxy
- If you're using a VPN service that does not support port forwarding then that's the issue, it is impossible to port forward on a VPN without port forwarding support
- If you're using a VPN service with port forwarding support then go to their website & figure out how to configure it, each VPN service is slightly different
- If you're not using a VPN/Proxy then most likely you'll need to log into your network router/firewall & configure a port forward there. Basically create a port forward for your torrent client's incoming connection port & point it to your local system on the network (your NAS)
Also make sure to whitelist your torrent client in any anti-virus/malware software you are using, those will definitely slow you down and/or block connections to your torrent client.
There's potentially other issues but everyone starts with being connectable first.
Your TGx link is broken, I found the correct one at https://torrentgalaxy.to/forums.php?action=viewtopic&topicid=2657 EDIT: Nevermind looks like Lemmy itself keeps breaking the link, try this linked version instead
Sort of related question: Do any of the torrent indexers with DHT crawler currently index Bittorrent V2 hashes? That would seem like the easiest workaround for finding V2 torrents since none of the general public/private sites have V2 support.
(I'm talking about sites like BT4G, BTDig, SolidTorrents, BitSearch, BTMET, Libtor, etc.)
You can double-check but AFAIK that VPN service does not offer port forwarding. It'll probably be even slower than your current VPN service since it's not really meant for torrenting or heavy usage.
Search around for earlier posts on VPNs with port forwarding e.g.
https://lemmy.dbzer0.com/post/2311570
https://lemmy.dbzer0.com/post/969323
https://lemmy.dbzer0.com/post/465513
https://lemmy.dbzer0.com/post/312389
etc.
I would look into port forwarding, but it seems like Mullvad doesn’t support that anymore?
Correct, in your case it is impossible to use any port forwarding until you switch VPN services. In the meantime you're basically stuck with whatever torrent speeds / connectivity you manage to achieve.
Wonder how active the project is, to date they still haven't included the old RARBG torrents.
https://git.torrents-csv.ml/heretic/torrents-csv-data/issues/1
However, the server doesn’t have the best power consumption, so I’d like to use WoL to remotely turn it on.
When you say remotely you mean over the internet, right? Or did you mean remotely within the same LAN e.g. from your living room or wherever.
By default WOL doesn't work over the internet AFAIK. The wikipedia page mentions it a bit https://en.wikipedia.org/wiki/Wake-on-LAN#Subnet_directed_broadcasts
Like others said you may be able to get that going with a VPN or anything VPN-like that allows broadcasts between connected systems. Or if your motherboard supports IPMI / IMM you should be able to connect to the system & perform power functions that way.
In my case my motherboard doesn't have those sort of management functions so in the end I settled on logging into my router remotely & initiated WOL through there. That could be another option for you if your network router is capable of sending WOL packets to the LAN.
However, the server doesn’t have the best power consumption, so I’d like to use WoL to remotely turn it on.
The ads were a Vuze thing, not BiglyBT.
When the devs left Vuze and forked the code into BiglyBT they never included ads or anything like that. That's what the comment meant, that since day 1 of the BiglyBT fork it did not include the ad junk that Vuze has.
Is there anything Jackett does that can’t be manually installed to qBittorrent as a search plugin?
Well yeah, Jackett supports around 585 public/private torrent indexers and trackers. You can view them all on their Github page https://github.com/Jackett/Jackett
AFAIK there are not 585 existing search plugins you can install into qBittorrent so Jackett has way, way more functionality in that sense.
The better question is whether you need all those as search plugins? Probably not, you're likely fine with a few search plugins for the bigger sites.
That's not the total subscriber count. Sounds like you're viewing the subscriber count from your specific instance at lemmy.sdf.org - The 3 subs you mention are subs from users at lemmy.sdf.org specifically.
To see the total subscriber count you'd have to view the communities home instance directly e.g.