I didn't know that, I thought it was like on FireFox extension site (and others) where the dev can answer.
But anyway I understand it's quite impossible to answer to everybody when you have such a popular (and great) product :) Keep up the good job, thanks for your answers and time ! Jerome Le lundi 22 octobre 2012 14:51:08 UTC+2, Christopher Forsythe a écrit : > > I don't think you get it. We are not allowed to reply to the people there. > Period. Apple allows no developer to respond to reviews at all. I want to > help everyone possible where possible, but it's not possible. > > The only thing that you can do as a workaround is to google someone's > name, find them elsewhere, and then help them. But that's pretty creepy so > I won't do it. > > Chris > > On Mon, Oct 22, 2012 at 6:52 AM, Jérôme Cadet > <[email protected]<javascript:> > > wrote: > >> Sure I understand, but consider the App Store comments are a very >> important input for regular users like me. >> >> For example I decided to upgrade to Lion after reading so many complaints >> on the forums, waiting a long time, and then I read a detailed comment of a >> user on the App Store explaining what to do to avoid all the issues, so I >> took my chance and follow his advice (repair authorizations before / >> upgrade / don't do anything and repair again) and oh boy I was happy to >> have this advice because the first 10 mn after the upgrade was just a >> nightmare (nothing was working fine) and all went miraculously well after >> the new authorization repair : Apple didn't help me at all to take the >> secure way for this upgrade, there so many forum threads of people furious >> after the upgrade and no clear solution, I wouldn't have done it without >> this precise comment. >> >> So maybe you should consider spending some time to answer the App Store >> comments (at least "read the mailing list we solve all your issues !"), >> this is your *first* public window to the world ! >> >> Jerome >> >> >> Le lundi 22 octobre 2012 05:39:30 UTC+2, Christopher Forsythe a écrit : >>> >>> Keep in mind that there is no way for us to reply to reviews to try to >>> help the people complaining about things, even things they are very >>> confused about. Some people will rate you a 1 star if you aren't perfect, >>> etc etc. >>> >>> However, when we reply saying something is fixed, it's probably a good >>> idea to listen on our end. :) >>> >>> -- >>> Chris Forsythe >>> @The_Tick <http://twitter.com/The_Tick> >>> >>> On Saturday, October 20, 2012 at 1:39 AM, Jérôme Cadet wrote: >>> >>> Thanks for the answer, but the comments I can read on App Store are not >>> really convincing for v2 : issues at install, growl not recognizing apps... >>> with an average of 3 stars "only", pretty disappointing. >>> >>> Maybe I'm gonna wait some time and let my 1.4 freeze from time to time >>> in the meantime... or there are effective solutions for all these comments ? >>> >>> Jerome >>> >>> >>> Le vendredi 19 octobre 2012 18:06:55 UTC+2, Daniel Siemer a écrit : >>> >>> Growl 2.0 is out on the app store, and fixes a number of issues, >>> including the CPU spike/crash. Please upgrade (its a free update for >>> people who have already bought Growl) and see if this still occurs for >>> you (it shouldn't, but if it does, please let us know). >>> >>> On Oct 18, 5:03 pm, Jérôme Cadet <[email protected]> wrote: >>> > Hi all >>> > >>> > my growl is dying on a regular basis, it's eating a lot of CPU on a >>> > continuous time, I realize it when I come back home (let's say 1/2 a >>> CPU >>> > load), and the icon is not responding, if I try to open the menu it >>> crashes. >>> > >>> > I open it again, all seems ok. >>> > >>> > And then it happens again 2/3 days later. >>> > >>> > 10.7.5 / latest growl version >>> > >>> > Am I the only one ? >>> > >>> > Thanks >>> > Jerome >>> > >>> > Growl crash.rtf >>> > 55KViewDownload >>> >>> -- >>> 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/-/**RwBcqmIkhmQJ<https://groups.google.com/d/msg/growldiscuss/-/RwBcqmIkhmQJ> >>> . >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to growldiscuss...@** >>> googlegroups.com. >>> >>> For more options, visit this group at http://groups.google.com/** >>> group/growldiscuss?hl=en<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/-/XRAufzHZihAJ. >> >> To post to this group, send email to [email protected]<javascript:> >> . >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/growldiscuss?hl=en. >> > > > > -- > Chris Forsythe > @The_Tick <http://twitter.com/The_Tick> > > -- 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/-/qZRVV-y0-BUJ. 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.
