Back
Banjo Bridge
Load previous page…
#banjo Setup Laravel Vapor and try deployment
#banjo Make sure Slack replies get threaded on Discord
#banjo Check that channel/user mentions and emojis get translated correctly.
#banjo Finally get Slack => Discord messages sent
#banjo On channel sync automatically create one webhook per Discord channel so that we can make use of customized avatar/username functionality which isn’t supported for regular API messages
#banjo Successfully receive data for implementing first event
#banjo Re-implement rejecting messages for various reasons
#banjo Add scheduled task to refresh potentially stale Discord bot tokens
#banjo Setup async handling of received messages for both Slack and Discord
#banjo Auto-join all channels on Slack when syncing channels because otherwise the bot can’t listen.
#banjo Implement Slack Socket Mode connections with proper reconnects and simplify how I handle message types
#banjo Refund customer who had competing offer because they outshipped me. C’est la vie 🤷♂️
#banjo Organize original Slack message processor into concrete steps so I can start porting it to new app structure
#banjo Complete onboarding workflow
#banjo Receive answer from owner of banjobridge.com that he doesn’t want to sell the domain to me under current circumstances
#banjo Grab a table from Tailwind UI so I look like I got mad 1337 design skillz even tho I don’t
#banjo Load and pair up Slack and Discord channels. Give user preview to see if they missed any channels they might want to sync.
#banjo Finalize installation workflows for Slack and Discord bots, accidentally find way to optimize setup process which is now 2(!) steps
#banjo Setup Slack OAuth process so I can receive workspace specific token to post messages
#banjo Write email to owner of banjobridge.com if he’d like to sell the domain to me as proclaimed on his website