tracker URL

[ariesjj]

great work bro...what is the tracker url?

[Wiilf]

Yeah what is the URL. Everything is fine on user side except no clarity on this step when creating a torrent.

[Wiilf]

Yeah what is the URL. Everything is fine on user side except no clarity on this step when creating a torrent.

[Wiilf]

Yeah what is the URL. Everything is fine on user side except no clarity on this step when creating a torrent.

[Wiilf]

Yeah what is the URL. Everything is fine on user side except no clarity on this step when creating a torrent.

[SuprDewd]

Sorry, maybe this should be made more clear in the upload interface. But in reality it doesn't matter at all what tracker/announce URL you use; it is automatically populated in download.php when other users download your torrent file.

[Wiilf]

Yes all is well. I have figured it out. For those curious, download will reinsert a new announce URL, whether created torrent has announce or is blank. From there username and torrent_id is matched to peer table and the rest is sorted.

I'll be modifying this so it retrieves only passkey, allowing JOINs to retrieve other fields away from _GET in client. Thanks again! This is a great script and I plugged it in very nicely.

Working with user dB session class, mass-uploader and more. Thank you for no UI, it made back-porting extremely easy.

[SuprDewd]

Hey, do you mind dropping me an email about your plans at suprdewd@gmail.com ?

…

On Thu, Aug 20, 2020, 11:14 Wiilf ***@***.***> wrote: Yes all is well. I have figured it out. For those curious, download will reinsert a new announce URL, whether created torrent has announce or is blank. From there username and torrent_id is matched to peer table and the rest is sorted. I'll be modifying this so it retrieves only passkey, allowing JOINs to retrieve other fields away from _GET in client. Thanks again! This is a great script and I plugged it in very nicely. Working with user dB session class, mass-uploader and more. Thank you for no UI, it made back-porting extremely easy. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABNVZMARFRS7IU52YAVXV3SBUASDANCNFSM4LARZU7A> .