Perhaps they should pay an extra bounty every time they screw up the fix as an incentive 
https://twitter.com/msftsecresponse/status/1413166936133754882 …
-
... and why not pay bounties to people in the infosec community (
@jonasLyk,@cube0x0 and@gentilkiwi to name a few) that poke around and retest patches to see what breaks, helping Microsoft customers to get a better understanding of the potential mitigations and residual risk.
they do kinda pay bounties, the thing is though its more work and stress to submit the stuff then doing it. The amount of BS having to go through just dosnt make it worth the max of 2000$ . Example:https://twitter.com/jonasLyk/status/1405025400972005380 …
-
-
But also being asked to close submission and resubmit for then getting it denied because new submission date is after the junction folder rule change. If there is any way that there even is remotely hint of it being not bounty eligable they will try...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.