biggest thing you need to do to improve support is stop sending mailings from a no-reply email address. Replying should create a support ticket automatically if the email it came from is associated with an account. Further verification could be required depending on the request.
Thank you for saying this. I feel like this is a major problem with a lot of services. If they care that little to send me an email from a no-reply then how do they expect to keep customers who want to reply to the same person. There is absolutely nothing more frustrating then having 5 different people work on a similar ticket and repeat yourself over and over.
just a happy Sumologic user, saying hello and Thanks! Most of your product is great (I am ex splunk user)... The biggest complaint is that I can't cmd+click to open anything in new tabs as everything is so JS crazy front end.
overall the pattern matching stuff is pretty cool. Also, would like a see raw logs around this for when I am trying to debug event grouping errors based on the starting regex.
E.g. With LogReduce you can click on group and see log lines that belongs to it. IS that something that solves your problem, or are you looking for something else.
Feel free to send me an email (it is on my profile).
I find this surprising seeing as cloudflare blocked me on shared wifi while traveling internationally from accessing many sites, claiming it was to prevent email spam. They were blocking more sites than over zealous hotel and government internets. When I started a thread about how they were blocking from a significant percentage of hotel and coffeeshop wifi's in various countries their response was find other wifi. Really seems like you need to turn down the filtering.
I am pro continuous integration, continuous delivery to staging. I think it takes extra care to do continuous deployment to production. There needs to be a number of systems in place some of which @mattjaynes mentioned others really depend on having a very solid and accessible deployment pipeline.
based on the old "calendar about nothing" site that eventually became Github's streak feature. I built http://nothingcalendar.com/ to track working on one of my goals every day. Haven't worked on it for years, but still works well for tracking simple streaks.
Heroku for static content is always terrible, I am always surprised at how many people host static sites on Heroku, it is really easy to host of S3 buckets and it is much faster for static pages.
keep emailing and asking on the message boards. Fitbit is a bit slow to get back to people but normally pretty good about it. I built ruby apis to access fitbit before they had an API and a android app prior to them releasing their own. I was in email contact with them the whole time and they were willing to help me out and give me beta access to the api before it was public.
I love fitbit, and hope they allow users to at least download the detailed personal reports.
I would say diggs attempts at manipulating the front page and banning people, blocking posts, and unfairly pushing some content to the front helped kill it. When I lost faith in the democracy of Digg I just stopped going and spent time with my votes elsewhere (reddit)
