Comment by hmason

It's actually because Twitter rate limits the oembed endpoint by IP, so the app caches the oembed codes and uses those if it gets limited. I've been meaning to flip that bit to the client but haven't gotten around to it yet.