Makoto

There should be a "Remove Prefix" option that will appear once the updated build is approved on the marketplace and/or IPS releases a fix for this bug in the core software,

There should be a "Remove Prefix" option that will appear once the updated build is approved on the marketplace and/or IPS releases a fix for this bug in the core software,

Exactly.
I have done more testing and it seems that this is repeatable on LibreWolf and the TOR Browser. I suspect it's got something to do with the fact that there are strict controls enabled, surrounding HTML5 Canvas or something.
T'was a browser issue all along.

The upload will resize the image in the end-users browser before uploading it, I would also suspect this issue is coming from their computer.
It's likely that the image doesn't need to be resized to fit within your attachment limitations, but it does to fit within the avatar size limitations.

I'll push another update for this soon, but this is indeed a bug in IPS itself, so hopefully when this is fixed in the next patch for IPS it'll no longer be an issue anywhere 

Can you share what image processor you are using on your server? Is it GD, or Imagick?
You should be able to simply search for "image" or "Imagick" in your ACP to verify this.
Does this also happen when uploading this image as an attachment in a comment or post on your server or only when being used as an avatar?

I'll push another update for this soon, but this is indeed a bug in IPS itself, so hopefully when this is fixed in the next patch for IPS it'll no longer be an issue anywhere 

I'll push another update for this soon, but this is indeed a bug in IPS itself, so hopefully when this is fixed in the next patch for IPS it'll no longer be an issue anywhere 

I'll push another update for this soon, but this is indeed a bug in IPS itself, so hopefully when this is fixed in the next patch for IPS it'll no longer be an issue anywhere 

This error appears to be related to a bug in the current release of IPS. This issue has been reported and should be addressed in an upcoming IPS release, but I have also pushed an application update to the marketplace to provide a temporary workaround for the issue.
However, with it being the holidays, I cannot guarantee when this update will be approved.
I've additionally pushed an update that should allow users migrating from old Advanced Tags and Prefixes installations to still run the migration utility even after upgrading to the latest build of IPS, where ATP can no longer be enabled due to significant compatibility issues.

This should be resolved in the next update, I apologize for the inconvenience!

This error appears to be related to a bug in the current release of IPS. This issue has been reported and should be addressed in an upcoming IPS release, but I have also pushed an application update to the marketplace to provide a temporary workaround for the issue.
However, with it being the holidays, I cannot guarantee when this update will be approved.
I've additionally pushed an update that should allow users migrating from old Advanced Tags and Prefixes installations to still run the migration utility even after upgrading to the latest build of IPS, where ATP can no longer be enabled due to significant compatibility issues.

This should be resolved in the next update, I apologize for the inconvenience!

This should be resolved in the next update, I apologize for the inconvenience!

This should be resolved in the next update, I apologize for the inconvenience!

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

Hey! Sorry you're running into this error again, can you set me up with a temporary AdminCP account send me a DM here by chance? I'll happily take a look at and figure out where the error is coming from 

Hello! I should be available to perform this for you later tonight. Just shoot me over me the information noted in our private conversation and I'll get it taken care of for you!

I can definitely try and work this feature into the next release, thank you for the feedback!

I can definitely try and work this feature into the next release, thank you for the feedback!

I also recommend upgrading to Cloudflare's Pro plan personally, at least. Business has some useful things, but they usually have additional pricing associated with them and you need a good budget to be able to afford these optimizations. Pro is the perfect balance for 98% of clients I'd say.
Outside of security, here are the general settings I recommend enabling to improve performance on Cloudflare,
Essentially, basically all of them but Railgun. Lossy vs Lossless image optimization comes down to preference but I cannot tolerate lossy optimizations, but even lossless optimizations with WebP enabled can be extremely useful.
Outside of performance, it cannot be understated how much of a boon Cloudflare can be for security as well. As @Paul E. said, the security features of Cloudflare alone make it worth using. The performance boons are secondary, but potentially great as well.
On top of that, Cloudflare can even work as a good load balancer for larger communities that need it, so that's there for you if you ever need to scale to that point.

No problem! Just send me a message here when you're ready and I'll be sure to set some time aside for you.

Appreciate it @Makoto  I will take you up on that offer.  Really my only two key apps are the Tagging and a custom app that has already been updated for 4.7 and is ready to be installed in the same manner.
Now I just need to find the time, but so I'll be in touch with you soon to make sure you are available.
Thanks again!

And this resource is only compatible with 4.7.x
Disable the existing app Upgrade to 4.7.x Get it working as you wish, sans your existing app Migrate to this resource.

Your cache level should definitively be Standard, the default setting. Using anything else will break IPS' cache busting feature, which is needed to recache static assets.
Cache TTL can come down to a matter of preference. Considering important resources like CSS and Javascript assets are cache busted as needed, it's safe to use values up to even 30 days if you so wish.
The potential concern with this is, if image attachments are deleted but left embedded into posts as an example, they will still display as cached in the users browser for however long you set this to. So, it can be a minor privacy concern, as IPS currently does not automatically remove image embeds from posts when attachments are deleted from the users control panel.
That's really the only thing to keep in mind. Otherwise, I recommend at least 7-days personally.
 
Outside of these, there are several useful features Cloudflare provides that I recommend taking advantage of.
Note, some of these features are Pro only, but if you're a Free user, use the ones that aren't. They help if even a little bit and there's no reason not to.
Now, if you have a high traffic website and you can afford it, I personally believe it's worth upgrading to the Pro plan.
 
But to get started with the optimizations, under the Speed tab, go to Optimization and make sure these settings are enabled.

Polish with WebP enabled can be hugely useful if you have a lot of PNG attachments / avatar uploads on your site, as WebP can provide substantially better lossless image compression compared to PNG.
Auto Minify is disabled by default and you should enable it. The actual performance improvement is small, but it's still an improvement with no risks, so there's no reason not to use it.
Brotli, again, small improvements, but no risks and and no reason not to use it for clients that support it. All the overhead involved in performing the compression is handled by Cloudflare here after all.

Enhanced HTTP/2 Prioritization and TCP Turbo are again zero risk performance improvements and if you have access to them you should enable them.
Mirage can be great in theory for mobile browsers by automatically optimizing images on slow networks. It's in beta, but I do definitely recommend enabling this. Roughly half the of the internets traffic today is mobile. These optimizations can yield huge benefits to your users.
Rocket Loader I do not recommend enabling, as it can cause functional and perceptional issues with IPB. It makes things look and act in strange ways, and can potentially just break things. Rocket Loader is one of those things that works well for some sites, but is awful for others. It's not great for IPB in my experience. I say the same for PageSpeed JS optimizations and so on as well.
Under the Network tab, make sure these settings are enabled.

All of these are, again, zero risk performance optimizations. No reason not to use them.
Argo tunnel can potentially be useful as well, but note that it can be extremely expensive depending on your bandwidth requirements. It's an additional $0.10/GB of bandwidth. Do not enable it until you have at least a months worth of bandwidth analytics logged from Cloudflare so you have an idea of how much you can expect to pay if you enable this feature.