Jeff Hochberg

My feedback

  1. 439 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Implementing  ·  69 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeff Hochberg commented  · 

    @Christopher - that practically made my head explode! Unbelievable!

    One comment I'll make to the group - developers are very quick to ask "why do you need this?" or "what is the use case?". It's a very common request. If you understand what the issue(s) is/are that the customer is having and how they would use it, you typically get a good idea of what the feature should be. Unfortunately, there's a lot left to interpretation and, in many cases when the feature is ultimately delivered, it falls short of what the customer is expecting. This is due to poor communication between the developer(s) and the customer(s).

    In an ideal world, if the developers provided customers with a wireframe/description of the feature before it's released, there's a good opportunity to make changes before shipping the final build. Of course, this can become a total mess as well because everyone has their own wants/needs, so the process needs to be tightly managed.

    With respect to the "Why do you need...?" question - my response to the developers is:

    1. Why do I need the ability to export the console log? Have you ever worked on a piece of networking gear? The entire configuration from a switch/router/firewall/etc is visible via an SSH/Telnet session and being able to capture the text is CRITICAL for cases when you can't use other functions to transfer configurations to/from the device (i.e. TFTP/FTP).

    I use a couple of different console servers (WTI & OpenGear) that allow me to SSH into them and they connect me to the serial console of network devices.

    Hopefully, that makes sense to you.

    2. Why do I need the ability to export sessions?

    Because if I ever want to use the configuration from my Termius client in other SSH clients, then I should be able to export the address book to a human-readable (not binary or encrypted) so I can import it into something else. I might have to massage the data, but that's OK. As long as I have the vast majority of the content (name, IP address/hostname/FQDN), protocol, port, authentication method, etc. I can find a way to import it into something else.

    Please do not deliver the export feature such that the contents of the address book are not human-readable.

    Deliver that and I'll renew my subscription. A date as to when to expect the feature would be helpful as well.

    Jeff Hochberg supported this idea  · 
    An error occurred while saving the comment
    Jeff Hochberg commented  · 

    I ended up cancelling my subscription simply due to the lack of support for saving the console log. I absolutely love the product, but I'm not sure how such a basic feature was left out. I'm pleased to see "implementing" as the current status, but there's zero indication as to when the feature will ship. Termius folks - is there anything you can share with us?

  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Jeff Hochberg shared this idea  · 

Feedback and Knowledge Base