undecim
March 23rd, 2010, 12:31 AM
I'd really like some opinions on an idea I've had for a while now.
I've noticed that a lot of support threads in the forums take a lot of time and effort to diagnose and fix simple things. Often times, it gets to be a back-and-forth between techie, newbie, and terminal, and the real time waster is the latency between the techie and the terminal.
Even on IRC, anyone helping a user has to ask the user to type commands into a terminal and then post a pastebin link. And it doesn't help that some users give up on pasting to the terminal when Ctrl + V doesn't work and just start transcribing commands manually. The fastest way to solve a problem would be an SSH shell to the system, but there are many obvious problems with that, most notably security.
I have an idea for a web application that would make this process much faster and allow more collaborative troubleshooting.
It involves a terminal inside a web browser (via a browser plugin). The terminal is viewable by anyone in the same room, and all communication is done over ubuntu's IRC channel (for the safety of many eyes watching out for malicious commands.)
Anyone helping another user this way can "suggest" a command, and that command will be added to a list of commands that the user can easily run. This suggestion mechanism would be handled over IRC with an english-like syntax. (For example: "techie: @newbie: try the command 'uname -a'") so that any malicious commands are caught by the many eyes of the IRC channel.
Also, to prevent sensitive information from being shown over the application (IP address, etc.), the user receiving support will need to click an "update" button before the text shown in the terminal is sent to anyone watching it. When the update button is pressed, a message is shown over IRC with a link to the web page with the room (so that anyone in a normal IRC client can join in if they know how to fix the problem)
A plugin would have to be used by the browser receiving support that can open a shell on the local system or over SSH (for fixing servers, etc.).
I have a few mock-ups below. One for the user interface (for the person receiving support) and one for the supporter interface (for people giving support). Hopefully, those are a little more clear on my idea.
I've noticed that a lot of support threads in the forums take a lot of time and effort to diagnose and fix simple things. Often times, it gets to be a back-and-forth between techie, newbie, and terminal, and the real time waster is the latency between the techie and the terminal.
Even on IRC, anyone helping a user has to ask the user to type commands into a terminal and then post a pastebin link. And it doesn't help that some users give up on pasting to the terminal when Ctrl + V doesn't work and just start transcribing commands manually. The fastest way to solve a problem would be an SSH shell to the system, but there are many obvious problems with that, most notably security.
I have an idea for a web application that would make this process much faster and allow more collaborative troubleshooting.
It involves a terminal inside a web browser (via a browser plugin). The terminal is viewable by anyone in the same room, and all communication is done over ubuntu's IRC channel (for the safety of many eyes watching out for malicious commands.)
Anyone helping another user this way can "suggest" a command, and that command will be added to a list of commands that the user can easily run. This suggestion mechanism would be handled over IRC with an english-like syntax. (For example: "techie: @newbie: try the command 'uname -a'") so that any malicious commands are caught by the many eyes of the IRC channel.
Also, to prevent sensitive information from being shown over the application (IP address, etc.), the user receiving support will need to click an "update" button before the text shown in the terminal is sent to anyone watching it. When the update button is pressed, a message is shown over IRC with a link to the web page with the room (so that anyone in a normal IRC client can join in if they know how to fix the problem)
A plugin would have to be used by the browser receiving support that can open a shell on the local system or over SSH (for fixing servers, etc.).
I have a few mock-ups below. One for the user interface (for the person receiving support) and one for the supporter interface (for people giving support). Hopefully, those are a little more clear on my idea.