Parakeet is a bit big at the moment. It needs Postgres, redis, parakeet-index, parakeet, and at least one consumer instance. It also only really works with a full network approach or big-world using a special configured relay like https://relay.feeds.blue or https://relay.parakeet.at.
Ideally, weโd have tools to allow for more fine-grained backfill control to allow for hosting an AppView for a smaller community of group of friends, still with visibility of the wider world, like many do with fedi instances.
This is a problem I've been thinking about for a while and one idea I've had involves watching for every firehose event that is either from or somehow involves users in this set, and simply not indexing other firehose events unless needed:
If done right, we'd have a pretty good view of the local network and mostly avoid issues such as incomplete threads and poor discovery on single user instances.