We were having some issues with the current way of storing data for the user facing widget (the one you use on your product) related to local storage.  Some logout implementations usually delete all local storage, therefore erasing all the widget data.  This caused that each time a user logged out and the logged in it would appear as if it hasn't seen any of the updates, therefore creating confussion.

We switched to cookies to fix this issue. 

For privacy matters it only stores the id from last seen post.

We updated our CDN provider for a faster one and with edge locations all around the world.  This means that when a user loads the widget it will be sent form its closest physical location, therefore reducing loading times and latency ??

Fixed an issue that wasn't correctly displaying the number of published posts.  It was taking also in account the number of drafts.

Pushed fix that opens all posts (from the widget) in a separate window.

Fixed an issue that was preventing images from being displayed correctly on the widget.

Fixed issue that was preventing the correct image upload in a new or existing post.