My
@[email protected] workflow that runs
@[email protected] is like six or seven steps, low event count, really straightforward. The filter needs some work, the
#GeoNet API gives me the last 100 events in the last 365 days, and I'd like to filter it down to, say, any events in the last fifteen minutes before exploding the array and deduplicating, but my lambda function for that was not behaving, something to do with the way I was processing the date values. I took three different runs at it with three different techniques, no luck, so temporarily settled on the last ten events.
But building that bot from scratch I learned some things that I could use to simplify the workflow that handles
@[email protected] and
@[email protected] (who already has more followers than I do). I also have this idea at the back of my head that I could run one workflow to normalize the
#GeoJSON coming in and just feed it into another workflow that handles the tsunami lookups, UTC to local time shifts, and posting to the right feed. That would make it easier to scale up if some other fedizen wanted a bot just for Japan or Chile or some other locale that also rests on unstable ground.
I also figured out how to do
ntfy posts, so I selfishly have Alaska quakes coming straight to my phone from the current workflow, just for kicks. That new toy makes me think of other things I could be doing, either for work or for play, with Tines and a free lunch hour.
#Quakestodon #ShowYourWork #GeekAllWeek