Is this live yet? I tried setting something up in settings on studio though the smart feed was still blank :/
\nUPDATE oh nvm -- this is known: "It will read your signals (thumbs, hoppers, stubs, forks and quotes) to know what you have liked and engaged with. The agent is not built yet: this prompt is saved now so the Smart Feed can use it when it is."
\n\n\n\n","content_hash":"sha256:92db98521324f6dd02ac84b56a235f4512b0d69cd8790ac0ef85ddb888ad6622","media":[],"transclusions":[{"id":"3dmp10axxe7jhtc4qv78xrqwbh","version":1,"origin":"https://venkateshrao.com/blyg/","cited":{"source":"Venkatesh Rao's Blyg","author":"Venkatesh Rao","excerpt":"RFC Personal Algorithmic Reader Feed I haven’t stated this explicitly anywhere,…","url":"https://venkateshrao.com/blyg/t/3dmp10axxe7jhtc4qv78xrqwbh/","retrieved":"2026-10-19T15:57:52Z"}}],"stub_of":{"origin":"https://venkateshrao.com/blyg/","id":"3dmp10axxe7jhtc4qv78xrqwbh","version":1,"cited":{"source":"Venkatesh Rao's Blyg","author":"Venkatesh Rao","excerpt":"RFC Personal Algorithmic Reader Feed I haven’t stated this explicitly anywhere,…","url":"https://venkateshrao.com/blyg/t/3dmp10axxe7jhtc4qv78xrqwbh/","retrieved":"2026-10-19T15:57:52Z"}},"changelog":[{"version":1,"at":"2026-10-19T06:13:31Z","note":null},{"version":2,"at":"2026-10-19T06:13:35Z","note":null},{"version":3,"at":"2026-10-19T15:57:52Z","note":null}]}RFC Personal Algorithmic Reader Feed
\nI haven’t stated this explicitly anywhere, but the intent is for everyone to have their own algorithmic reader feed in their client. My initial idea for the default one to ship with studio is:
\n\n
\n- Allow main reader index to filter for all | threads | fragments
\n- Move items marked ‘ignore’ in changelog (might be a spec SHOULD convention? Spell it ignyre?) to a side tab
\n- Offer a couple of simple non-AI sort orders (newest, most recently updated)
\n- Offer an “AI key required” option to “smart filter” or “smart sort” by a default prompt in settings
\nThe default prompt could be something like “prioritize tech news and big updates on posts I interacted with before, and deprioritize updates that are just typo fixes.” This is also Jev suitable. The algorithm could just compute a numerical score to sort/filter by.
\nChangelog automation enables part of this. There’s also already a thumbs up/down signal (private likes record) that’s a natural input, though I think I haven’t made that clear in the UX. I also just realized clients need a log of posts they’ve interacted with before through hoppering, stubs or forks etc, since that’s important input to an algorithmic feed when the raw feed has versioned items.
\nThis also seems like a natural sharing artifact. People should publish their algorithmic policy itself as a thread.
\n\n