[breakthesystem]

Thank you for the encouraging words :)

Do you have specific improvement suggestions for copy, or should I just get some people who are good with this and ask them for help?

The all users thing is a nice idea. I'll have to think a bit about how it implement this.

[CodeWriter23]

Two things. In response to your request for suggestions, maybe a little more explanation about how it works. For example, does my code have to manage the dispatch to the "flavor"? Or is this in the client-side ablator libraries.

Second, this is a feature question or suggestion. Does the client side library track exceptions or have a way to report errors in a particular "flavor"? Or how does one decide to increase the roll out coverage of a new feature?

[breakthesystem]

Thanks, I'll clear that up in the copy! But in short, the ablator server decides which user gets whic flavor. Right now, this happens randomly, but I'm thinking of adding more rules in the future.

Exception tracking is not built in, but you could use something like sentry, and send the flavor value as metadata.

[encoderer]

For copy.. an example

"Ablator is a Service that enables you to roll out functionalities in a controlled way, and perform good A/B testing."

To: Ablator enables you to roll out features in a controlled way and measure their impact.

I'm sure this can be improved and once you gain traffic you can use your own service to optimize it, but I like to use the language my audience uses (features v functionalities) and strip out unnecessary parts

[breakthesystem]

Good example! I'll definitely work some more on that

[encoderer]

I don't mean get all flags for all users -- I mean your API should return the status of all features for a given user.

[breakthesystem]

Yes! The challenge is, I feel like it'd be a preferable to return all fearures for a given user within an Organisation, as opposed to all features, period. I don't know why I feel that way yet... maybe a security risks? Guess a username, find out about a new secret feature from some Organisation using ablator.

[encoderer]

Surely you have an API key?

[breakthesystem]

Not right now, since the functionality ID is just as effectively. But switching to API keys is probably the way to go, and I'll do some work on that over the next days.

Btw, I created an issue for that at https://github.com/ablator/ablator/issues/95