Replies inline -- Chris Forsythe
On Tuesday, March 6, 2012 at 5:43 AM, jlaw wrote: > Hello Chris > > I would not be too sure of the wisdom of thanking a contributor for > 'defending' you, whose sole purpose of commenting is to make inflammatory > misconstructions. A maxim in business, and one you should be well familiar > with is criticism and feedback (no matter how negative) is your best friend > as it provides opportunities to improve. I am in a service industry and I > receive negative feedback, regardless how unjust, but know how to convert it > into benefit. > He replied defending us. The sentiment is valid. Your tone was awful man, he's right that you were just attacking us basically. So ya, I thanked him. Your whole post was inflammatory from the beginning, so I'm not sure what you expected. This response was also inflammatory from the start. Bottom line, someone stood up for us since you decided to start off pretty awful. I was actually starting to reply when I saw your email, and decided not to in order to respond constructively instead of being angry. Here's my pot, I see your a kettle type of thing. There is no point in continuing this line of conversation though, it'll just degrade into uselessness, which it was already at even before I responded to try to right the conversation. > > You have a great idea in Growl and one you could further develop and selling > well with a bit of careful marketing and business acumen. I have seen it pop > up in so many corners of the internet and it has been a great companion until > the paid version, which essentially has not worked since. If you see a > notification and 'click to see..' pops up, you expect to click and in fact > see. Not even a double click works. Clearly, I am not the only one who has > encountered this bug and I suspect there are many more (probably who don't > have the time or patience to get through your feedback system. > > On the feedback topic: this (http://growl.info/reportabug.php) (open air > 'chat') seems to be the extent of it. A Growl user therefore can only get in > touch with you by joining yet another forum where you get #$%%^&*s like this > great 'supporter' above chiming in with worthless, vexatious commentary, > which does your product far more harm than good, not to mention the high > levels of irritation it produces in the genuine requester of support. (Google > Groups by the way is a horrible app, which includes non-functioning links in > emails, confusing, etc. etc.) > That's not the only way to contact us, which our contact page (http://growl.info/contact) goes to great lengths to explain. We're looking into other solutions than google groups. Do you have any suggestions? > > There has got to something wrong with that and I urge you to consider a > different avenue. Since the release and download of Growl 1.3.3 I have tried > to get in touch to request the problem be fixed but (now going from memory, > which is bit vague as the new release has been around a while now) was > frustrated by your cryptic feedback mechanism. Believe me, I share these > frustrations with dozens of colleagues that can't believe the ridiculous maze > that web developers weave and expect punters to follow - we just want to get > on with our job and want software providers to get on with theirs. I would > place $20 on Growl and would happily pay it, especially if it does the simple > thing it is held out to do (which it does not). > > Generally speaking, I spend a sizable proportion of my working life in my > sole practice dealing with software bugs, which at times is overwhelmingly > frustrating and it defeats the one raison d'être of software in a commercial > environment, namely to assist in increasing productivity. > > Now, are you willing to argue that I should prioritise my time in addressing > and elaborating what should be your, i.e. the software developer's, > responsibility? You find my frustration expressed here to be 'crass'? > You called us arrogant without even knowing us. That was probably the biggest problem with your email. You started out on a bad foot. Unfortunately what happened happened. I don't find your frustration crass. I find your tone crass. If you had formed your message in another way, you wouldn't have received the vitriol that you had. In all fairness email is a text based communication method, and you may have not meant to look like you were trying to be mean. But the other person read it that way, and I definitely read it that way. That's enough on this topic. I'm trying to get good feedback from you on what to do about it. But responses like this one really don't help. :( > > Anyway, enough time wasted already. There is a time difference since I guess > are somewhere in the states and I am in Australia so there is a time lag, > which I am familar with from dealing with emails 3 times a day with > marketcircle (http://www.marketcircle.com) who are in Canada. I would much > prefer it if you could address this problem with out dragging on in this > 'blog' thing and contact me directly by email. > Like I said, we have our nice contact page, that has multiple support options. But I'm the person who responds to the support address. You can subscribe to the google group via email and not have to look at the web forum at all. I certainly haven't looked at it in a long time. > > Many thanks for your time and I look forward to your constructive reply. > > > I look forward to a constructive response from you as well. I asked for specific answers, I didn't get that. > > On Tuesday, 6 March 2012 14:17:21 UTC+11, Christopher Forsythe wrote: > > I appreciate you defending us, especially when it comes down to sentiments > > like the crass one that we saw here. That said, it didn't really add much > > to the conversation. He had a valid complaint about finding it difficult to > > contact us, I'd like to explore that. His tone could have used some > > improvement, but at least there weren't curse words. > > > > The expectation of an immediate reply is kind of unreasonable, but people > > do have it now. I don't understand it really, but it is what it is. > > > > Chris > > > > On Sun, Mar 4, 2012 at 5:40 PM, TJ Luoma <[email protected] > > (mailto:[email protected])> wrote: > > > > > > On Sun, Mar 4, 2012 at 5:33 AM, jlaw wrote: > > > > > > > > I have precisely the same problem. > > > > > > > > To make matters worse, it's taken my ten minutes to work out how the > > > > hell to > > > > email the developers > > > > > > There's a "Report A Bug" button right in the app which will take you > > > to <http://growl.info/reportabug.php> > > > > > > There's also a 'Growl Web Site' link which will take you to <http:// > > > growl.info/ (http://growl.info/)> > > > > > > Both of them link fairly prominently to <http://growl.info/contact> > > > > > > Or you could Google 'growl contact' and use the first result: > > > http://www.google.com/search?ix=sea&sourceid=chrome&ie=UTF-8&q=growl+contact > > > > > > > > > > > > > and now I see your post is two days old, suggesting the > > > > developers have not even turned their minds to it, let alone fixed. > > > > > > HOW DARE THEY NOT HAVE FIXED A BUG THAT YOU REPORTED ON THURSDAY NIGHT > > > AT 8PM! > > > > > > DON'T THEY KNOW IT'S ALREADY 5:33AM ON SUNDAY?! > > > > > > If they don't shape up, I'd definitely threaten to fork the project > > > and hire your own more responsive developers to make a replacement > > > product! > > > > > > > > > > Sorry to sound terse, but I am getting really fed up with the arrogance > > > > of > > > > software developers. > > > > > > You're saying the software developers who are arrogant? > > > > > > Not users who are irate about one particular use case for the software > > > that keeps them from having to *manually* scroll back in their Twitter > > > timelines? > > > > > > Huh. > > > > > > > This problem has been apparent since the upgrade to > > > > 1.3.3. > > > > > > > > Alright Growl mob, time to show your paws. > > > > > > Oh yes, please do. I look forward to reading your angry blog posts. > > > > > > It's amazing how much entitlement you can buy with US$2. > > > > > > TjL > > > > > > (who is neither a Growl developer nor related to the Growl project in > > > any way, except as a user who has used this {admittedly imperfect} > > > software for years for free before it entered the Mac App Store, and > > > who happily threw a couple of bucks at the project to see it hopefully > > > continue.) > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Growl Discuss" group. > > > To post to this group, send email to [email protected] > > > (mailto:[email protected]). > > > To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:growldiscuss%[email protected]). > > > For more options, visit this group at > > > http://groups.google.com/group/growldiscuss?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/growldiscuss/-/ehg9UVQVBoYJ. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
