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.
#5720 - composr_homesite: Rename addon and move website_specific contents
The debranding isn't intended for people to fork Composr and not have people know that's where it came from. It's intended for web agencies to be able to roll out Composr to naive clients who want to be able to add content, and the agency just wants to market/explain it as their own system.
I don't see utility in removing references Composr from our own code, and I do see cost. Regardless, our license doesn't even allow forking Composr without giving us credit for having created the system in the first place.
I don't see utility in removing references Composr from our own code, and I do see cost. Regardless, our license doesn't even allow forking Composr without giving us credit for having created the system in the first place.