Longwave fails to load with Firefox Enhanced Tracking Protection strict mode

[mavit]

If Firefox's Enhanced Tracking Protection is configured to strict mode, trying to join a Longwave game via rocketcrab results in a blank page. The following messages appear in the Web Console:

The resource at “https://www.google-analytics.com/analytics.js” was blocked because content blocking is enabled. ejqc
Cookie “lastPartyState” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite [code]-5e47e408fd1e7f0d8408.js:1:127082
Uncaught FirebaseError: Analytics: Cookies are not enabled in this browser environment. Analytics requires cookies to be enabled. (analytics/cookies-not-enabled).
    t errors.ts:92
    create errors.ts:128
    Ee factory.ts:164
    <anonymous> index.ts:64
    getOrInitializeService provider.ts:194
    getImmediate provider.ts:95
    _getService firebaseApp.ts:127
    f firebaseNamespaceCore.ts:228
    d firebaseNamespaceCore.ts:209
    221 index.tsx:16
    l rocketcrab-58dfaf8f4c77b5e9:1
    107 main.6c897f8b.chunk.js:1
    l rocketcrab-58dfaf8f4c77b5e9:1
    t rocketcrab-58dfaf8f4c77b5e9:1
    r rocketcrab-58dfaf8f4c77b5e9:1
    <anonymous> main.6c897f8b.chunk.js:1
errors.ts:92:4
Partitioned cookie or storage access was provided to “<URL>” because it is loaded in the third-party context and storage partitioning is enabled. 2
Partitioned cookie or storage access was provided to “https://longwave.web.app/rocketcrab-58dfaf8f4c77b5e9?rocketcrab=true&name=ssss&ishost=false” because it is loaded in the third-party context and storage partitioning is enabled.
Partitioned cookie or storage access was provided to “https://longwave.web.app/rocketcrab-58dfaf8f4c77b5e9?rocketcrab=true&name=ssss&ishost=false” because it is loaded in the third-party context and storage partitioning is enabled. 7

Enhanced Tracking Protection can be disabled per-site, but the user likely won't realise that this is the cause, so won't know to try that.