Thanks for the suggestion! I’m afraid a replacement like that doesn’t fit this project, though. The whole point of this component is to embed tweets directly from X/Twitter. A third-party proxy such as fixupx doesn’t solve the underlying problems, it only adds another layer in between: one more service that can fail or change, and one more party that sees the requests. It would also rewrite the links stored in the posts themselves.
What I would actually prefer is a local copy of the tweets. That would help with load times and caching, make embeds resilient to outages, and keep an archive of the content. But it would require paid API access and a clarification of the copyright & content responsibility side, and I can’t offer either. So for now the component sticks to the direct embeds.
If someone only needs plain link previews and is fine with a proxy, a watched-word replacement can work for that, but that’s a different goal than this component’s.