couscouspie

Also note, that RAG and even vector search are more paths of the early days that didn't prove too valuable. Just let your agent search it directly and optionally create an index as a default entrypoint for common topics.

Both presented ways in looking at an RSS feed make sense and come with their own set of pros and cons. But to me it looks like it is entirely possible and the best solution to treat it as both at the same time: the feed is a stream, but you treat it as an inbox not for the items that are streamed themselves (e.g. blog entries), but as the notification that they exist. So, I will try out in the future to keep three lanes: a readlis, where you store the things you want to read, a read-it where you store the things you actually read already and the RSS-feed aggregor "inbox" where you marked things as read if you decided to either put it on the readlist or not. So the read-marker of the RSS-feed aggregor becomes a "noted-it" button.

A fourth lane that forwards interesting reads or notifications could be the building brick of a new internet, where you aggregate things from people you like or trust and index them as your personalised search engine.

That's not a physical law, but just the result of the current technological landscape.

Hardly matters. As long as von-der-Leyen remains head of commission the European Union stays devoted to the US no matter the consensus of commission, parliament, national governments or the people.

That's btw a perfect analogy what ADHD is when consuming anything, anytime.

I'm asking as I don't agree on the underlying assumption a use case was needed. I consider the value of transparency and public information for a democratic society as evident.