So, this reflects:
- performance and reliability issue within codebrowse.
We need to address it. The proximate triggering of it was a user
mirroring the codebrowse content as far as we can tell, which isn't an
intended use-case - they have been blocked to give us breathing spac.e
So, this reflects:
- performance and reliability issue within codebrowse.
We need to address it. The proximate triggering of it was a user
mirroring the codebrowse content as far as we can tell, which isn't an
intended use-case - they have been blocked to give us breathing spac.e