You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do you think about adding a 'spam' attribute to the CheckContent object, that would return 0, 1 or 2, to model the Mollom API?
It seems like for some cases it would be simpler to represent the result as one variable with 3 values, then 3 booleans. (Or, perhaps just name 'spam' and set it to 0, 1 or 2 directly model the Mollom API).
An example use-case might be passing the result back to JavaScript, where you can't pass the "$check" object.
(I first thought of naming this 'classification' and setting the values to 'spam', 'ham' or 'unsure'. Those names are clearer than the Mollom API, but perhaps it's best to consistent with it?)
The text was updated successfully, but these errors were encountered:
Michael,
What do you think about adding a 'spam' attribute to the CheckContent object, that would return 0, 1 or 2, to model the Mollom API?
It seems like for some cases it would be simpler to represent the result as one variable with 3 values, then 3 booleans. (Or, perhaps just name 'spam' and set it to 0, 1 or 2 directly model the Mollom API).
An example use-case might be passing the result back to JavaScript, where you can't pass the "$check" object.
(I first thought of naming this 'classification' and setting the values to 'spam', 'ham' or 'unsure'. Those names are clearer than the Mollom API, but perhaps it's best to consistent with it?)
The text was updated successfully, but these errors were encountered: