COLABORATER NAME AND CHAINING STRATEGIES

[Bugspiderlee]

hey james how are yu i was wondering if u can add a feature on the burpcolaborator client were a user can add the tab name .Like when you select a cclient so that it could namable
to easy the issue of tracking call backs .As for me i relie heavily with callback oriented hacking --(owast) so iam facing a sinario way i fail to track were a specific callback has come from
as i will be having multiple ccolaborater clients letsay an email blindxss and a blend email template injection or an callback staf
so if a user could name the collaborater i think it will be easy to monitor were a callback is coming from .this might facilitate easy tesing of OWAST with custom payloads

i also wanted to ask if it is possible to chain or link my (COH)CALL BACK ORIENTED HACKING payloads with scan check builder or burpbounty manually like having a payload wich
trigers a callback being setup in scan check builder like everytime i run a scan my scan rule or payload in burp bounty could have a fresh collaborater payload whenever i run a scan
and also to be detected buy burp scaner results that this callback have been trigered bythis scan rule in burpbounty
if this is pissible please will yu make a video show a step by step on how you can do that whenever yu are free please like the video yu did on advanced burp tricks for bounty hunters
and also how you can turnoff other scan checks and use burpbounty scan checks on the new version of burp it seems advanced to me i feel like if i do it on my own i will miss things
no do other pentesters
This would change the way i approach things