Steven,You are absolutely right saying that almost every community component comes with default priority level 0 to support custom extensions. With livefyre integration post AEM 6.1 GA, we have a new implementation of AbstractUser via this factory - com.adobe.social.integrations.livefyre.user.impl.L...

Try to work with priority level of your extended component ( AbstractUser) as ootb components get registered first and custom component need priority level higher than ootb.Try adding this to your extended component class ----------------------------------------------------/** Priority level of the ...

You can use either of the approaches you identified  By using performBeforeActions of your custom comment social component operation extension and insert a relationship between current_user_id (as start node) and subscribed resource node (as end node) as per your required type (notification/email-su...

Sandeep,What Janice explained is true for all production usages of AEM communities as an independent module.That specific licensing requirement is for those AEM customers who have licenses for other modules (but not of AEM communities) running in production setup but want to extend their Sites/Asset...