Offhand it sounds like it could be a drop in replacement for you. But there are a lot of other variables you’d need to consider e.g. if you require specific app/TV support & don’t like the current Jellyfin offerings.
Maybe others can clarify or you can post with any specific requirements/questions in the Jellyfin forums or the lemmy communities !jellyfin / !jellyfin
That aside you could always just try it out & see how you like it.
I’ve been considering moving to Jellyfin for a while, but I’m worried they will do the same thing in future.
Currently would not be possible. Jellyfin does not have the sort of centralized accounts/logins that Plex does e.g. you’re not asking Jellyfin devs for permission to log into your own server. That’s just a Plex thing.
If you’re asking could they add that “feature” in the future? Highly unlikely but I guess anything is possible. Were that to happen most likely the code would get forked into a new project.
PS - Jellyfin itself is a fork from Emby back when those devs decided to close their source. Myself & tons of other people dropped Emby at that point & migrated to Jellyfin. jellyfin.org/docs/general/about/
Basically, the author of the project scrapes the torrent DHT network
Is that accurate? Where is DHT mentioned?
Neither their github nor their main site makes any mention of DHT, also don’t see any DHT scraper in the git page git.torrents-csv.ml/heretic but maybe I’m not looking in the right place?
You can create a new torrent for that data if you want, that way you can continue seeding it in a new torrent swarm.
Otherwise if you intend to seed in the old torrent swarm then you need the old .torrent for that. Search around maybe you’ll find it (or if you remember where you downloaded it originally that’s even easier).
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.
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 (www.canyouseeme.org, 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.
You can though it’s a bit of a roundabout way of doing it.
P2P releases typically come from private trackers, so you’re having them go from private trackers --> usenet --> public/private torrents
Scene releases that leak to the public typically hit private trackers/usenet around the same time, so you’re having those go scene --> private trackers/usenet --> public/private torrents
In others words anything you’re seeing in usenet has already been uploaded to at least some private trackers & possibly public torrents.
Of course with public torrents anything goes, unfortunately with the demise of RARBG public torrent users are only seeing a fraction of scene/p2p releases. 1337x/TorrentGalaxy does cover some of this but they aren’t covering nearly as much as the RARBG uploaders used to. So IMO if you’re seeing a scene/p2p release that hasn’t already been uploaded at 1337x/TorrentGalaxy then sure go ahead & create the torrent from your usenet download.
Make sure you are fully connectable (port forwarded). To check this you will want to test your torrent client’s incoming connection port with a 3rd party port test website e.g. www.canyouseeme.org, www.yougetsignal.com/tools/open-ports/, portchecker.co, etc. Those websites should be able to successfully connect to your torrent client’s incoming connections port. If the test fails then you need to look at adding an incoming port forward in your network router’s configuration.
Also make sure DHT/PEX is enabled in your torrent client (those are enabled by default).
PS - The above is if you’re not using a VPN/Proxy (you didn’t mention using one)… definitely don’t re-configure your router configuration if you intend to use a VPN/Proxy, all port forwarding needs to happen on the VPN/Proxy server in those cases.