miitinguid

Miitinguid is a term used in the Miiting conferencing ecosystem to denote the unique identifier assigned to a specific meeting instance. It functions as a stable reference that allows clients, servers, and analytic services to locate, access, and track a given meeting across multiple components of the platform.

In practice, a miitinguid is a string generated to be globally unique within the system. It is typically implemented as a UUID- or GUID-like value, often displayed as a hexadecimal string with hyphen separators. The exact formatting may vary by deployment, but the goal is collision resistance and traceability.

Creation and persistence: The miitinguid is generated at meeting creation by a central identity service and stored in the meeting's metadata. Once assigned, it remains constant for the life of the meeting, enabling reliable joins, transcripts, recordings, and audit logs even if the meeting is renamed or moved.

Usage: Applications pass the miitinguid as part of API requests and URL paths to identify the target meeting. Internal services use it to pull configuration, access controls, and historical data. It is not meant to convey sensitive user information by itself.

Security and privacy: While a miitinguid is not a password, it should be treated as a bearer reference to a meeting resource. Public exposure of miitinguids may increase link-sharing risk, so access controls, expiration, and rate limiting should be applied where appropriate.

History and notes: The concept emerged within the Miiting platform as part of its resource-identification strategy and shares the same design goals as UUIDs and GUIDs used in other systems. It is not a global standard outside the Miiting ecosystem, though it aligns with common UUID practices.