Under the hood
Useful2 Signal3
Organization-shared memory setup now takes credentials explicitly and re-negotiates when the endpoint changes.
What's wrong with this entry?
Anonymous. No account, no email.
What
Setup for organization-shared memory now takes credentials and storage together rather than adopting storage alone, and it throws away its cached negotiation when the API endpoint changes instead of reusing a one-time result.
Details
- First sync now performs the steps in sequence: adopt credentials, adopt storage, discard on endpoint change, then negotiate once with concurrent callers sharing the single attempt.
- Reads are still gated by the
orgMemoryReadsetting, which defaults to on; setting it to false skips them.
Evidence
orgMemoryRead
Strings lifted out of the shipped bundle, so the claim above can be checked against them.