Page 2 of 2

Re: New features

Posted: Mon Jan 29, 2018 3:11 pm
by x1admin
AndresERiveraB wrote:
Mon Jan 29, 2018 2:38 pm
x1admin wrote:
Mon Jan 29, 2018 7:47 am
CoolCanuck97 wrote:
Mon Jan 29, 2018 1:54 am
What happened to the check for patch feature? This is critical... I have quite a few "unpatched" that will now show as taking forever to patch by the site owner. :(

UPDATE: Lots of HTTP 500 errors. What's up?
eg: https://www.openbugbounty.org/reports/228340/
we don't change "check for patch"
for some reports there are no option to check for patch..
for example this has not that option.
https://www.openbugbounty.org/reports/191861/
also this one https://www.openbugbounty.org/reports/191868/

Image
191868 hmmm maybe because report already mark as fixed? =)
191861 you already request "patch check" for this reports little time ago, wait 24h

Re: New features

Posted: Mon Jan 29, 2018 5:14 pm
by AndresERiveraB
i will check the rest... but thanks for the information

Re: New features

Posted: Mon Feb 12, 2018 1:02 am
by CoolCanuck97
Not a fan of the new homepage layout. Does anyone really care about who is most recommended? I'd rather see the top PR websites at the top, etc like the old layout.

Is there a setting I can change on my account to get the better homepage version, or an alternative URL I can visit? Thanks

Re: New features

Posted: Sat Feb 17, 2018 1:22 am
by mcurietribute
vpq_wtf wrote:
Sun Jan 28, 2018 4:26 pm
x1admin wrote:
Fri Jan 26, 2018 8:38 pm
SHR00MHEAD wrote:
Fri Jan 26, 2018 8:24 pm
Seems to be an issue with Vulnerability Fixed part.

Check https://www.openbugbounty.org/reports/246794/

"30 November, -0001"
thanks fixed
Why remove a feature that *some* researchers were using?

I was using that feature every single day, now I'm going to have to go out of my way to write a script which will submit through the manual function and bypass captcha which will take me weeks.

I've received good feedback from this feature and actually, it's all I have been using for almost 5 months now.

Can you consider removing the captcha on the manual function at least?

Considering this platform works off researchers, we should be working together, not against each other, it's simply stupid for me to have to do this, so it would be nice if we could come to some agreement and not just "no sorry".

EDIT: Of course, you have switched the captcha to recaptcha now, which is almost impossible to bypass.

Can we work on some solution man?
Many of us researchers actually requested recaptcha be added.

Thank you admin for adding recaptcha.

Re: New features

Posted: Sat Feb 17, 2018 10:41 am
by vpq_wtf
mcurietribute wrote:
Sat Feb 17, 2018 1:22 am
vpq_wtf wrote:
Sun Jan 28, 2018 4:26 pm
x1admin wrote:
Fri Jan 26, 2018 8:38 pm


thanks fixed
Why remove a feature that *some* researchers were using?

I was using that feature every single day, now I'm going to have to go out of my way to write a script which will submit through the manual function and bypass captcha which will take me weeks.

I've received good feedback from this feature and actually, it's all I have been using for almost 5 months now.

Can you consider removing the captcha on the manual function at least?

Considering this platform works off researchers, we should be working together, not against each other, it's simply stupid for me to have to do this, so it would be nice if we could come to some agreement and not just "no sorry".

EDIT: Of course, you have switched the captcha to recaptcha now, which is almost impossible to bypass.

Can we work on some solution man?
Many of us researchers actually requested recaptcha be added.

Thank you admin for adding recaptcha.
Why would you request such a stupid thing?
Are you really that incompetent?

Re: New features

Posted: Sat Feb 17, 2018 6:59 pm
by mcurietribute
vpq_wtf wrote:
Sat Feb 17, 2018 10:41 am
mcurietribute wrote:
Sat Feb 17, 2018 1:22 am
vpq_wtf wrote:
Sun Jan 28, 2018 4:26 pm


Why remove a feature that *some* researchers were using?

I was using that feature every single day, now I'm going to have to go out of my way to write a script which will submit through the manual function and bypass captcha which will take me weeks.

I've received good feedback from this feature and actually, it's all I have been using for almost 5 months now.

Can you consider removing the captcha on the manual function at least?

Considering this platform works off researchers, we should be working together, not against each other, it's simply stupid for me to have to do this, so it would be nice if we could come to some agreement and not just "no sorry".

EDIT: Of course, you have switched the captcha to recaptcha now, which is almost impossible to bypass.

Can we work on some solution man?
Many of us researchers actually requested recaptcha be added.

Thank you admin for adding recaptcha.
Why would you request such a stupid thing?
Are you really that incompetent?
Are you really that incompetent?
No, some of us just know how to actually program - that's all.
we should be working together, not against each other
And coming from someone that says "we're a team" to immediately demoralizing a fellow researcher is a sign of a character flaw. I'd recommend seeking therapy.
Why would you request such a stupid thing?
It's not stupid when it makes my life easier.