bfarber

For managed clients that I've worked on I've effectively done the same. We have a tracker that lists any custom applications and plugins, and further separates them by "marketplace" (or third party) resource vs a resource we've built in-house. For anything we've built in-house, we review the code and test locally. For third party resources, we check the marketplace to see if the resource is compatible with 4.5.
That's it in a nutshell. You can then decide if you have resources that aren't compatible if you're willing to forge ahead or if you need to wait for updates.

Quickly to address this - if the thing being followed has more than NOTIFICATIONS_PER_BATCH followers (which defaults to 30), the notifications are queued and send in the background.

Even Microsoft will not support IE11 (or legacy Edge) in any way from next year, including in its own products like Teams. Other major sites like Twitter are starting to drop any support too. It won't be long until you'll struggle to use the web on IE11. Technically we have not supported it for a long time, but because we held back on modern CSS features, it still mostly worked. For 4.5, we decided now was the time to press ahead with improvements and drop support ourselves.
By dropping support, we've been able to use newer CSS features that benefit designers (and therefore site owners), simplify our theme (with more improvements to come), and we'll also be able to begin the process of modernizing our javascript.
If your community has a significant percentage of IE11 users due to your audience, you may prefer to stay on 4.4 (though that, understandably, has drawbacks too). If you're just an individual IE11 user, I would strongly suggest using a newer browser - literally any of them would be a better choice. 

There is no legitimate reason anyone or any organization should be using IE. If you have users stuck on it, that sucks, but it’s akin to having users tell you they unfortunately are stuck on 14.4k dialup and find the site loads too slowly. 
IE is dead. Let it Rest In Peace. 

It's on our radar, yes. It's not an insurmountable technical limitation, I just wanted to clarify that there was a reason this hasn't been implemented just yet.

The bug report is still open.

It is entirely possible, for what it's worth, to modify your skin template so that if the user has ignored the poster the post doesn't show up at all. Granted, it could make for some confusion (i.e. post #1, post #2, post #4) but that would only be a minor thing.

We do not have any Instagram API integration built in.

Most clients still run based on traffic. I'm uncertain on the specifics for cron-enabled accounts I'm afraid. I'm a developer and not intimately involved in the hosting setup.

This is a frustration that has irked us since 4.0. The gallery uploader for images needs to have a confirmation dialogue before it can be closed. Along the lines of 'Are you sure you want to close the uploader? All progress will be lost." It is annoying to accidentally hit escape or click outside of the box and have it close.

I didn't say Sendgrid has been around longer than SES (frankly I don't know). I was just saying we've had Sendgrid integration longer available within our software.

There is no specific schedule. We release updates when they're ready and as needed.

Hidden status is also represented in the search index, and in the tags index at least. You'll need to review those tables (core_search_index, core_tags_perms).

AdminCP > Members > Profiles
Add new custom fields and configure them to be requested on registration (or use the profile completion tool if using the quick registration mode).

Web views are supported for anything that doesn't have a native view.

Hidden status is also represented in the search index, and in the tags index at least. You'll need to review those tables (core_search_index, core_tags_perms).

Pricing has not been determined for that potential future service just yet.

Yes, we have a bug report still open about this issue

That's probably it, yes. There was a fix for Spotify in 4.5.

Another developer could recreate the application or plugin, or they may be able to adjust your existing app/plugin with the source code available to them (i.e. with FTP access to your server to work on it there).

If you wanted to create some text in the interface that you wanted to be able to translate to different languages, you can create a language string and use that instead of just embedding the text in a template. That's mostly what it comes down to.

We have an internal suggestion about this open already

Firefox say:
"To protect your security, forums.aaca.org will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window."
https://support.mozilla.org/en-US/kb/xframe-neterror-page?as=u&utm_source=inproduct

Look for the key _date_this_week in translations.

No, the page generation will be the same speed. In theory the page may load slower for the end user because the browser requests the image from the original URL and then is redirected to the new location (so two requests instead of one), but it will likely be negligible in most cases. Your alternative is to go through all the content and replace the paths instead.