Supinic

(async () => {
    const essentia = require("essentia.js")
    const time = {
        start: process.hrtime.bigint()
    };

    const file = await require("fs").promises.readFile("D:\\pirate gay remake.wav");
    time.file = process.hrtime.bigint();

    const vector = essentia.arrayToVector(file);

Supinic

(function (ircLib) {
	var Bot = function () {
		var $class = function (channels) {
			this.irc = null;
			this.nick = "Supibot";
			this.server = "irc.chat.twitch.tv";
			this.port = 6667;
			this.channels = Array.isArray(channels) ? channels : channels.split(",");
			
			this.initIRC();

Supinic

Online storage of supibot commands: JSON vs JS

JSON
	(+) respected format
	(+) safe, no issues with evaluation
	(+) easy to port around
	(-) awkward to edit overall
	(-) terrible to edit code
	
JS

Supinic

1. Repo will be new, and separate from anything that concerns the `supibot-sql` repo 
  - (idea: supibot-sql is just a version control for whatever the main instance does)
2. Implement a method into `sb.Command` to "install" a new command from a description object
3. sb.Command.install will also handle duplicates - will update instead of failing (like now)
4. Repo command definitions will be in `.js` syntax as IIFEs that return a description object
5. Each command definition should be prefaced by an author/ownership comment
6. Think about some sort of authorship/source signature hash, not necessarily as a part of the definitiion but rather as a separate file or a list of hashsums in the root dir

Supinic

Current:
	N/A

High priority:	
	Blood
	Ion Fury (same devs as Blood)
	
Rest:	
	Leisure Suit Larry X (+ speedrun?)