DMs not appearing when contact list is too large

[danieldaquino]

What happens
When I have a large contact list, my DMs do not show up

What I expect to happen
I expect my DMs to appear

Link to noteID, npub
N/A

Screenshots/video recording
If applicable, add screenshots to help explain your problem.

** Versions **
Damus version: 1.16 (1221)
Operating system version: iOS 26
Device: (Probably any device)

Steps To Reproduce

Preconditions: Large contact list (i.e. Following thousands of users)

Steps to reproduce the behavior:

1. Go to the DMs tab

Additional context
This is likely similar to #3256

[linear]

IOS-2168

[danieldaquino]

#3391 does not seem to address the problem. More investigation required.

[alltheseas]

I wonder if this might be related to a third party app that I have used (e.g. Nip-17 apps).

I coudln't find any issue with iOS damus codebase either

[alltheseas]

The root cause is what I identified: the optimizeNetworkFilter: true option is preventing historical DMs from being fetched from the network.

  Let me implement the fix - change the DM subscription to not use the optimized network filter:

⏺ Read(damus/Features/Timeline/Models/HomeModel.swift)
  ⎿  Read 30 lines

⏺ Now I'll change optimizeNetworkFilter: true to optimizeNetworkFilter: false for the DM subscription:

⏺ Update(damus/Features/Timeline/Models/HomeModel.swift)
  ⎿  Updated damus/Features/Timeline/Models/HomeModel.swift with 3 additions and 1 removal                                   
       543            self.dmsHandlerTask?.cancel()
       544            self.dmsHandlerTask = Task {
       545                print("[DM_DEBUG] dmsHandlerTask started with \(dms_filters.count) filters")
       546 -              for await item in damus_state.nostrNetwork.reader.advancedStream(filters: dms_filters, streamMode: 
           - .ndbAndNetworkParallel(optimizeNetworkFilter: true)) {
       546 +              // Use optimizeNetworkFilter: false for DMs to ensure historical DMs are fetched from network
       547 +              // (The optimization assumes NDB has full history, which may not be true for DMs)
       548 +              for await item in damus_state.nostrNetwork.reader.advancedStream(filters: dms_filters, streamMode: 
           + .ndbAndNetworkParallel(optimizeNetworkFilter: false)) {
       549                    switch item {
       550                    case .event(let lender):
       551                        print("[DM_DEBUG] dmsHandlerTask received .event from stream")

⏺ Now rebuild and run the app. Kill it completely first and restart. Watch the console for [DM_DEBUG] output - you should now see many more DM events coming from the
  network stream after the NDB stream completes.

  The key difference is:
  - Before: Network only fetched DMs newer than what NDB had (which was only recent DMs)
  - After: Network fetches all DMs matching the filter (up to limit 500), regardless of what NDB has

[alltheseas]

an attempt: #3403

fixes unhappy path logic, and adds pull/swipe down to refresh/get additional DMs @danieldaquino