The tweet mentions the challenge of bypassing a WAF that blocks the use of equal sign (=) and <script> tags for XSS attacks. The user also tried URL encoding without success. This indicates a complex filtering mechanism in place. Further analysis and testing are required to find a suitable payload for XSS in this specific scenario.
For more details, check out the original tweet here: