custom feed broken w.r.t. DID filter #14

Fixed! The custom feed now properly handles DID filtering. Changes made:

1. Backfill now filters records by DID when a DID filter is active
2. Live events are also filtered by DID
3. The indexer fetches extra records (3x) when DID filtering to ensure enough results after client-side filtering

Also fixed an issue where handles with 3+ segments (like satyam2.climateai.org) were incorrectly detected as NSIDs instead of handles.

It's still not working - stuck on "Waiting for events".

Hi Adam, can you share more details to help us debug this?

1. What's the exact URL you're using? (e.g., /feed?type=custom&view=feed&dids=did:plc:...)
2. Which DID are you filtering by - your own (did:plc:ucuwh64u4r5pycnlvrqvty3j) or another one?
3. Which collections are selected in the filter bar?

This will help us understand if the issue is:

• No records exist for that DID in those collections
• The backfill isn't finding them
• Something else

We've also improved the UI to show 'No records found for this filter' instead of 'Waiting for events...' when filtering returns empty results - that should make it clearer what's happening.

OK https://www.impactindexer.org/feed?type=custom&view=feed&collections=app.gainforest.%2Corg.hypercerts.%2Capp.certified.%2Corg.impactindexer.&dids=did%3Aplc%3A24722mmp6koynnvhsgobn2qa worked although it was slow.

Thanks for confirming it works! The slowness is expected when filtering by DID - it needs to paginate through the indexer's records to find matches for that specific DID. The more collections you have selected, the more queries it needs to make in parallel.

For better performance, try selecting fewer collections if you only need certain record types.

Status update: DID filtering works but can be slow for DIDs with sparse records — the indexer GraphQL API does not support server-side DID filtering, so we paginate client-side up to 1000 records per collection. The UI now shows 'No records found for this filter' instead of getting stuck on 'Waiting for events' when filtering returns empty results. For best performance, select fewer collections when filtering by DID.