Ask Crisp support why they aren't sending me email notifications even with email notifications enabled (it's a gmail account so shouldn't be any mail routing issues, already checked spam folder, etc). h/t @marc for sending me a live chat which caused me to realize I never received it after 3 days, only found it when I manually checked my Crisp inbox 😬 #watchdog !private

Deploy rule wording change for Build in Public because @marc let me know there were a few false positives and after testing the new rule wording, it seems to be fixed now 👍 #watchdog !private

Fixed a null pointer in watchdog by adding a missing `continue` statement. Now the X bot runs reliably even when tweets with malformed data get parsed #watchdog !private

Built an internal endpoint that lets me remotely force a browser to refresh the current page, which is a short term solution that will hold me over during rate limiting situations - that is until I add retries all over the codebase which is happening very soon #watchdog !private

Think about new design for error handling for the X bot (because X goes down a lot and rate limits at a random interval, this should make things more reliable over the long term): Think I'm going to make each browser function fail after 10s max (library I'm using currently deadlocks if the element doesn't exist on the page since it retries indefinitely) which would then trigger a refresh after a delay #watchdog !private

Fix refresh to be every 30 seconds instead of every 10 seconds because X is rate limiting me occasionally and Watchdog missed some posts last night. Will soon add randomization to this to act like a human. #watchdog !private

See Watchdog reporting posts in production via my remote monitoring tool! #watchdog !private

See Watchdog for X running in production! Manually provisioned an EC2 instance and set up docker compose for the chromium container, easier than fighting with Kamal under a time crunch #watchdog !private

Have even more issues with Kamal where it refuses to deploy a new docker container (container fails to start), I think because the same port is being used by the old one? Works when I manually stop the old container and deploy again. Seems horribly broken and now need to move to a different deployment method to get #watchdog working for Build in Public !private

Mess with kamal for hours and hours and FINALLY get the app deployed in prod (not working in CI yet, it just times out on SSH for some unknown reason). Kamal needs a lot of work to be production ready, not very happy with it so far. Now to make sure my app can talk to the chromium container which is also running on Kamal now #watchdog !private

Mess with complicated AWS VPC settings and get dual-stack ipv6/ipv4 working, then deploy a Ubuntu VM, now working on app deployment to prod with Kamal with the help of @strzibny's book #watchdog !private

Fix bot detection issue which was preventing login on X from succeeding sometimes #watchdog !private

Redo entire build and deploy pipeline; separate the Chromium process manager into its own Docker container and have the bot in a separate container control Chromium remotely to prevent crashes #watchdog !private

Added a remote monitoring server with live video feed running via Docker so I can see what the bot is doing at all times before enabling @marc 's Build in Public community in prod #watchdog !private

See @marc become a customer of Watchdog (thank you @marc!) and post about that + the X integration going live: x.com/ben_makes_stuff/status/… Will update landing page and post on other socials later, not advertising it too heavily besides on X for now #watchdog

Get Watchdog AI rule violation detection + automated post reporting working for X communities. Pretty cool to watch it work with headless = false and trace mode enabled. Full demo: www.youtube.com/watch?v=VMxCI… #watchdog !private

Finish “report user” ie delete message implementation for X communities, now to test it #watchdog !private

Overhaul pricing for Watchdog before launching X support because it was a mistake to try to sell to small communities, and post on X on about it: x.com/ben_makes_stuff/status/… #watchdog !private

Added logging of "dry run" flag to allow community owners to see if the rule was actually enforced or not. cc @marc because you asked about this I think #watchdog !private

Added stubbed out punishment handlers for X and enabled dry run mode so I can see if AI message analysis is working for X #watchdog !private