Images over 5MB shouldn't be used

[sybrew]

From freshcreate's report:

We should skip/filter out images that are over 5MB in size because Twitter doesn't support these.

There's performance overhead involved, i.e., testing each subsequent file for its size isn't fast by any means, especially when the files are offloaded to a different server.

So, we'd prefer using WordPress' stored metadata. For that, WordPress needs to populate the filesize field first — see https://core.trac.wordpress.org/ticket/47459. Until then, this issue is marked as "Won't fix."

[sybrew]

From codebot's suggestion:

Allow users to specify a preferred registered size, from 'full', to anywhere below.

When such a size is no longer registered, we should default to 'full'. This can be a bit sporadic since themes define their image sizes way after plugins_loaded. Nevertheless, it'd be a welcome addition.

Alternatively, we could allow users to specify the maximum size in pixels. This will be more reliable since the image parser always asserts this value, and it goes over the registered image sizes for each image individually. Moreover, older images may not have been downsized to presently registered image sizes.

[sybrew]

A patch for filesize registration has been submitted. We might be able to implement this feature sooner than later.

See: https://core.trac.wordpress.org/ticket/49412

[sybrew]

https://core.trac.wordpress.org/ticket/49412 is merged for WP 6.0, removing the blocker.

[sybrew]

Facebook now accepts images up to 8MB, but that doesn't mean other social networks allow this. We'll stick to 5MB and add a filter for those wanting more.