nimeet Docs
中文

Whiteboard Changelog

Whiteboard product versions, new operations and the compatibility window of each version.

Version v1.0.0 · Updated 2026-10-28 · revision 1

This page records version changes of the Interactive Whiteboard product line. Version numbers map one-to-one to the REST interface definition and the Web SDK version.

Version 1.0.0 (2026-10-28)

First GA release covering rooms, scenes, content, snapshot, replay and tokens end to end.

  • Added /v1/whiteboard/rooms: create, list, detail, ban/unban, permanent close.
  • Added /v1/whiteboard/rooms/{uuid}/scenes and scene-state: list, insert and switch scenes.
  • Added strokes, images, viewport: append/erase strokes, insert images, update the viewport.
  • Added undo / redo: per-member undo/redo backed by the full operation log.
  • Added snapshot, snapshot.svg, replay: JSON snapshot, SVG export and the replay timeline.
  • Added tokens/rooms/{uuid} and tokens/teams: room and project tokens with admin / writer / reader.
  • Added members: join/leave and the writer limit.
  • Published @nimeet/sdk-whiteboard-web 1.0.0: Room, Scene, Camera, Member, Player/Replay and error codes.
  • Android / iOS ship interface definitions plus explicit NOT_SUPPORTED stubs only; no rendering or media path.

Compatibility window

  • The 1.0.0 REST surface is frozen in the v1 whiteboard interface definition; new optional fields are compatible changes.
  • Breaking changes ship as new paths (/v2/...) and a new SDK major version; 1.0.0 stays dual-published for at least 90 days.
  • Token prefixes (NETLESSROOM_ / NETLESSSDK_) stay stable.

Known limitations

  • The operation log keeps the latest 10 000 records per room.
  • The server does not provide document conversion or scene deletion.
  • The in-memory store is cleared on restart; production must use a persistent store.

Generated by the documentation build pipeline · 2026-10-31 01:24:02 UTC · Documentation center v1.1.0.

Content follows the public API definitions.

ni-meet is a self-hosted RTC PaaS with a LiveKit-based media plane (Apache-2.0) and an Agora-compatible API.