pull down to refresh

ah, yeah, any postprocessing of links to insert referrals and other data makes sense.

Yeah, that's what the article is basically tracking. I.e. what Goog does on search and GPT on references in chats. Twitter and FB have been doing it forever too.

But we can go a step further. With a local LLM (or a remote one but that isn't incentive-compatible with privacy, and privacy is a rapidly growing concern all over the world, especially since the data leaks just keep on punching us all in the face) I don't really need to open my browser.

The first LLM-driven app I wrote wasn't just leeching an article into cache for the LLM to view, it was also normalizing the view for me. So I could stay in-app, no outside traffic directed by me other than to feed the LLM, let it summarize, cache the article, and then I view it from cache, in a bespoke format optimized for my pleasure (dark mode bliss) no ads, no bullshit. And if the site got smart with my "Hello I am google chrome on windows" ingestion script, and blocks it with a captcha or an edgesuite list entry, renewing a tor circuit takes 2 seconds.

reply