I hereby claim:
- I am koad on github.
- I am koad (https://keybase.io/koad) on keybase.
- I have a public key ASCfSA0p_iIqYJuQGLHtem64OPtncINEGM9-dG-oxr5LUQo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
| // Discord all events! | |
| // A quick and dirty fleshing out of the discord.js event listeners (not tested at all!) | |
| // listed here -> https://discord.js.org/#/docs/main/stable/class/Client | |
| // Learn from this, do not just copy it mofo! | |
| // | |
| // Saved to -> https://gist.github.com/koad/316b265a91d933fd1b62dddfcc3ff584 | |
| // Last Updated -> Halloween 2022 | |
| /* |
| process.stdout.write('\u001B[2J\u001B[0;0f'); // clear the screen | |
| const signale = require('signale'); | |
| signale.time('upstart'); | |
| const upstart = new Date(); | |
| signale.pending('Catchall API starting...'); | |
| signale.info('Setting local timezone to "America/Toronto"'); | |
| process.env.TZ = 'America/Toronto'; | |
| const { parse } = require('querystring'); | |
| const express = require('express'); |
| # Saved to -> https://gist.github.com/koad/733ca120bc7f0ca44ebd2e96d658b177 | |
| # Last Updated -> July 5th, 2023 | |
| # | |
| # koad-was-here | |
| # | |
| # koad's https://starship.rs prompt configuration. | |
| # ~/.config/starship.toml | |
| format = """ | |
| $cmd_duration\ |
| π Beatify Identity Verification π | |
| Hey there! Iβm koad on Beatify, proudly representing as koad on github! π Check my profile for authenticity! | |
| π https://beatify.audio/koad/signature/APZ8DfXHGfpdatYeT | |
| -----BEGIN PGP SIGNED MESSAGE----- | |
| Hash: SHA256 | |
| π Beatify Identity Verification π | |
| I hereby claim: |
| /** | |
| * π Animated Terminal Prompt with Rainbow Spinner | |
| * | |
| * A beautiful, animated command-line prompt that features: | |
| * - Braille pattern spinner animation | |
| * - Smooth rainbow color transitions | |
| * - Graceful Ctrl+C handling | |
| * - Real-time prompt updates | |
| * | |
| * Author: koad |
| /** | |
| * π¨ ANSI Color Learning Playground for Node.js Terminal | |
| * | |
| * This script demonstrates various ways to add colors and styles to terminal output | |
| * using ANSI escape sequences. Perfect for learning how terminal colors work! | |
| * | |
| * ANSI Color Code Reference: | |
| * βββββββββββββββ¬ββββββββββ¬βββββββββββββββ¬ββββββββββ | |
| * β Color β Normal β Color β Bright β | |
| * βββββββββββββββΌββββββββββΌβββββββββββββββΌββββββββββ€ |
| /** | |
| * Keybase Janitor Supreme | |
| * | |
| * The digital equivalent of a bouncer with OCD - automatically evicts unwanted | |
| * private chat messages from your Keybase like they never existed. | |
| * | |
| * Mission Briefing: | |
| * This script stalks your chat like a caffeinated security guard, watching for | |
| * messages from your personal "naughty list" of users. When these digital | |
| * troublemakers send you anything, this script: |
| #!/bin/bash | |
| # | |
| # =================================================================== | |
| # Meteor 3.0 Migration Analysis Script | |
| # =================================================================== | |
| # | |
| # Purpose: | |
| # This script scans Meteor applications for deprecated functions and patterns | |
| # that need to be updated for Meteor 3.0 compatibility. It provides detailed | |
| # reports with file locations, line numbers, and migration advice. |
| Condense the above conversation into a JSON object with the following fields: | |
| - "context": A short, descriptive title summarizing the main topic. | |
| - "condensed": A bullet-point list containing dense, high-detail, word-efficient summaries of all key insights, technical changes, or instructions discussed. Maximize clarity and completeness while minimizing unnecessary words. | |
| - "endpoint": The name of the AI agent generating this response. | |
| - "sentiment": A single word that reflects the overall tone or feeling of the conversation (e.g., 'neutral', 'urgent', 'optimistic', 'frustrated'). | |
| - "tags": An array of keywords or topics covered (for search/indexing). | |
| - "actions": A list of discrete steps or changes that a developer or system should take based on the conversation. | |
| - "code_refs": A list of file paths or code areas likely impacted by the discussed changes. | |
| - "risk_level": One of 'low', 'medium', or 'high' β based on how disruptive or critical the changes are. |