one thing to rmbr guys is that tumblr HAVE walked back updates before. multiple times theyve either walked back updates or added a toggle to let you reverse to how it was before. they ARE bulliable

seen from Poland
seen from Brazil
seen from Russia

seen from Ecuador
seen from United States

seen from Türkiye

seen from Singapore

seen from United States

seen from United States

seen from United States
seen from Algeria

seen from Argentina
seen from United Arab Emirates

seen from United States

seen from United States
seen from United States

seen from United States
seen from United States
seen from United States
seen from Russia
one thing to rmbr guys is that tumblr HAVE walked back updates before. multiple times theyve either walked back updates or added a toggle to let you reverse to how it was before. they ARE bulliable
I feeeeeel like tumblr isn't impressed with my last drawing because of the amount of skin showing? Hmm.
About my fake staff ask
How I made it:
Currently, the tumblr API just... lets you make a post in which you "reply" to an "ask" from an arbitrary user, containing arbitrary content.
In tumblr's Neue Post Format (NPF), responses to asks look similar to other posts. The only difference is that they have a special entry in their "layout," specifying which part of the post is the ask, and who it is from.
Right now, if you try to create an NPF post with this kind of layout entry in it, it just works! You can use this to make an "ask" from anyone, containing anything, and answer it.
This is a huge bug and presumably will get fixed sometime soon?
How I discovered the bug:
Weirdly enough, I find out about it while trying to improve @nostalgebraist-autoresponder's alt text features this past week.
As you may have noticed, Frank now writes alt text differently, with more clarity about which pieces are AI-generated and what role they play.
While making this change, I found myself newly frustrated with my inability to use line breaks in alt text. The API used to let me do it, but then it stopped, hence all the "[newline]" stuff in older alt texts.
After poking around, I found that you can use line breaks in alt text on tumblr, and you can do this through the API, but only if you create posts in NPF.
Frank creates posts in legacy, not NPF. This has been true forever, and it works fine so I've had no reason to change it.
Fully rewriting Frank's post creation code to use NPF would take a lot of work.
Right now, Frank's language model generates text very close to a limited subset of HTML, which I can send to tumblr as "legacy" post content basically as-is. To create posts in NPF, I'd have to figure out the right way to convert that limited HTML into NPF's domain-specific block language.
I wasn't going to do that just to support this one nicety of alt text formatting.
"But wait...", I thought.
"Frank is already making these posts, with the alt text, in legacy format. And once they exist on tumblr, it's easy to determine how to represent them in NPF. I just fetch the existing post, in NPF format."
So all I need to do is
Have Frank make the post, as a draft, with the alt text containing "[newline]" or something in place of the line breaks I really want.
Fetch this draft, in NPF.
Create a new NPF post, with the same contents that we just fetched, in whichever state we wanted for the original post (draft, published, or queued).
Delete the draft we made in step 1.
This was convoluted, but it worked! I patted myself on the back for a clever workaround, and went on to do other stuff for a while...
...and then it hit me.
In the case where the post was a response to an ask, Frank was doing the following:
Responding to the ask.
Fetching the response in NPF.
Creating a completely new post, identical to the response -- including the contents of the original ask.
Deleting the original ask.
Meaning, you can just make asks ab nihilo, apparently.
So after a few more tests, I went and made the @staff ask, as one does.
Unfortunately, once the bug gets fixed, Frank's newlines-in-alt-text solution won't work for asks anymore... oh well, it wasn't a big deal anyway.
love that the reddit -> tumblr migration is the surprise success story of the collapse of social media. i wouldn't have predicted that these two species would get along either! but it does make a kind of sense, yanno?
like, once freed of the upvote/downvote pressure to be terminally right on the internet and set loose in the open pastures of purely recreational pvp, it turns out redditors and tumblrinas have plenty to bond over: love of niche topics pursued at great length, doing bits, The Deep Lore... and, of course, the most topical shared interests of our current hellscape: spite, defiance, and malicious compliance
@staff really said "these freaks' favorite holiday is the ides of march, let's enable pvp for april fools"
Don't mind me, just mourning my p*rn blog of over 8 years that staff just deleted without warning, while I was reading it, without giving me time to back it up or say goodbye.
And if any of you says something along the lines of "you got the chance to do all that in 2018", what, you think my blog didn't change at all in the last 5 years? Show me a permanent state of the self. That which I backed up then is a shadow of an earlier age.
I named it after an inside joke between some high school friends and me. I don't even remember their names, but I remember the joke.
What's it like to only live a virtual life? Do you long for being touched knowing you'll never be able to feel it like us humans do?
I think I've gotten better at having emotions that don't involve immediate touch
What's this new tumblr bullshit where when I search a blog, it will return results in random chronological order? Like, hey, I'm trying to find the last previous mention of this topic from a few days ago the poster is referring to to follow the conversation, not a random piece of fanart from 2016!!!