Brian

I've added a few more options, including permanent conversation deletion (rather than moving it to closed).

I'm adding API endpoints that can handle both agents and visitors (ie. creating a new message).

I've been making amazing progress with the backend APIs and the UI! Super excited :D

Hello! I apologize for the delay in updates, school has been eating up my time. I've been working more on implementing the chat system for agents.

I'm currently working on the inbox system and finishing up Websockets.

I'm currently working on Websocket implementation for the inbox page!

Wow, nearly 6 hours with no devlog! We're making great progress on the dashboard and the page system behind it! I'm trying to take my time on this part since it's the core of the app and I want to make it as intuitive as possible :)

I've added an account create flow page, implemented adding new workspaces in the API, and I'm now working on the user dashboard! Since I'm still learning Tailwind, I'm really just using this time to experiment with the classes so I can perfect this dashboard :)

I've done a few updates while at school! I've finally migrated to stored tokens for authentication (with an expiration option). Authentication tokens expire in 7 days, while password reset tokens expire within 15 minutes of non-use (otherwise they can only be used once and are permanently deleted after the request is processed).

All done with password reset implementation on the client-side as well! The next step will be migrating away from JWT and saving sessions in memory OR the database (probably a better idea).

I just finished adding implementation on the backend for password resets! However during this I noticed that JWT may not be the best method for sessions since that means we won't be able to revoke sessions (in the event of a password change, hijack, etc). Gonna work on alternative authentication.

I have finally finished with the sign in page, sign up page, and the password reset page! I'll need to add implementation for the password reset but I'll probably handle this later.

I'm currently working on the website itself! Adding the login page, reset password page, and signup pages.

I've been working on structuring all the components, and this is what I came up with:

/client -> The React app for the agent dashboard
/static -> Home page for Dispatch (what we were working on)
/ -> The Express.js server for API + WS handling (also serves the /client build)

All done with the README.md and the homepage! That took way long than I wanted it to :(

I decided to copy an existing one of my React apps and modify the CSS + Tailwind classes to get the promo page done faster. I'd like to focus my time on developing the back end systems!

I've been working on installing all the dependencies, structuring the project, and creating the Prisma database models. I'm currently debating if I should create the frontend or backend first...

Fixed an issue with the margin on the subheader, and I added a little label to remind the user when their inbox expires!

Finally finished with the implementation and revamped the UI!

I've added compatibility so users can have a custom duration with the API. Currently working on improvements for the mail UI.

I finally finished creating the API documentation! I took some time to make sure it looks clean and made it easy-to-use.

Second iteration is finally ready to ship! Here's a quick demo for anybody interested in how it looks now :)

I managed to upgrade my setup to a good Hetzner server! I also shortened the length of the emails since it previously used UUID (which was super long).

After some final commits, the website is finally ready for production! Updating the server right now.

We're down to the final stretch before the project is ready to ship! I created a MailViewer component to load emails and display them neatly, as long as any additional HTML.

Still working on some minor page changes. I had to fix a bug present in the toast and dialog which caused the opacity animations to work only half the time. This was solved using requestAnimationFrame which basically tells your device hey, i need to display an animation, update the frame and render the initial state before i do it.

I've created one unified session function which will handle all API requests. Decided to do this to clean up the code a bit (lots of repetition...).

Similarly for the toast, I created a dialog component to warn users before continuing with certain danger-zone actions. The component HTML is using a modified version of the code here (bleh Tailwind for putting all the other themes/icons behind a paywall): https://tailwindcss.com/plus/ui-blocks/application-ui/overlays/modal-dialogs

Had to fix a quick bug because index.html wasn't being served automatically for all routes (since this is a React app it's necessary).

I've been working on the overall design for the Mail page, and created a simple Toast component that I can use to display user messages. The component HTML is using a modified version of the code here (thank you Flowbite!): https://flowbite.com/docs/components/toast/

Currently working on designing the mailbox page! API is all done and ready-for-use (ignore the longgggg email, oh and the localhost...)

I've fixed a few bugs and also added session tokens when new disposable mailboxes are created. These are to prevent attackers from viewing your messages or deleting your inbox, because the token is required for access.

I've updated the code to save a message if one is caught! This means the API should now be fully operable and I can create, destroy, and view messages of disposable emails.

I've finished creating the SMTP server, setting up the Prisma database, and included rate limiting for API commands too!

Updated the server to install dependencies and serve the compiled React website if found.

I moved around some of the CSS properties, modified the page glow colors, and added a 404 not found page!

I've moved the custom cursor to its own component and added a pointer checker to remove it for mobile devices!

During this time, I finished working on the README, setup the domain + GitHub Pages, and patched a few bugs (including one which caused the How it Works, Features, and FAQ buttons to not function properly on locations other than /).
<br>
I also fixed the scroll margin top for each section, and create a ScrollToTop component to force the page to start at the top when the location is changed.

I've finished building the website and setting up my React + Vite project! I'm currently working on creating a README.

More progress on the website! I added a features section, finished the navbar, and added a custom cursor :)

I've created a simple page and setup my React Router!

First devlog! I'm learning how to setup Vite + React for the first time, and installing Tailwind CSS :D

Looks like the Summer of Making website was down! :(

During that time I finished adding the commands, updated the README, and also added an optional width/height parameter in the config.

I'm currently adding support for the existing box options, just like in the original whiptail library.

Just pushed the changes and re-created the Docker container. Stockbin is live and ready to ship!

I've added a search + filtering option for tags to find items easily! I also improved the query parameter formatting since it was previously messy.

Had to push a quick update because it was selecting the front camera on mobile devices...

Using the html5-qrcode library, I added a built-in QR code scanner!

I've added a simple way to view and print a QR code for a specific item.

I've added expiring items to be displayed on the user dashboard.

I've added an expiration date option for perishable goods, with the option of configuring your time zone in settings. If a time zone isn't configured at the time of creating/updating items with expiration dates, it will attempt to pull their local time zone from their browser and update their account automatically!

I've created some Docker files for easy deployment. I'm ready to ship!

I added a view button to all items and a list of their parameters! I've also finished with the README.

Using the existing creation ejs template, I updated it to support editing an existing ID as well! The backend now accepts both new items and existing ones.

I've been working on improving the code structure and creating the pagination system to view your inventory!

I've been working on adding error handling to the database, main server, and creating simple user middleware.

All done with the settings page! Working on the backend APIs next.

I've finished with creating a simple home-screen and I'm almost done with the settings menu!

I've finished with the backend creation API, setting up the database, and the create menu!

I've finished the backend login API implementation, and added email support with Nodemailer!

I've finished creating a basic login system, and I'm working on the create page next!

Welcome! I'm currently working on implementing a passwordless login system to access the dashboard.

I added a note for the old version which mentions an issue related to PDK iteration checks. Basically the application was using the bitwarden.com API to find the user PDK iteration instead of checking what region they're in.

This could really only be a problem if the user was using bitwarden.eu and had configured their PDK iteration count in their Bitwarden settings to something that isn't the default value (which is obviously experimental and not recommended by Bitwarden).

Still worth mentioning though in-case users have issues.

I was having issues with the system tray not showing up in the compiled exe installation. Turns out I forgot to include extraResources in my package.json, so it wasn't downloading my icon properly. All fixed now and the system tray is shown!

Just added support for self-hosted Bitwarden servers (as per issue #3 on GitHub). Works great now!

Good evening! Today, I worked on adding a system tray, allowing users to easily view their backup status and manage the app. I also worked on restructuring the restore flow (instead of using a file HTML input, I'm processing the JSON file on the server side).

Just finished creating the README documentation, pushed to GitHub now!

The CLI tool is all done (sorry for laggy demo, Snipping Tool sucks...)!

I've added some advanced features that users can toggle when running the program!

I've been able to build an algorithm that checks matching subdomains and usernames. The next step will be to add apex-level domain checking as an optional, advanced feature!

I'm currently working on restructuring the code since this is a project I worked on a long time ago and it's full of bugs...

Welcome! I'm currently working on creating the user selection for the CLI.

I've created a Prisma database migration, and updated the logo/banner to have a gradient theme.

It's been a week! I've been working on a few bug fixes, including enabling UserInstall (this will allow users to use Timer Bot anywhere). Unfortunately due to Discord API restrictions, however, event reminders need to be sent to the users DMs since the bot won't have permission to send messages in the channel it was run. Regardless, everything works great!

I've created a simple Loki database migration script, and have successfully merged the databases! Timer Bot is now live on version 3.1.0!

I've updated the README, Dockerfile, and docker-compose.yml to include the updated changes and caution users. I'll be working on a helper script to migrate the old Lokijs database easily next!

Looks like I may have shipped too soon... I was not aware of this, but Prisma doesn't allow a Number type, and rather only accepts Int, BigInt, and Decimal. To combat this, I had to make a few adjustments to the db.js code so that it converts to Number respectively.

They really need to fix this... very frustrating.

Working on the Prisma schema.

The project is now ship certified! Since then, I fixed the script tag structure and moved the disableKeys to the window so they're accessible in other files. Also, I noticed a small bug which allowed users to click the enter key and create new lines in the terminal when bash files are running (thanks ship certification video 😉).

These have now been fixed!

I'm currently working on merging my LokiJS databases to Prisma, an open source database management library. I'll be using SQLite for my database since it's more commonly used and lightweight.

There was a bug involving the deletion of presets, where if the preset tag (the name of the preset) was a number, the interaction event would believe it's a cached interaction ID, and caused some issues. I have fixed it by adding a simple t_ string in front which is removed when handling it.

I just finished creating a simple README.md for the website and uploading the LICENSE file.

The website is almost ready! Uploading to GitHub and setting up GitHub Pages :)

(apologies for the laggy screen recording... snipping tool sucks)

It's looking like the website is now mostly done! Still working on modifying each page a little, including meta tags, etc.

Welcome! During this time I've worked on building the whiptail-js library, which is used for this website. I actually have a separate project for it which you can find here: https://summer.hackclub.com/projects/10034

I'm working on building the interactive terminal, and making a few small adjustments to the website layout.

whiptail-js has been published to npm and the repository is live! I'm planning on potentially adding more features in the near future. Check it out on npm here: https://www.npmjs.com/package/whiptail-js

Just finished writing to README, being published to npm!

It's been a while! What started as a simple personal website turned into a full-on Whiptail UI class in JavaScript, which mimics the look and feel of a terminal-based dialog. It's now complete with keyboard navigation and touch support.

I'm calling it whiptail-js: a lightweight terminal-style dialog library for the web, which is used through the WhiptailJS class. Currently writing a short README to get it published on npmjs :)

I have added touch support and removed the viewport meta tag to keep the UI consistent across desktop and mobile.

I've made the UI responsive by listening to arrow key clicks! I'll be adding support for mobile next by allowing users to select by clicking the items with touch.

I've been working on a terminal-like GUI interface written w/ HTML + CSS. I used the raspi-config terminal GUI as my starting point because it's a good representation of what I'll want my website to look like.

Working on detecting arrow keys and allowing the user to select an item.

Finally, I added an optional parameter in the /timer, /alarm, /reminder, and /preset run command to specify a custom channel where the notification will be sent in. By default, leaving out this parameter will send the notification in the same channel the command was run (as it was earlier)

I've noticed that many users are in different regions across the world, so I added a simple /convert command which will allow you to convert a date and time for a certain region to your local time zone.

Just finished working on an import command allowing users to import multiple events in one go!

I've been looking over the code a bit and have implemented a /export command, which allows users to export all events at ONCE as an ICS or JSON file.

Also, it came to my attention that the rate limit for active events was only one... that was 100% a mistake and I must've skipped over it as I was testing on the development server. It was fixed to 15 events now!

It's been a while! I'm currently working on a handful of small improvements, including an Add to Calendar feature allowing you to generate an ICS file for easy Google Calendar / Apple Calendar implementation.

I'm working on a few admin commands, including an eval command (which may or may not be a smart idea...)

I've been working on a few bug fixed behind the scenes, including an issue reported on GitHub where Bitwarden users without a full name set weren't being displayed.

I've been working on adding a simple backups tab to view your backed up vaults, as well as extra error handling!

I've mostly finished with rewriting the code, and I worked on designing the home page UI!

Previously, the application was only able to create automatic backups for one single account when logged into Bitwarden Desktop. I've been working on revamping the UI to match the new Bitwarden style, and implementing multi-account backup systems! Also, I've been working on restructuring the code and libraries.

I added a simple command to view the status of the server, and the bot is now live!

Making some finishing touches! Ready to move over to Docker.

Working on small imperfections, fixing Docker configurations, added check for environment variables.

Some of my written libraries (like the PayPal integration) need access to a client in order to send a confirmation message to users. Problem is these libraries are imported in the parent process since running them in each shard would just cause a bunch of conflicts (hence why I've implemented IPC communication from shard -> main process). After overthinking about it for 10 minutes I just figured the simplest solution was to treat shard 0 as a default singleton client and create a message listener in the shards. So that's what I did!

Currently working on implementation with the PayPal Business API for tips! My original plan was to make some quick implementation with Ko-Fi and Discord roles, but they take a 5% cut, so I setup a webhook directly to PayPal.

After about an hour of debugging DiscordAPIError[10062]: Unknown interaction bugs, I finally realized my own stupidity. I completely forgot about the Docker container running on my other server that was connected with the same bot token...

Glad to say everything works as it should now haha.

Working on rebuilding all my libraries and database functions to work thru IPC!

So, I may have gotten a little carried away with writing all the commands and didn't consider the fact that the ShardingManager also means I was spawning multiple instances of my database... working on making an IPC communication method now haha.

Also completely forgot that each user may have their own timezone, so I've been working on adding timezone compatibility for alarms and reminders.