Feature requests and code improvement #137
Replies: 3 comments 1 reply
-
API will be dealt with when the basic announce and scrape system works on the new core I'm rewriting now. |
Beta Was this translation helpful? Give feedback.
-
I was about to open an issue with the sames things, when i saw this feature request. |
Beta Was this translation helpful? Give feedback.
-
Hi @dev1z, I'm working on the roadmap. I will create a new discussion for each feature so we can include and track them separately. |
Beta Was this translation helpful? Give feedback.
-
@Power2All, @WarmBeer Here are some ideas to improve tracker usability which I have in mind. Would like to know if this is out of scope or it is possible to be added without hurting performance.
3.1.
GET /api/peers/:peer_id
- Return all peers with selectedpeer_id
and include info_hash + peers stats for easier data manipulation.3.2.
GET /api/peers/:ip
- Return all peers with selectedip
and include info_hash + peers stats for easier data manipulation.3.3.
GET /api/peers/:priv_key
- Return all peers with selectedpriv_key
and include info_hash + peers stats for easier data manipulation.3.4.
GET /api/key_status/:priv_key
- Check ifpriv_key
is used by multiple IP addresses and returnnumber | false
to check if someone is sharing keyip
andport
from peers or renameip
to beip_addr = ip:port
and include separateip
+port
fields.Those are current ideas to make private tracker more advanced and easier to use.
Beta Was this translation helpful? Give feedback.
All reactions