Back at work on #crisp

fix some google cloud fcm api timeout errors I have been seeing in #crisp logs since 5am this morning

polish new #crisp website shared inbox section

throw away plants at #crisp office for pest control

polish new #crisp website pricing page

finish implementation of pricing page of new #crisp website

work on new #crisp website

Finish data mock for #crisp app

update #crisp offices homebridge setup for security and iot

Create data mock adapter for the #crisp app, to make testing easier

run speedtest from my mac connected to my #crisp offices lg ultrafine over thunderbolt with wired ethernet

Work on new conversations list #crisp

improve #crisp chatbot Redis management resiliency to network failure

suspend #crisp office monitor with arm

work on the #crisp bot today, bringing more ai scenario blocks

Just discovered CSS container queries, literally a game-changer!! Gonna use them for #crisp where we have user-resizable components but still need to maintain responsiveness

fix a huge issue with #crisp infrastructure, due to the way dns works in debian/glibc based systems, where if the primary resolver goes down, nodejs dependencies such as sequelize would be unable to fallback to the secondary dns resolver, leading to downtime of anything that connects to a sql database from nodejs, meaning the whole #crisp rest api would go down!

schedule a full day working on fixes here and there on #crisp polishing the huge machine we've built over 10 years

Fine-tune dropdown keyboard navigation #crisp

was feeling more and more cloudy as days passed handling #crisp issues (scale is hard for someone creative, makes good money but hard on happiness), taking some slowdown time today working on #prose to re-energize