@potemkin_ai said in What's coming in Cloudron 9:
Unless I'm stating I've build something on my own and instead, I just rewrapped Cloudron - it's bad, yes.
This is what I'm getting at.
The bakery example is hilarious! I supposed it only could be applicable if I either don't know anything about baking, or the bakery refuses to be transparent about which brand of flour it uses, or lies and says they make their own in-house flour. Otherwise, weak. Cloudron is open about the tech it uses. Me using an open source app is so far off-base as to be useless as a comparison. Even various resellers tend to inform the customer what their tech is composed of. I won't go with any company that isn't transparent (enough). Your point was totally not made, but I understand your attempt.
Whitelabeling solves this by not adding extra terms to user facing interfaces (i.e. log in with Cloudron).
Good luck never uttering the word "Cloudron"! Look, I know there are users out there to whom no amount of explanation will help them understand the underlying tech, but I'm not talking about users, I'm talking about customers trying to decide from who to buy services from. But, I get your point about a benefit of whitelisting in your example. On the other hand, I enjoy telling people I use Cloudron in order that they too might start using it, so why would Cloudron remove that potential from a company using it in-house with 10s, 100s, of employees, some of whom might want to use it themselves on their own time for their own projects?
Anyway, thanks for the rebuttals and points everyone!
Now, let's tackle those apps which also don't allow, or make it possible, to change their own icons for our own use!
