> I think the thing in the middle is taking to Twitter to complain immediately
What I meant is that flow of the events seem to have been something like:
- User received notification about impeding upgrade
- User replies to Ghost and tweets about the event
- CEO replies on Twitter
- ??? (Here it feels like some information is missing)
- Ghost terminates the users service
I cannot fathom that a user complains once via Twitter, and Ghost terminates their account. Has to be something else that have happened, otherwise this is way beyond crazy to do (from Ghosts side)
> I run multiple services, and I expect people to give me a chance to resolve problems before taking to Twitter. If they don't then I contact them to express my disappointment that they haven't done so, and then I have, on occasion, refunded people, returned their data, and terminated their service.
Same here, with lots of people complaining about bunch of different things and I have never, paying user or not, terminated their service unless I've asked before if I can terminate it or not.
Interesting to see that there are others who simply terminate users service when the user complains (gives feedback), wonder how that impacts the bottom line?