5 ms·
I'll consider it. The way it sits now is a bit specific to my deployment environment and in a language that I'm not sure a lot of folks would choose for new dev
by aparks517 6y ago
I'll consider it. The way it sits now is a bit specific to my deployment environment and in a language that I'm not sure a lot of folks would choose for new development (Perl 5 forever!)
Would you say that you're mostly interested in having the code for learning purposes so you could write your own thing, to deploy your own instance mostly as-is, as a starting place for significant modification, or for other purposes I haven't considered? Knowing this would help me understand what sort of open source contribution would be most valuable.
- bradley_taunt 6y agoReally it would just be to tinker with it and maybe have sort of "notes" or "micro posts" on my own personal blog. Any changes / adaptions I happen to make I would certainly open source as well (although my programming quality might not be as good as your current project for all I know...) I looked into basic Twilio SMS setup very recently, but it looked like I would find myself heavily invested in their documentation just to spin up something like you've made.
- aparks517 6y agoCool, thanks! Yeah, Twilio has a lot of documentation. It's pretty good, though. It felt like most of the time I spent on this project was finding the right documentation and setting up my account and number correctly. Maybe what the world really needs is a Twilio Concierge as a Service -- a meta-Twilio if you will. ;)