We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
A typical Composr user will likely not have a web server capable of running Glaze or Nightshade. These tools require quite a large amount of data / RAM and a decent GPU.
I'd suggest we make some sort of AI protection / awareness documentation page and talk about Nightshade and Glaze and how to use it in conjunction with Composr rather than implementing it in Composr directly.
Or, if we can find an external SaaS API that does this, we could incorporate that in Composr.
I'd suggest we make some sort of AI protection / awareness documentation page and talk about Nightshade and Glaze and how to use it in conjunction with Composr rather than implementing it in Composr directly.
Or, if we can find an external SaaS API that does this, we could incorporate that in Composr.