I think once upon a time nitter supported embedding. But even if it does now, it's a bad idea due to the rate limiting. Unless you want to set up a large caching instance specifically for people's embeds.@Twiglard would it be possible to make the media function accept twitter frontend URLs?
for example,
https://nitter.net/ChrisAvellone/status/1582058085517910023
so just detect if it ends in a /status/[0-9]{20,} and rewrite it to a twitter.com URL?
If we're writing plugins for xenforo then the more useful thing is slurping the tweet at the time of posting and embedding it directly in the post's text where the embed code was. Like substack does with shitter links.
What I'm doing personally with twitter.com, twimg, facebook and fbcdn is disable their cookie and site data permissions. But Firefox and Chrome should now have per-site containers for third-party cookies dependent upon the first-party domain, out of the box.