remove relay__negentropy__maxFilterLimit for now

- this was causing problems on big DBs
- need more reliable way of enforcing limits

src/apps/relay/RelayIngester.cpp

@@ -121,7 +121,7 @@ void RelayServer::ingesterProcessNegentropy(lmdb::txn &txn, Decompressor &decomp
         if (arr.get_array().size() < 5) throw herr("negentropy query missing elements");
 
         NostrFilterGroup filter;
-        auto maxFilterLimit = cfg().relay__negentropy__maxFilterLimit;
+        auto maxFilterLimit = MAX_U64;
 
         if (arr.at(2).is_string()) {
             auto ev = lookupEventById(txn, from_hex(arr.at(2).get_string()));

src/apps/relay/golpe.yaml

@@ -94,7 +94,3 @@ config:
     desc: negentropy threads: Handle negentropy protocol messages
     default: 2
     noReload: true
-
-  - name: relay__negentropy__maxFilterLimit
-    desc: "Maximum records that can be processed per filter"
-    default: 1000000

strfry.conf

@@ -124,9 +124,4 @@ relay {
         # negentropy threads: Handle negentropy protocol messages (restart required)
         negentropy = 2
     }
-
-    negentropy {
-        # Maximum records that can be processed per filter
-        maxFilterLimit = 1000000
-    }
 }