#eightyonekilograms

I was at the camera shop today and Sorely Tempted to grab a cheap 1.8 50mm for this but I ended up running with my 24-105 f/4, fortunately modern sensor tech is crazy good even at ISOs that would have ruined my old camera. Most of these probably won't work printed huge but they're perfectly serviceable at small-medium or online. I'll sift through these but here's some quick pulls with hastily thrown together edits to compensate for the noise. Definitely one of the situations where I think RAW really shows up, giving me a ton more latitude here. With a 2.8 on a Sony sensor you could really get the noise down.

I think if you're used to older cameras the one thing is to push your ISO way, way up. these are all 12800 or 25600, modern sensors (especially if you're not on Canon like me!) can do remarkable things even way up here, and you can push your shutter speed down a lot to get action solid in ambient light. These are mostly 1/200-ish, some as slow as 1/60 and some as fast as 1/400 depending on ambient light and vibes.

Flash I think would look pretty bad, flames aren't actually that bright so flashes tend to make them disappear, think taking a flash photo of a campfire, it just looks like ashes. You could maybe use a little flash to give you some breathing room on the face, or a continuous low-level light.

Also here's some video, both 30fps and 120fps slowmo. The raw video is a little better, here's an 8Mbps render of it.

(this group is Tribo Fuego)

@eightyonekilograms: it's going back through time.

Me: Whoa. I can already tell DoorDash's new tachyon-based delivery tech will be a huge hit.

---

5 min later

Me, increasingly concerned: you know, it's only a matter of time before DoorDash realizes they can build a computer based on a closed timelike curve, which means they'll be able to solve PSPACE-complete problems in polynomial time.

81k: was gonna say, they'll be able to send stock orders and troop movements back in time.

Ah I think I ran into this inadvertently once. What’s the repro?

It works when

the post you are reblogging is “susceptible”

the first paragraph in your reblog is block-quoted

you do not use the Markdown editor when writing the reblog

I don’t know exactly what posts count as “susceptible,” but my guess is that “susceptible” = “was created as an NPF post.”

NPF is tumblr’s “v2″ implementation of how they store posts on their backend, see here and here.

When it was released, you could only create NPF posts using mobile clients.  I’m not sure this is still true, but the trick only worked when I created the OP on mobile and not on web, so if we assume “mobile = NPF” (plausible) and “NPF means susceptible” (plausible), it all adds up.

Why do I think this might be an NPF issue, besides the observed connection to creating on mobile?

In the “legacy” storage format before NPF, posts were stored as HTML, and the structure of reblogs was represented in nested HTML blockquotes.  Additionally, tumblr has not moved everything to NPF -- as I implied above, some posts are “created as” legacy and some are “created as” NPF.  And they do some translation between the two formats in various places (exactly which places, I’m still hazy on) as posts are requested, modified, and reblogged across different clients.

The bottom line is, somehow this “trick” is hitting some part of their code that (rightly or wrongly) thinks it’s dealing with the old format where blockquotes encoded structure, and it’s misunderstanding a content blockquote as a structure blockquote.

----

The only mitigation I know of is to go into the Markdown editor and save the post “as” Markdown.

(I have no idea what this does behind the scenes.  If I try to retrieve the post in NPF through the API it looks the same as before (the NPF looks “correct” in both cases), if I try to retrieve it in legacy/HTML format it’s fixed, and its display in the browser is fixed.)

I'm the nooooo guy on the left aren't I

Was this is a pre-emptive apology or are you actually getting nasty replies /anons? Because you definitely do not need to apologize for having a high-functioning day. This site can be such a crab bucket sometimes.

Eh, it’s pre-emptive.  

It feels like I’m being that smug asshole who’s all “mmmyeeessss, what did you do today, I cured cancer and climbed the entire Appalachian trail and then stopped for a bite to eat at Gordon Ramsay’s”. Like I said, humblebragging. 

That’s not the kind of person I want to be.