@justintstanley I received hundreds of emails every day, of which I only read about 10%. The only ones I would *always* read where the ones with recall attempts.
@niklassbe @christianvozar @TrevAustin@_joemag_ Because you're a kid (or really, anyone) who made a mistake, and thought you were adding numbers, with nothing warning you that you aren't.
If you had given me 200 guesses about which company just pulled a “hey fuckstick, we’re turning on a chargeable service for your account because fuck you” I would not have guessed @awscloud.
Clearly times are changing and so must my impressions and opinions about the company.
@QuinnyPig@Dropbox Wife found she had to upgrade in order to access a file someone shared with her ( ¯\_(ツ)_/¯ ), so she did. Later cancelled Pro, but lost access to everything, with no obvious way to get it back. Given all the other viable options, it wasn't worth figuring it out.
@mvandemar@feliciaday@PlanetComicon In a noisy restaurant the other day nobody could hear me, so I closed-captioned myself by downloading a transcription app to my phone & hanging it around my neck. So yeah.
@nathankpeck@kreddyio@rakyll All loggers should be non-blocking and be willing to discard messages if they would block the application or consume too much I/O. In reality, none of them are. If you really require 0% loss of messages, then it's not logging, it's a business-critical function.