Thinking about this, it feels like the author is adding bandage on a leg, after breaking it. If you need to supervise your programs so you can't even leave the computer, feels like your time would be better spent on writing your software so it CAN (and will) fail but can recover by itself.
If you have any advice, methodology or anything that would make me a better programmer please share it with me.
I used to write code to fix existing problems; now I see if there's code I can refactor or remove first. Big difference.
That's aside from `diggan's point, which i agree with: if you need to babysit your server to such a degree, something is wrong.
We're on Hacker News, right?
I agree that allowing SSH would be a real issue, and better use an SSH client for that purpose.
But then, let me just clarify one thing for the people thinking that "Oh Whatsapp is owned by facebook it's evil". Do you really think that app on your Android device or your iPhone device will be foolproof secure? Both are owned by Google and Apple, there are some drawbacks. But tinkering about what if and what not is not my business. It does the job and if someone really wants to hack me, it's not that SSH app on my phone that will prevent him or her.
Programs break, like humans, this is just a way of giving a quick aspirine shot when I am not in front of my computer, which happens seldomly, but still.
I like the fact that when I wake up, i can message my server "start_tests with some new parameter" and he does the job while I enjoy my coffee. Cronjobs have to be defined beforehand, this is meant to be dynamic.
Don't allow shell access if you don't want.
Support libre software! :)
I'd love to be proven wrong about that though.
The reason I'm asking this that I work with communication/payment solutions for developing countries. Whatsapp usage is quite high in our user base but as long as there is no official api I figure I can wait.
(As for why not Telegram: I like Telegram, I just got one of my extended family groups over there yesterday, the problem is that unlike Whatsapp it doesn't work on things like s40 and s60 phones which means it isn't an option everywhere.)
He's deploying a project that's failing and he needs to manually restart processes on the server. He can't find a good SSH client for android, so he has his server execute commands messaged to it through WhatsApp. WhatsApp. https://en.wikipedia.org/wiki/WhatsApp#Security
And he open sources it!
This is either an April fools day joke or a 14 year old
A good use-case I can actually imagine myself using on the get go is allowing our part-timers to whatsapp our bot for their roster and scheduling, or make plans to what kind of days they want to work.
The beauty of this is that any new part-timers can come and go and with a simple server/authentication system in place it can be quite useful.
Love that it can work with Telegram too since my daily operations use both Telegram and Whatsapp.
It's better in some minor aspects: it's finally possible to screen -D -rr automatically upon connect; but it has an annoying top bar that can't be hidden; I use large font sizes (I'm often in shaky buses and trains) and it ends up using too much screen space in an iPad mini.
ServerAuditor is also more configurable re: fonts and colors and such, although the default font in Prompt is pretty good.
Ultimately it's what I use because it's the most tolerable, but I've yet to find a good Android ssh client.
Best to use a different protocol and avoid whatsapp.
Throw an interface around that, and let's talk. :)
Remember when IE had around 90% of market share 10 years ago? Well, the history repeats.