probably the worst twitter frontend ever created
Warning
Twitter has seemingly removed the SSR endpoint from Jetfuel (https://jf.x.com/ssr/). Google still has one search result in its index, but it doesn't seem to be publicly accessible. I'm going to be open-sourcing & archiving this project so it's discoverable through GitHub's code search. This is one of my primary motivations for open-sourcing my own stuff when possible: GitHub's code search has helped me a lot when writing code for many libraries/APIs I haven't been familiar with.
For anyone interested, here's how this frontend looked like when it worked: profile pages, posts
$ pnpm i
$ pnpm run dev
I haven't really figured this part out yet. It's probably possible using workerd, but the public directory not being served through the worker makes this harder, as workerd does not support static assets AFAIK.
it doesn't use twitter's official api, nor any of their client endpoints. instead it does requests to their jetfuel service, https://jf.x.com. I don't know exactly what it's used for, however I found it by sending an Instagram link to a friend of mine. It had a rendered image of the tweet embedded, and I wanted to know what endpoint produced it.
Simply by searching for site:jf.x.com on Google to see if they had indexed any other endpoints, I found https://jf.x.com/ssr/, which looks to be an SSR version of Twitter for search engines? It allows you to search, view profiles and their recent tweets (not just the "top tweets"), which is more than the normal logged-out experience provides you. So I decided to write a really bad frontend on top of it.
Most of the HTML is just proxied from that site - some attributes are stripped, but most of the styling is done through rather painful css selectors. Is doing it like this a good idea? Hell no.