Feeds on new web3 apps can feel a little stagnant, creating the impression that there's "not much to see" and leading to user churn

There are two features we've built internally that help solve this:

1. feed freshness - ensures users see casts they haven’t viewed or interacted with before

2. impression count - lets you define how many items returned by the API are marked as “seen” for the current user. so for example the top 5 items in the feed will not be returned no matter if user has interacted with them or not