For the past 3 months, I've done a few development explorations with Twitter API. The results were (shameless plugs) my two projects, Tweet Schedul...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for this write-up, this will be super-helpful to other developers (also, I love to see folks deploying code to Now!). Looking forward to seeing your CLI tool. Also - did you look at autohook? dev.to/twitterdev/how-to-build-a-c... :-)
Hey Andy, I totally missed Autohook. Itβs awesome. I aim to write something quite similar, but slightly more versatile in my CLI.
By the way, is Autohook serverless friendly? It seems like itβs designed for a running server, right?
Hi Alex! Thanks for checking out Autohook! So great this is inspiring you to create something similar.
Autohook has a built-in server, but you can disable that and use your own instead. This is useful in situations where you want to serve a webhook via a serverless module, and only use Autohook to handle incoming messages and user subscriptions.
The standalone server test shows an example of this. You can serve a webhook from anywhere, as long as it implements a CRC check (you can use
validateWebhookfrom Autohook without starting a server).Hi Alex, your article was really helpful for me as a beginner to Twitter developer stuff.