No, it was also working with the self-hosted nitter instance I was using which should have almost nothing cached. Double checked with a new tweet posted in this thread.