Thanks for your feedback. We're aware of this issue and are working on fixing it, but we haven't found a reliable way to reproduce it yet. There are two main reasons for this problem:
The Discuss Kit blocklet is being upgraded or restarted.
We've made some improvements to this issue, but we need further confirmation and track. Please feel free to leave a comment with your feedback here if you encounter this issue again. Thanks!
Thanks for your feedback and time, we really appreciate it. We started looking into this issue two weeks ago. According to our latest bug bounty rules, known issues don't qualify for the program. Thanks for understanding. ❤
7 条回复
Thanks for your feedback. We're aware of this issue and are working on fixing it, but we haven't found a reliable way to reproduce it yet. There are two main reasons for this problem:
How can I help. It only occurred one more time after that but it was just the same, didn't screenshot it again
We've made some improvements to this issue, but we need further confirmation and track. Please feel free to leave a comment with your feedback here if you encounter this issue again. Thanks!
Thanks will do.
Sorry to disturb but since it's a valid bug maybe input bug bounty qualified tag 😁 thanks
Thanks for your feedback and time, we really appreciate it. We started looking into this issue two weeks ago. According to our latest bug bounty rules, known issues don't qualify for the program. Thanks for understanding. ❤
Alright!