Hi,

EasySocial's Comments system and Komento's system is entirely different.

EasySocial's comment system is meant to be used as a simple straight forward comment on stream items (and yes it is possible to integrate it with other elements).

Komento on the other hand, is meant to be used for independent large elements such as product, blog post, article, events and so on, and it is meant to be used as a large scale commenting solution.

Jason Rey wrote:

and yes it is possible to integrate it with other elements).

does this mean, i could use easysocial for commenting on articles or other components?

Hi,

Yes based on our API it is possible but it depends if there are developer doing this.

Internally we will leave the EasySocial comments as is, and Komento will be the commenting solution.

Jason Rey wrote:
Internally we will leave the EasySocial comments as is, and Komento will be the commenting solution.

I understand and respect this choice but in that case, are you working on an option to replace EasySocial commenting system with Komento? Because, as Mike and Josep, I'd like to see my users commenting experience being consistent! So I'd like to choose between one of these and stick to it.

Yep, as Sebastien says, main point in using easysocial ones is promote user participation and community relation through easysocial, but homogeneity in comments is first :P

Hi,

Sorry but no because Komento doesn't serve that purpose and EasySocial's comments is not meant to be used as how Komento is used.

Dear Jason,

I don't understand your point… How are Komento and EasySocial's commenting system not serving the same purpose. I guess Komento is not a discussion solution as EasyDiscuss is, its purpose is just to allow people to react on other items (stories, pics, whatever Komento is interacting with).

How Komento used integrated with HWDMediaShare or JEvents is different of EasySocial's commenting system on ES Videos and Pages (when available)?

I get that Komento can do much more than ES's commenting system. However, consistency is very important because users don't want to bother with different behavior (or look and feel) for the same action (commenting) in two location on the same site, unless there's a goo reason.

See J3.2, that's why JUX team worked so hard on consistency… so to ease JUX.

(I did a long message, please don't miss my point: I don't say you have to do this, I just say I don't get it when you say it's not meant to be)

Hi,

Perhaps let me put it this way.

We usually strive to write our codes in a way that it is "independent" enough that it can standalone by it self as much as possible.

This is the case for ES comments, and hence ES comments can be integrated independently if a developer were to call ES comments code.

Although the codes are written to be API based, and hence the ability for it to become "integrate-able" with other elements, it is not intended to replace what Komento does.

Having comments in a "stream" and having comments in an article/blog/event/product/etc, is slightly different in our point of view. Although technically they are all just an "entity", but the purpose of using which comments under which case is actually different.

Think of it this way, ES comments is simple, and can be brought out to integrate with other elements due to its simplicity, but Komento is not meant be stripped down to use with as "stream comments", as that will just clutter up the dashboard in EasySocial, making its stream item looks bloated.

That said, the counter argument is to have the option to strip down Komento so that it can work in both advance and simple mode, and we do have plans in the future to head towards this direction. As much as we would like to achieve this, we are only from a really small team, handling a few huge components on our hands (while juggling support at the same time), we can only do so much right now.

I hope you understand.

Hi,

Thanks for your answer. This I understand perfectly. And I know you're a small team and have a lot of work… which you achieve greatly, by the way!

Our point was not to ask this, right now, but more to get an idea of where you're heading.

In fact, I don't think it is a matter of options a weight, we meant that (correct me Josep if I'm wrong). Our wish is to see one day (not necessarily tomorrow allow me to stress this once more! ) this :

- User A comment an article
- User A comment a status
- User goes to his "My comments" page/app/whatever on his profile and see both his comments. (maybe that can be a "My comments" page which regroups my "comments" apps: Komento, ES Comment, Easydiscuss, 3rd party…)

and

- User A publish an article
- Publication is on the stream
- Whether this stream item is not commentable, whether it is but comments are united between stream and article page (even if comment form is different and display options too)

Thanks for your patience, I hope you don't take my passion for criticism because it really is not.

Hi,

No worries. We enjoy having healthy discussion with our customers. It helps us understand the requirements of our customer and it helps us build better products.

I know what you mean here and I am happy to tell you that, this is definitely in the next (perhaps a few upcoming revision) versions.

The idea here is, when a comment is posted on an article, Komento creates an EasySocial stream item. When another user posts a comment on that stream item, that comment will be synced back to the article and added in Komento.

now you're talking!!

thanks for the heads up, can't wait to see that happen.

Hi,

You're most welcome.