hugodf / botnet

:satellite: networking tools for Slack

👋

I'm a JavaScript developer and run codewithhugo.com.

You've probably seen me around the Node.js/JavaScript/Testing community, where I help with:

• Wes Bos' awesome-uses.
• Alpine.js Weekly Newsletter
• Alpine.js devtools
• Alpine testing utilities

About me:

• 📚 I blog at codewithhugo.com, recently published The Jest Handbook.
• 🔭 find me hovering around the Alpine.js repository with code contributions, comments in GitHub Issues, the community Discord and StackOverflow.
• 💬 Ask me about: JavaScript, Alpine.js, Node.js, React, Testing
• 📫 How to reach me: on Twitter, @hugo__df
• 🤔 I’m looking for some Sponsors to keep running the Alpine.js Newsletter

botnet's Issues

Enhancements for UX

If the command times out Slack provides a generic "that slash command didn't work" message, which might be confusing to users. Slack requires a response within 3 seconds, returning a direct message like "Sorry, BotNet couldn't complete this request."
Alternatively, if possible, you could return a message such as "Lookup in progress..." and then post a response to the response_url once it's available.

Discrepancy in the app name

I noticed a discrepancy in the app name — sometimes it's referred to as "Bot Net" and sometimes "BotNet". I recommend picking one or the other and using it consistently across your help pages and other references. Please let me know which you settle on and I can update the name in Slack if needed.

Change `[url]` in commands for clarity

I recommend changing [url] in your commands for clarity:

/dns [domain]
/domain [domain]
/ping [host or IP]
/whois [domain]

Add validation for command inputs

I recommend adding validation to the inputs for each command.
For example: /ping http://cnn.com or /ping soup — return errors for these or any other invalid input, or in the event no input is given at all, ie: /ping