@andypiper thanks for the response.
It’s my understanding the workaround wouldn’t work for my use case where tweets are going to be organically submitted by the Twitter user typing in the direct URL to the meh.com homepage. I would need the Twitter user to submit their tweet using a unique, cache-busting query parameter.
I guess that would work if the entire Meh.com community coordinated amongst themselves to make sure no one else has used that query parameter before. “Hey, has anyone used ?twitter-cache=229987632 yet? No? Ok, great, it’s mine. Hands off!” But I don’t see that happening.