I am a Product Manager on the Kinja team. We recently learned that our Commerce Insets are being blocked by EasyList. Our Commerce Insets generally follow a paragraph that is written by the editorial team at TheInventory.com, as part of a recommendation or a review. They are a visual way for us to provide additional context on a product to our readers, such as price, and how many of our readers have already purchased the item. This "social proof" is especially useful for building trust in our recommendation.
An example of an inset can be found here:
Code: Select all
The kinja team is dedicated to creating a good experience for our readers, and we believe these insets add valuable information. We also have A/B tested these units against normal text links and have seen that users engage more with these designs than a text link.
If there are any concerns with how these insets are behaving, please let me know! Otherwise, please remove
##.commerce-insetfrom https://github.com/easylist/easylist/bl ... txt#L20071 and https://github.com/easylist/easylist/bl ... e.txt#L457