* Moving away from auto_increment

! Initial id size will stay as u64 but u128 are easily the next major change
This change shouldn't break clients written in high level languages since most already use 128's under the hood anyway
- This commit also removes the auto_increment flag from basically everything that uses RNG id's

json-api/migrations/2020-03-11-005217_channels/up.sql

@@ -1,6 +1,6 @@
 -- TODO: somehow make the name colum unique
 CREATE TABLE IF NOT EXISTS `channels` (
-    `id` BIGINT UNSIGNED NOT NULL auto_increment,
+    `id` BIGINT UNSIGNED NOT NULL,
     `name` VARCHAR(255) NOT NULL,
     `description` VARCHAR(2048),
     `kind` INTEGER NOT NULL,

json-api/migrations/2020-07-05-215114_members/up.sql

@@ -1,7 +1,7 @@
 -- TODO: add rate limiter in some form
 -- PERMISSIONS start at 0 and full perms => all F's
 CREATE TABLE IF NOT EXISTS `members`(
-	`id` BIGINT UNSIGNED NOT NULL auto_increment,
+	`id` BIGINT UNSIGNED NOT NULL,
 	`secret` varchar(256) NOT NULL,
 	`name` varchar(256) NOT NULL,
 	`status` integer NOT NULL,

json-api/migrations/2020-07-06-022319_messages/up.sql

@@ -1,7 +1,8 @@
 -- Time stamp is _not_ in ms
 CREATE TABLE IF NOT EXISTS `messages`(
-	`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
+	`id` BIGINT UNSIGNED NOT NULL,
 	`time` BIGINT NOT NULL,
+	-- Assuming content-type is `not` text/plain this will be a reference to some auto-named file
 	`content` VARCHAR(4096) NOT NULL,
 	`content_type` VARCHAR(10) NOT NULL,
 	`author_id` BIGINT UNSIGNED NOT NULL,