-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[req]: Bitmagnet #15126
Comments
repo at https://github.com/bitmagnet-io/bitmagnet |
has torznab api endpoints so WEBUI development can be ignored. |
I cant progress this one, the docker compose is for an alpine build which wont run on my windows desktop docker, so I could not test this even if I wanted to create a cardigann indexer to make torznab queries and parse xml responses. |
I'm also interested in this but because it follows Torznab API I think it would make sense for Jackett to have "Add Custom Torznab Indexer" where you just point to any Torznab API compatible URL. That way no need to add such indexers in code. Potentially could be more such aswell. |
It's not about name and not duplicate. Only underlying protocol would be same (Torznab) but you could add any endpoints with whatever name you want. For example you could even chain Jackett itself. Consider this case I have 2 friends where they have access to private trackers but they don't want to share those credentials so they let me use their Jackett instance as another Indexer for my own instance. It would look like this
This essentially allows federation of Jackett. |
Yea, I understand that, but as we can't make duplicate indexers, it makes more sense that we'd add separate, named indexers for Bitmagnet, Jackett, Prowlarr, and anything else which might arise. |
You're thinking along the lines of what the *arr apps have. In the mean time, this ticket is focused on an individual new indexer request. |
Set bitmagnet up on my ubuntu22 image on my win10 VirtualBox and got the webui up long enough to see it gather a few torrents |
I've written a yaml indexer which works, albeit with some constraints.
but its a start and better than nothing. |
v0.21.2025 |
We also have Magnetico, another self-hosted DHT crawler, and it's set as semi-private. I'm not sure which of public/semi/private is most accurate (anyone can set it up, you don't need an account, so public makes sense, but as it's self-hosted and runs locally, by default no one has access but you, so private makes sense too), but they should probably be the same. |
Hmm. I don't think we can set it private and not prevent username/password input boxes showing up on the config |
Also I may have put bitmagnet in the wrong place in the readme, I was just duplicating the magnetico entry as a template ;-D |
Moved. |
did a little experimenting. |
So we could move them both to private I suppose, to reflect the view that its a personal indexer? |
Yea, makes sense. |
I just tested it and searching on Jackett itself seems to be working fine. But when I search on qBittorrent using Jackett plugin then results doesn't seem to contain anything from BitMagnet but always from other indexers 🤷♂️ Also it looks like magnet/download link is missing in results for it (maybe that's why qBittorrent excluded it?) |
If the Jackett dashboard search using the bitmagnet indexer shows results that all include a magnet link, then the indexer is working as it should. if the qBt plugin is showing the same torrents names as Jackett, but Jackett shows a magnet and the plugin does not, then that is an issue with the qBt plugin. |
It shows results but without magnet link.
Don't see point of creating new ticket. Here's log
We can see that Also btw if I click on torrent's name it opens homepage of
qBittorrent shows results that come from other Jackett indexers but results from |
Not possible to implement here right now because |
Ah. the indexer uses the yaml infohash statement (which takes the hash from guid and builds a public magnet link, because the yaml cannot process the torznab:attr fields). But what is happening is that since we switched the type from public to private 4 days ago, cardigann prevents auto-magnet-generation from the hash because that would generate a public magnet not a private magnet (which uses just one tracker from the private site). Forgot about that little gotcha ;-) I'll switch to semi-private and that should restore the magnet. |
v0.21.2090 |
Works fine now! Also shows up in qBittorrent. |
Is there already a request for your feature?
Is your feature request related to a problem? Please describe.
Not a problem, just a feature request.
Describe the solution you'd like
I would like to add the Bitmagnet self-hosted torrent search engine to Jackett :)
Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: