3 ms·
I'm assuming that hamburglar is talking about the backend that Tumblr relies on, and it's not pretty. They had big troubles with stability at one point last yea
by nwh 13y ago
I'm assuming that hamburglar is talking about the backend that Tumblr relies on, and it's not pretty. They had big troubles with stability at one point last year, including a typo in VIM on a production server that spat out all of their API keys to every user.
https://gist.github.com/zachinglis/29c5c5970d1f3313abd1/raw/9fdb9a15feee6528a43ea3c7b16dc5423b01f92b/gistfile1.txt https://gist.github.com/zachinglis/29c5c5970d1f3313abd1/raw/...
- graue 13y agoI've seen that leaked PHP code before... does anyone have a link to the full story to go with it? Was it really only last year? The code is scary in so many ways. I assumed it was from Tumblr's early days and they long since fixed it up.
- nwh 13y agoI'm not sure if there is any official story, but it is clearly somebody messing up with `vim` on the production servers. They've tried to go into insert mode, failed, and not realised their mistake until after they've written the file. If I remember correctly, this output was the response to every tumblr request for about 15 minutes before anybody noticed and fixed it. i?php