I think that there's a difference between running a mirror of everything that removes ad income, and quoting a tweet with original links from your own cache.

The substack thing is a special case when substack started to compete with X directly. That was a whole spat. To my knowledge, today, if you put a substack link on X your post it still gets automatically deboosted.

https://github.com/zedeus/nitter

I was about to experiment with a custom nitter embed and I just found out that nitter got a cease and desist from X. Last week they updated the `README` saying that the nitter project could continue but the repo got archived a couple of days ago ...

Also TIL that you can only publish screenshots of tweets on Substack.

> we pay for X's api

In that case...

![](https://m.stacker.news/156557)

optimism

njump is injecting cloudflare trackers on the embed:

That one can probably be handled with a local caching ws client instead of the 3rd party one.

Could snap an image and serve that though.

Would probably have to snap nitter - although we pay for X's api for posting to the 

 account so we might be able to just cache the data and render it ourselves.

Stacker Saloon

saloon

> njump is injecting cloudflare trackers on the embed:

ugh.

> That one can probably be handled with a local caching ws client instead of the 3rd party one.

That's what I've been wanting to do.

> Could snap an image and serve that though.

Would probably have to snap nitter - although we pay for X's api for posting to the `stacker_news` account so we might be able to just cache the data and render it ourselves.