Be less aggressive in event size

Author: dcadenas

strfry/config/strfry.conf

@@ -41,7 +41,7 @@ relay {
     }
 
     # Maximum accepted incoming websocket frame size (should be larger than max event and yesstr msg) (restart required)
-    maxWebsocketPayloadSize = 131072
+    maxWebsocketPayloadSize = 262144
 
     # Websocket-level PING message frequency (should be less than any reverse proxy idle timeouts) (restart required)
     autoPingSeconds = 55
@@ -97,10 +97,7 @@ relay {
 
         # reqMonitor threads: Handle filtering of new events (restart required)
         reqMonitor = 3
-
-        # yesstr threads: Experimental yesstr protocol (restart required)
-        yesstr = 1
-    }
+   }
 
     negentropy {
         # Support negentropy protocol messages
@@ -112,15 +109,16 @@ relay {
 }
 
 events {
-    # Maximum size of normalised JSON, in bytes One of the users we found was
+    # One of the users we found was
     # following 2546 users, and the JSON for that was 190k
     # https://primal.net/p/npub1nlch0l8fj86x4ew2f5kxdn4q3vwmprkz0v7hsm9vcry62xee683qmqq7ay
     # Explore the followers DB periodically to find the largest user, compare
     # that with other services and check if the limits are still reasonable
     # If you change this, ensure it aligns to events relay filters:
     # https://github.com/planetary-social/nos-event-service/blob/e7aacd5d402f9cd8be8aee7ad64e3ed211357f31/service/app/handler_process_saved_event.go#L21-L26
 
-    maxEventSize = 262144
+    # Maximum size of normalised JSON, in bytes
+    maxEventSize = 196608
 
     # Events newer than this will be rejected
     rejectEventsNewerThanSeconds = 900