Multiplayer UX

[jsmorabito]

Backend

• [ ] Confirm receiving
• [ ] Needs an update of server side protocol to await confirmations
  • Similar setup to what happens with awaited-events in client.cljs
  • but with per connected client
    • Needs to be able to recognize reconnects
      • For now based on username send with :presence/hello

Frontend - Figma Mockups

• [x] Toolbar presence #1117 - complexity/low

• [ ] block inline presence #1365 - complexity/low

• [ ] conflicts for shared block/uid - complexity/medium

  • 2 writes to same block

    • we do want to lock blocks

    • if there is a conflict because shared block/uid, add both as siblings

      • some indication that this isn't a bug

    • edge case: backspace at start of block tries to join the block above it. merging blocks.

    • if someone creates a new child above your block, that increments your block/order by 1

      • this re-renders the block that I am editing, and resets the textarea string, caret position, and other things
      • [ ] need to persist the text and caret position, otherwise the temporary update gets erased
      • locking is not just UI, should look at surrounding context via block/uid
      • if only order or indentation is affected, we shouldn't destroy the temporary text string
  • 1 person writes, 1 person deletes
    • if we don't know where to add this block, append block to Daily Notes and as much context as possible with #[[Merge Conflict]] tag

• [ ] network - complexity/high but can be complexity/medium or complexity/low if we lower constraints

  • if disconnected/offline (reconnection logic), websocket or js event should alert us with a notification + message
    • if not typing, can navigate db
    • if typing, can continue typing on that block
      • easy solution: "Any changes you make might not be saved."
    • if spotty network, constantly disconnecting/reconnecting
      • if typing, can continue typing on that block
    • if permanent disconnect (e.g. going on an airplane)
      • easy solution: "Any changes you make might not be saved."
      • what happens when you reconnect after a long time and a lot of changes have happened?
      • what happens when you reconnect and someone deleted the entire parent context of the block you were editing?
        • 1 person writes, 1 person deletes
          • if we don't know where to add this block, append block to Daily Notes and as much context as possible with #[[Merge Conflict]] tag

• [ ] server error - complexity/low

  • throw js/alert and console.error with as much information as possible
  • tell user to share screenshot + log
  • @ or DM us on Discord!
  • remind users to opt into Sentry
    • create alerts and filters on sentry to look for these errors!!

Later

* selected blocks - maybe not yet, requires some engineering and refactoring + selecting substring within a block/string + fix existing `selected/items` API first * when a new block is rendered on the DOM that the user is not editing, show something - not yet + probably use animation package + problem: our current usage of react/reagent is messy and re-render happens in an erroneous way + can add in later enhancement PRs - presence partially addresses this because `editing/uid` of other users communicates this implicitly - one possible problem: if other users pastes in a large amount of text, this confuses the current user by changing their view - additional inline block UX - entered a block - editing a block - selecting substring within a block/string - network - on reconnect, do a smart diff to only send necessary tx-data (closer to local-first data persistence) - then show a summary of changes on the UX side of things

[tangjeff0]

This screenshot is Google Calendar showing multiple accounts' schedules side-by-side.

Long-term multiplayer UX, multiple pages side-by-side from different graphs?

[tangjeff0]

Notes from chat with @neotyk and @shanberg on potential RTC UX https://roamresearch.com/#/app/athensresearch/page/aEfAXnSHX

• when a new block is rendered on the DOM that the user is not editing, show something
• if there is a conflict with the tx because shared block/uid, add both as siblings
  • when a block is appended
• if there is a rejection because bad network, wait and show something/queue
  • when a tx is pending in the queue
• for presence, can highlight parent block as well