Skip Navigation
8 comments
  • They actually did try to optimize it a bit in v5.6.1, but the person that found the exploit was on the older unoptimized version v5.6.0.

8 comments