@arch I'm confused, I thought birdsite changed the API and disabled the guest tokens that were needed to have any automation read any of it, so Nitter was a complete dead end?
Or by "caching a post I've seen" are you doing some manual proxying/browser/other shenanigans?
The goal for forking is honestly just caching a post I've seen and letting me write a second service that reads that cache and renders it. So if I see a post, I can just copy paste the link without manually changing the URL, and it will render for other people publically without exposing the entire Nitter instance.
Add comment