use nano-ids for change controlled tables

[samuelstroschein]

Use a nano id (see LIXDK-209) for every table that is change controlled (comment, discussion, file)

@samuel.stroschein said in LIXDK-281:

The complexity of a lookup table for share ID that map to UUIDs is avoidable if we use nano ids on tables where appropriate. See LIXDK-209.

Instead of having look up tables, we can use nano ids for the lix_id, file, discussion, and comment tables. These tables are the result of the change table anyways. The change table could stick to UUID v7. Benefits:

• increased sharing conversions because links are shorter
• no lookup tables (which would be needed for discussions, comments, etc as well)
• decreased storage

cc @niklas.buchfink (because we chatted about uuids for discussions in the navbar), @martin.lysk1 (because lix SDK team)

Additional information

Would close LIXDK-281 and LIXDK-209.

[samuelstroschein]

This is great. Even making the lix-id a nano id entails that multi lix can be encoded in the URL too. E.g. an app like the file manager (cc @niklas.buchfink) can persist in the URL what lix is opened.

lix.opral.com/y2h8s/files
lix.opral.com/As2h9/files

If the URL contains the lix id, the link is automatically sharable. A user receives the link which triggers the app to find the lix with the given id in OPFS or request it from the lix host. LIXDK-281 would not be needed anymore.

[samuelstroschein]

Discussed with @niklas.buchfink, we likely want sharable links for the public preview.