fffinnagain

[fffinnagain]

The scale of baby hummingbirds vs a human hand

#itty bitty birb

[fffinnagain]

A very very minor thing I have been curious about for a while, and I'm finally asking: why do you calculate queue posting times the way you do? For example, if I set my queue to post 3x a day, naively I would expect it to post every 8 hours. But in reality it posts every 6 hours with a 12 hour gap between days. Why complicate the math like that?

Answer: Hello @circumference-pie!

Buckle up y’all, it’s story time again!

First: nobody who works at Tumblr right now was a part of the work of planning the default queue implementation, which was more than ten years ago. So the full story behind “Why does it work that way?” has unfortunately been lost to the sands of time. All we can do is tell you how it works today and surmise some reasons why. The queue is actually a very clever system and part of how it works explains some of why it works the way it does. Also, there have been attempts to do what you ask—we still have “Queue 2.0” available in your Tumblr Labs settings, which tries to get closer to how you expect things to work.

Anyway! How the queue works today is not actually a queue in the traditional sense. There is no single list of posts that are in “your queue”. Instead, when you “Add to queue” after creating a post, we’re actually scheduling it to post at a future time, as if you had used the “Schedule post” option instead. We’re just calculating that time on your behalf when you use “Add to queue”, based on your settings, and how many other scheduled posts you have already. We use a secondary “index” model, called “ScheduledPost”, to keep track of posts you have scheduled on your blog. We do mark the ones that are a part of “your queue”, but the data model doesn’t keep one list of your “queue” per se.

You can see this in action on your blog, hiding in plain sight. If you add a bunch of posts to your queue, and then schedule a post for a specific future date, you’ll see both in your blog’s “queue” list, side by side. Because technically to us, they’re the same thing: queued posts are really just another kind of scheduled post, relying on the same always-running service to publish scheduled posts across all of Tumblr. Here’s a fun fact: we typically have about ~14.5 million future posts to publish from this list at any given time and are publishing hundreds of these scheduled posts every second.

So when you’re adding a new post to your queue, what we’re doing behind the scenes is starting at the beginning of your “day”, and creating time slots based on your queue settings. If a time slot is already filled, we move on to the next one. That’s why the default queue scheduler works how you describe—we’re trying to fill those “slots” based on the start of the day, rather than trying to divide the calendar day evenly. This just makes it much simpler for us to understand, scale, and predict when our “peaks” will be. At peak times, the publish-scheduled-posts service is publishing tens of thousands of posts in a manner of seconds. We did rewrite that post-publishing part of this architecture a few years ago to improve its efficiency and solve a lot of “lost post” bugs, but we didn’t change how “Add to queue” works.

However, the Queue 2.0 project available in Labs was an attempt to change the queue system to work as you expect—instead of starting at [beginning of day] and creating enough slots to fit [number of slots] every [number of hours], it tries to divide the calendar day into [number of slots] and fit the result back to the original algorithm’s mapping of the day. We never productionized this alternative approach, because it has a few bugs that some blogs hit in extreme cases, and we’ve never had time to fully fix them. It also can cause a bit of weirdness when time zones diverge, like with daylight savings time. Also, a lot of people prefer the default algorithm, and we haven’t thought of a nice way to transition everyone from one to the other. So for now, both options exist, and you can choose which algorithm for queue-slot-generating you want to use. We hope that makes sense! 

While complicated, it is a great example of a system built by engineers to make sense and be scalable and predictable. But sometimes these kinds of systems, while clever, aren’t very intuitive to understand without digging into how they work.

Thanks for your question, and keep ’em coming. 

#how #queue

[fffinnagain]

once i accidentally said "I love you" to EVERYONE AT AN ACADEMIC SOCIETY'S GENERAL MEETING, in the middle of a comment on plans for the next year, and while it was kind of true, and definitely only platonic, I have not been ok since.

Reblog if you think it’s okay to platonically say “I Love You” to your friends

[fffinnagain]

The National Park Service has released crochet/knit patterns! The triops is my favorite.

Here's their Ravelry:

But wait there's more if Ravelry isn't your thing:

#omg #to crochet #a mountain goat #or fish

[fffinnagain]

My face is having uncontrollable spasms. Great. It hurts really, really, really bad.

I think part of why I have trouble explaining pain to the doctor is when they ask about the pain scale I always think “Well, if someone threw me down a flight of stairs right now or punched me a few times, it would definitely hurt a lot more” so I end up saying a low number. I was reading an article that said that “10” is the most commonly reported number and that is baffling to me. When I woke up from surgery with an 8" incision in my body and I could hardly even speak, I was in the most horrific pain of my life but I said “6” because I thought “Well, if you hit me in the stomach, it would be worse.”

#super helpful references #health scales

[fffinnagain]

before the poll, a quick definition of terms:

"mutual" - you found this post from a mutual (on their blog or your dash) "following" - you found this post from someone you're following, but who isn't following you "random" - you found this by scrolling through someone's blog, who you don't follow. this includes people following you "For You" - you found this on the For You page "recommended" - you found this in a "Check out these blogs" popup, or a "recommended" post when looking at a different post "other" - you found this post some other way. comment how? "reblog ✅" - you're going to reblog, queue, or schedule this post "reblog ❌" - you're NOT going to reblog, queue, or schedule this post

with that out of the way:

#curious poll

[fffinnagain]

A surprisingly helpful bit of social maneuvering I've figured out from trial and error: Throughout your life, you are going to need things from people. Often, it's going to be on a deadline. And when that deadline passes, you generally want to know what's going on. So, you need to ask them.

There are two kinds of people, broadly, in this situation. The Shameless will tell you what the holdup is, with absolutely no regard for if the reason is "good enough". This is actually very helpful, because you get the real reason immediately, and can start working on a solution.

The Ashamed is trickier. People who are Ashamed are people who were often told they were giving excuses when they were trying to explain, and they'll often avoid you until they solve the problem on their own. This causes them and you a lot of stress, and often takes a lot longer to solve.

Long term, the strategy for dealing with people who are Ashamed is to provide a supportive environment where they're comfortable sharing any problems they're having with getting things done. But, there's a way to at least partially short-circuit that:

Provide an explanation for them.

One example might be "Hey Susan, I noticed that I don't have your report yet. Are you busy with other projects?" The readymade explanation signals that you're willing to accept an explanation, which is the big anxiety point.

Sometimes, you still won't get an honest answer- especially if the honest answer isn't "good enough" by the standards of the person who traumatized them. But, I've found that it often at least gets you a lie that lets you give them some slack or work around the problem.

Let's say that Susan has actually completely forgotten that she needed to do the report. She's horrified at herself, and completely unwilling to admit the real problem. But, she can now safely reply with "Sorry Jennifer, I've been swamped, and it got lost in the mix. I can have it to you in two days. Does that work?"

From there, so long as Susan gave an estimate for when she can actually do it, she and Jennifer can hash out a solution.

It's not a perfect solution, but it works astonishingly well for how small of a change it is.

#wise words

[fffinnagain]

"don't mass reblog/like :/" coward. fool. somebody just went through and liked and reblogged 64 things from my blog in the span of half an hour at most. and i've never felt more alive in my life

#love and like and reblog

[fffinnagain]

sometimes I get stuck on a bird because there are too many amazing photos and I can't decide which one to pick

bulk crested caracara post to help me along (it worked! decision made)

#like 😭😭😭 #they are holding hands #or feets #birb

[fffinnagain]

btw this isn't a vague/subtweet (post?) or anything but just so y'all know, there's a way to mark things as "inspired by" on ao3

you don't have to just put it in the notes!! very cool under-utilized feature

#acknowledgements #ao3

[fffinnagain]

1926: “This girl has all of [the] trends and she’s not loath to wear them at once: bell earrings, a dog collar worn as a necklace, a large beauty spot on her cheek, an ivory cigarette holder, a design to cover the vaccination mark on her arm, heavy bracelets, an anklet, a photo of a boyfriend on her stocking, an anklet watch, fancy garters worn below the knee and a mirror fastened to her wrist.”

Waiting for wristwatch anklets to make a comeback

#all this #all that

[fffinnagain]

not disagreeing about the inevitability of teens today discovering recordings of artists that other living generations feel ownership of. But let's also recognise that recordings of music being available for discovery is kind of new, like species-history wise.

We haven't evolved culturally to tolerate these generational frictions because music hasn't been preserved this way, been ubiquitously and independently retrievable, for more than like two or three successive generations?

So yeah the whiney millennials are being hypocrites but they are also the first to get to be hypocrites this way, having discovered on napster their parents' records and their cousins' cassettes. It's understandable that they aren't prepared to recognise the loop.

saw a grown woman on tiktok snidely calling gen z the christopher columbus generation bc someone’s fifteen year old son ‘thought he’d discovered weezer’. newsflash every generation finds out about the music of the previous generation at some point it comes free with being fifteen. being annoying about music also comes free with being fifteen. a kid saying yeah i’ve just found this band nirvana have you ever heard of them should be a thing of joy

#music technology

[fffinnagain]

Bittern at the grocery store

#birb #comic #reasonable pursuits

[fffinnagain]

i cannot stop laughing at send no pee

[fffinnagain]

Patreon

[fffinnagain]

This is going mildly viral on tik tok so I figure I’d repost it here. (Follow me on ig for show announcements and please book me to perform at your schools!)

#side eyes primatology #hoh #lol

[fffinnagain]

AI on fiber arts. How much of this could actually be knit or crocheted?

#fiber arts #ai take on fiber arts #still can't find a source