So you mean this one? Twitter has compressed it & it's a size that is within out constraints. It's just not very readable. Even your one on twitter is a bit long & i'd be not inclined to read the content. However we could look at changing the max optimised size to 2000 x 2000 (maintaining original aspect ratio) which would slightly enhance readability.

@Sairahcaz2k was is the aspect ratio that failed or the pixel size?
4000 x 4000 is a very huge photo, if I screenshot my entire screen it' only 3456 × 2234, this is what we've based it off. Even the ultrawide iphone 15 Pro/Pro Max camera only takes a photo 3024 × 4032. So I assume maybe you used Devtools to capture the entire page even outside of the viewport?

@MrPunyapal - I guess we could consider allowing larger, doubling it would be ok, especially now that we restrict the aspect ratio, which is really whats most important for viewability. Either way, you might find if you took an 8000 x 8000 pixel photo of text, when it's compressed to 1000 x 1000 the text might not be readable, we'd have to look into it more.

I love this! Another great example of when good programmers put their attention to detail outside of the code & come up with something beautiful! Although… now I’m hungry for pizza & it’s only 9am….

Plus we can further tweak it, by improving the feed algorithm as to what is relevant to the user, then it will reduce the amount of time the root post is seeming to appear. Either way it's a step in the right direction.

If you have not need to write any cooperative multi-tasking type operations since PHP8, such as thread pools or anything where you need fine grained control over async operations, you probably haven’t needed to consider the Fibers feature & Fiber class.

Weakmap is a lot more common. Good for storing data against an object key, which is cleaned up when the object is destructed.