shanology:

usobuki:

chandri:

staff:

We recently learned that a third party had obtained access to a set of Tumblr user email addresses with salted and hashed passwords from early 2013, prior to the acquisition of Tumblr by Yahoo. As soon as we became aware of this, our security team thoroughly investigated the matter. Our analysis gives us no reason to believe that this information was used to access Tumblr accounts. As a precaution, however, we will be requiring affected Tumblr users to set a new password.

For additional information on keeping your accounts secure, please visit our Account Security page.

If you’re wondering why you were forcibly logged out of Tumblr with no warning and required to reset your password today, see above.

You know what would have been better than kicking me out and forcing a password change with no explanation, making your homepage look like a phishing site, Tumblr? SENDING OUT AN EMAIL OR SOMETHING.

Wow I’m glad that didn’t happen to me that’s shady as shit looking???

HEY GUYS THIS IS SUPER IMPORTANT:

I’ve already been forced to reset my password just now, but I’ve also seen several people on my dash who have basically lost their blogs because they had those blogs tied to defunct e-mail addresses they no longer had access to – and tumblr is giving no option for resetting your password without access to the e-mail they send you

If you haven’t been hit with the password reset yet – and it seems to be rolling out in waves – this would be a really good time to be sure your e-mail preferences are up-to-date in your tumblr account. If you can’t access the reset e-mail when they send it to you, you’re locked out. 

Hopefully they’ll fix this or come up with a work-around, but in the meantime, be prepared.

pastellieria:

daggerpen:

carnistprivilege:

i think my favorite thing about tumblr right now is that the queue limit is supposedly 300 posts but it’s actually not, it’s really 301 posts, and this is because the queue is an array and therefore obviously zero-indexed but tumblr isn’t using the length of the queue to determine when to stop adding posts, but rather the index of the post you’re trying to add, and the 300th object in a zero-indexed array has a fucking index of 299 but they don’t cut you off til after you’ve added the post with the index of 300 (ie, the 301st post) and that is such a simple, stupid, careless programming mistake and it would be SO easy to fix (it would literally be 1 line of code. one. line.) but the tumblr dev team obviously cbf to bother with it and honestly if that doesn’t tell you the level of care and attention to detail the developers give to their actual fucking product and the amount of emphasis tumblr’s management places upon quality assurance (ie, NONE) then idfk what would.  this website is such a joke jfc.  @ all aspiring programmers: don’t work for tumblr if you want to like, write good code or learn anything useful.  i mean i guess if you’re incompetent and wanna wear your tie as a belt this would be the ideal workplace for you but i’m just saying.

This is literally the first thing you learn in arrays which are like the second thing you learn in introductory programming and they fucked this up I’m screaming

@carpediemma