See Watchdog moderating images on X with the new AI image moderation feature enabled #watchdog !private

Shipped image moderation for Watchdog across all platforms (X, Reddit, Telegram, Discord)! Demo: www.youtube.com/watch?v=JbxLs… #watchdog

Hijack requests to community timeline endpoint and added rate limit monitoring for X so I can get an alert (or automatically wait the right number of milliseconds) when X is likely to block Watchdog #watchdog !private

Wake up and see that auto recovery is working - as when I went to sleep it was blocked by X - and when I woke up it was refreshed enough times to start working again, going to deprioritize further work on this for now #watchdog !private

Respond to a very unique inbound from a guy on Telegram who operates a bunch of Furry communities and wants chat moderation. He's likely going to move forward with testing it for one month at $29/mo, then scale it to all of his communities if works well #watchdog !private

Built a backtesting endpoint so customers can see how changes to the rules affect how Watchdog interprets messages h/t @marckohlbrugge for the suggestion #watchdog

Notice Watchdog is still getting blocked by X on occasion even though I have much better resiliency now with auto refresh. Investigating hijacking the requests so I can see the X-Rate-Limit-Remaining header to know when to start scraping again instead of refreshing blindly #watchdog !private

Post about the X integration on LinkedIn because I totally forgot to do so when I posted on X: www.linkedin.com/feed/update/… #watchdog !private

Added retries and backoff to all message analysis jobs in Watchdog so I can stop getting paged for intermittent 5xx errors #watchdog

Log into my remote monitoring UI and see that my resiliency fixes worked - Watchdog for X has been running continuously for over 24h with no crashes. No more manual restarts needed! #watchdog !private

Foiled a 1337 h4x0r #watchdog !private

Notice Watchdog is getting some organic traffic now, and talk to some random guy who joined and might buy Watchdog about privacy concerns #watchdog !private

Added way more resiliency to the X bot to handle scenarios where X goes down, rate limits, or otherwise doesn't load the timeline of posts for a community #watchdog !private

Watchdog now removes offensive messages on X instead of just alerting the admins - thanks @marckohlbrugge for the suggestion #watchdog

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