Liveblocks Best Practices

**Liveblocks Best Practices for a Collaborative Whiteboard App**

### 1. **Room Management**
- Always clean up unused rooms to avoid memory leaks. Use `room.leave()` when a user exits the whiteboard.
- Prefix room IDs with the user’s ID (e.g., `whiteboard_${userId}`) to ensure uniqueness.

### 2. **Authorization & Security**
- Validate user permissions in your `@liveblocks/node` auth endpoint. Example:
  ```javascript
  export const authEndpoint = async (request) => {
    const session = await validateSession(request);
    if (!session.isPremiumUser) throw new Error("Unauthorized");
    return { userId: session.id };
  };
  ```

### 3. **Optimizing Performance**
- Use `shouldThrottle` in `useStorage()` to reduce re-renders:
  ```javascript
  const others = useOthers({ shouldThrottle: 100 });
  ```
- Batch updates with `useMutation()` to minimize network calls.

### 4. **Error Handling**
- Wrap Liveblocks hooks in error boundaries to catch connection issues gracefully.
- Log errors to Sentry or similar tools for debugging.

### 5. **Scalability**
- For large teams, partition rooms by project (e.g., `project_${projectId}`) to distribute load.

Need more details on a specific area?