bfarber

The e-mail banner ads. A simple feature, but considering the thousands notifications emails going out, such a huge potential for conversions. 

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

I'm 35 🙂 

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

The members REST API endpoint specifically (this does not apply to other endpoints), allows you to set undefined member properties through the rawProperties request parameter.
&rawProperties[member_points]=100  

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

Makes sense - we can take a look at that before 4.4 is released.
Yes (although realistically if you are using Sparkpost, you may be able to glean more advanced analytics through their control panel).

There's some nice ideas here in the comments, and I'll try to take note of them for future releases, but please also remember if you have any requests for changes in the software you're always welcome to post in our feedback area as well (for those who may not have). 🙂 

This was already implemented for 4.3 🙂
 
 

You can use the /gallery/images endpoint for this, it accepts the category as parameter
* @apiparam string categories Comma-delimited list of category IDs (will also include images in albums in those categories)  
And the gallery-image apiresponse contains already what you suggested.
* @apiresponse object images URLs to where the images are stored. Keys are 'original', 'large', and 'small', and values are URLs to the corresponding images  

There's some nice ideas here in the comments, and I'll try to take note of them for future releases, but please also remember if you have any requests for changes in the software you're always welcome to post in our feedback area as well (for those who may not have). 🙂 

This is a theme setting that you can toggle at will without having to make any changes (in the currently released version).

This blog entry details (and/or touches on) at a high-level some of the changes made in 4.4 to improve performance. 
There will always be other areas that can be improved. There are always new test suites that can be tested against. Technology is constantly changing, both on the backend and in the user agent. If something was not mentioned in the blog entry, chances are it hasn't been changed. That doesn't mean it isn't something we should look at, it just means we haven't yet due to many reasons (time is one factor, but also sometimes changing an approach, such as how plugins are handled, is not a simple thing to do). I recommend posting suggestions of other areas you would like for us to look at in the appropriate feedback forum, so when we are planning 4.4.1 or 4.5 or 5.0 or any other future version, we can easily reference those ideas. Posting your suggestions here in blog entry comments will, unfortunately, likely result in those ideas being lost and forgotten.

This is absolutely no longer the recommended approach with HTTP/2 becoming mainstream, just FYI. Naturally there's always a balance, but I would recommend reading up some more on best ways to handle CSS/Javascript with HTTP/2 to learn more.

From the point of view of managing subscriptions. So, the ability to disable renewals, upgrade/downgrade.
It would be awesome to be able to sell a product/subscription and manage them using the API.

This blog entry details (and/or touches on) at a high-level some of the changes made in 4.4 to improve performance. 
There will always be other areas that can be improved. There are always new test suites that can be tested against. Technology is constantly changing, both on the backend and in the user agent. If something was not mentioned in the blog entry, chances are it hasn't been changed. That doesn't mean it isn't something we should look at, it just means we haven't yet due to many reasons (time is one factor, but also sometimes changing an approach, such as how plugins are handled, is not a simple thing to do). I recommend posting suggestions of other areas you would like for us to look at in the appropriate feedback forum, so when we are planning 4.4.1 or 4.5 or 5.0 or any other future version, we can easily reference those ideas. Posting your suggestions here in blog entry comments will, unfortunately, likely result in those ideas being lost and forgotten.

This is absolutely no longer the recommended approach with HTTP/2 becoming mainstream, just FYI. Naturally there's always a balance, but I would recommend reading up some more on best ways to handle CSS/Javascript with HTTP/2 to learn more.

This is a theme setting that you can toggle at will without having to make any changes (in the currently released version).

This is absolutely no longer the recommended approach with HTTP/2 becoming mainstream, just FYI. Naturally there's always a balance, but I would recommend reading up some more on best ways to handle CSS/Javascript with HTTP/2 to learn more.

This is absolutely no longer the recommended approach with HTTP/2 becoming mainstream, just FYI. Naturally there's always a balance, but I would recommend reading up some more on best ways to handle CSS/Javascript with HTTP/2 to learn more.