One of my goals with Autoblue is to be very open and transparent during the process of developing this plugin, and to take you along on the journey. Part of that is sharing feature updates whenever I add something new to Autoblue, which is why I’m writing this post!
Logs aren’t exactly an exciting feature—in fact, I hope you’ll never even need to take a look at them. However, they might be invaluable when you do need them, and as a developer I’m quite excited about this.
Imagine this scenario: you publish a new post, expect it to get shared to Bluesky automatically and… nothing happens. You refresh a few times, but your post doesn’t appear, so instead you end up cursing me under your breath and sharing your post manually.
While I’m working super hard to ensure this never happens, there’s always something that can go wrong. Maybe the Bluesky API is simply down. With Autoblue’s logs, you’ll be able to trace back all the steps that happened when the post got published, and see where things went wrong.
Why logs?
That’s a fair question—logs don’t really sound exciting, especially when thinking about some other features I have planned for Autoblue, such as scheduled shares and media uploads. However, with Autoblue being a brand new plugin still in development, bugs are bound to appear, especially as I add more features.
By adding logs now, I can ensure that when things go wrong it’ll be clear what happened and where the error occurred. This will make it much easier to fix issues quickly, and will hopefully make the experience of using Autoblue much nicer.
If you run into any issues with the new log functionality, please ping me on Bluesky!