#FediFoxDev used a postgres query to find the most replied to toots (and thus hopefully largest threads) on this Mastodon instance

Happy to see my re-ordering algorithm for proper threading, and my rendering still handles them really well. Only the very largest thread took a bit more than a millisecond, everything else is <0.3 ms

Mastodon takes multiple seconds on the /context responses though yikes. Really happy with my stale double-rendering approach so you still get to see content almost instantly, while it's waiting for verification from the Mastodon server that the data is still up-to-date