#and you can message and ask questions and stuff

[thankskenpenders]

Today we got some news regarding a big change for the Ian Flynn's Q&A podcast, the BumbleKast. As outlined in a blog post by Ian, starting in 2025, all Sonic-related questions submitted to the show will first need to be screened by Sega. (I have to assume this is also why Ian announced they'll no longer be doing live Q&As starting next year.)

Frankly, I can't say this is particularly surprising.

While the BumbleKast is ostensibly a podcast about Ian's work as a freelance writer for all sorts of things, and also just a place for him to shoot the shit about stuff he likes, he's still predominantly seen as The Sonic Guy. Sure, he also does a bunch of other freelance work for other series, and original comics like Drogune, and he's also the narrative mastermind for the whole Rivals of Aether franchise these days, but it's his insights into what goes on behind the scenes with Sonic that people really care about. Your average Sonic fan can't just go up to Iizuka or whoever and ask him a question about the current state of the lore, but Ian's inbox is always open.

Because of this, I've thought a lot about the BumbleKast's place in the fandom and The Discourse in recent years. Ian wants to be as open and honest as he can about his work, and I think that's admirable. To me, hearing about creators' struggles and the shit they go through just to get a story out the door tends to make me sympathize with them more. Sometimes a story just doesn't turn out as well as you'd hoped, but you're on a tight deadline and all you can do is move on to the next project. I've even softened a bit on Penders over the years as he's shared more about the absurd situations and odd creative demands made behind the scenes at Archie. Unfortunately, not everyone has that mindset.

Ian's basically always had obsessive haters who were eager to take everything he says out of context to try and stir up shit, but that used to be contained by the niche nature of the Archie comics. Most of the fandom didn't give a shit about what Ian was doing with Sonic and Sally's love life or whatever. Most of the fandom wasn't even reading those comics. But Ian's gone from being a writer for a non-canon spinoff comic, to being the initial lead writer for the first ever canon Sonic comic series, to being the new main writer for the games themselves as part of the official Sonic Lore Team. Way more Sonic fans care about his work now, and when he's so open about his work that makes him an easy scapegoat.

It feels like damn near every week on Twitter Ian's personal trolls have posted yet another BumbleKast clip out of context to rile up the fandom and make it look like he has no idea what he's talking about or like he has some kind of agenda. And, unfortunately, people often fall for this. Of course, it also goes the other way, with people more sympathetic towards Ian taking things he says about Sega and framing them as proof that Sega has no idea what they're doing with the brand. Which, well, let's be real, isn't always the most unreasonable thing to think, given Sonic's rocky history. But I'm surprised it took this long for Sega to start paying more attention to what gets said on the BumbleKast when fans use it so regularly as a source of drama.

I've also often felt that they just need to be WAY more selective about what messages they respond to on the show. Questions Ian can't actually answer due to NDAs, questions that are borderline incomprehensible, "questions" that are really just fan ideas. And the haters, oh, the haters. Ian does not need to put up with angry rants about how he should make SonAmy canon or what the fuck ever. Even if Ian's willing to put up with it, as a listener it can make the show just super unpleasant at times when someone aggressive pops up with an inflammatory question. There have been entire BumbleKast Mini episodes I had to skip because they were just obsessive critics of Ian's paying to grill him on a dozen different things and treat him like an idiot.

But at the same time, I get why the show got to be this way. It's become a part-time job for Ian with multiple new episode a week. Given how piss poor the pay tends to be for freelance writers, I can't really blame him for wanting to keep this secondary stream of income open, and to not have to refund people left and right for rejecting their questions. The man's got bills to pay. (And so does Kyle, for whom managing the BumbleKast seems to have become a full-time job.)

I dunno. The man's got the patience of a fucking saint. I would've quit the franchise if I was in his shoes, with people wishing he would die for shit like minor disagreements over Sonic's characterization or him misremembering an obscure old lore thing. While I do hope that Sega doesn't keep too tight of a leash on him moving forward, and I hope that he's still able to speak his mind about his work, part of me also hopes that having to be much more selective about Sonic questions results in less bullshit like this.

[dogs-have-fallen]

Welcome to my Blog !

( blinkies at the end , minor flash warning )

Hello critters of Tumblr ! This is my updated intro post :3 Here , you will find information about me , as well as what my content is / will be , and my DNI

My name is CODY ! You can also call me Coy or Dog ( and any variation of such ) I use he / it / thing / pup / mutt and really any canine related neo pronoun .

I identify most with the therian + transspecies labels ! I am a coydog , specifically a coyote mixed withh a golden retriever . I also identify with the canine / candid umbrella as a whole . I am also an anomaly and a robot !!

I have been awakened since 2017 , so at the time of posting this I have been a semi - active part of the community for seven years ! How cool !

I am 19 years old , but no worries ! This is not an 18 + blog . If I do decide to post more adult content , I will either explicitly state MDNI on the post or I'll make a side - blog !

I do ask that if you wish to DM me that you are at least 16 years old . This rule is quite lenient , if you are younger than 16 and have questions about my identity or therianthropy in general , feel free to message me ! For regular conversation though , the 16 + rule applies .

Things I WILL post :

I will post my art ! It will mostly be art relating to my identity , and I hope to one day start taking commissions or requests !

I'll also post most , if not all, of my kin related thoughts

Things I WILL NOT post :

NSFW content without proper tags

Personal content outside of kin related things

DNI

Please do NOT interact if you are a proshipper , if you are pro - fiction , are an NSFW only blog , anti - therian , anti - furry , anti - transspecies , or anti - regression . DNI if you are radqueer or transID ( trans - race , age . abled , etc ) and other general dni stuffs

Additionally , I really don't care for system discourse , and since I am not a system I will not take a stance on non - traumagenic systems .

DO interact if...

You are a therian , a furry , an age or pet regressor ( I will tag content not safe for regression ) , an artist , are alternative , punk , and all the cool things !!

I hope you enjoy your stay !

blinkies from sunanthrope here on tumblr !

[lesbianphan]

Review of ii please? 🎤

Hi Cal! Took me a while to get to this message cause I felt like I wanted to write a longer reply.

I feel like I need to preface by saying I'm not a big tour fan in general when it comes to youtubers. I know Dan and Phil do it like no one else ever dares to do, but I still don't really enjoy the format very much, especially since it feels exclusionary to people who can't be there when the youtube channels get dead for tour reasons (which means I might get more annoying during tour again whoops). So prefacing as well with the fact that tatinof makes me want to die inside and is maybe my least favorite thing they've ever done, I didn't have that high expectations for II.

That being said, I liked II way more than I thought I would! It's like the teenage version of dnp content, I suppose! TATINOF felt like it was made for 10 year olds, and even though introverts didn't feel mature or adult like I hope TIT will be, it was still fun enough! Phil especially did much better with this format (and maybe some more experience) and didn't make me want to die from second-hand embarrassment as much asdkj (sorry I promise I love him, hard to watch him act though).

I found it to be like an internet variety show of sorts, and was overall pretty enjoyable to watch. It felt more Dan and Phil than overly scripted TATINOF. They vibed more with the public, they felt more comfortable in their skin and on stage. Overall a better performance, and a more interesting show imho. It was still a litttlleeee too long imho, their shows tend to drag on a little too long for my taste (even WAD, which I absolutely LOVED, could be much shorter to pack more of a punch, so the message doesn't get lost in the amount of content in it).

I find it funny that it was supposed to be the last Dan and Phil thing, because idk if it's because I'm watching it now, but it just has middle child energy. It didn't feel like an ending at all to me! I found the theme interesting as well, about giving people what they want / doing what they want, but once again it might have been better communicated if the show wasn't as long.

Tldr: I really liked Interactive Introverts way more than I expected, I think they did a good job with it even if it does have some transitional energy that is hard to explain, and it's very of its time, as all of their projects seem to be.

I feel more ready to face whatever the fuck they'll do during TIT now that I've seen all their shows, but I do hope they throw out the booklet and let loose a little more on this one. I'm intrigued to see what an actual adult Dan and Phil show looks like (not onlyphans lol).

[boxwinebaddie]

an uncle nina check in <3

hi team! thanks for sticking around! i know my blog isn't always the most exciting and enriching place in the world in terms of content, but i am very /content/ to have you all here. <3333

i promise, oddly enough, i have A TON of inspiration and ideas for all my weird styles ( if you're curious about anything please lmk! i've been trying to flesh out my aus out lately ), i've just been in a major bummer depression era lately, so it's hard for me to get my asks done and i'm having a hard time committing to finishing my writing. :<

i think it's because of stress and my bipolar, but i am trying to get back on the horse! ( are we all laughing at the idea of me trying to get on a horse? i'd start crying help city girl fail moment for me ) yeehaw!

and while, unfortunately due to the instability ( fabulous legendary iconery ) of my pretty girl popstar personality, i do not know whether i will be answering almost no questions or one million, regardless of that, i just wanted to let you know, i'm still here, still kicking my feet, twirling my hair, cooking...i'm just really trying not to force myself to put out anything i don't like...and only do what makes me truly happy.

however, nothing, my dear sweet e-darlings...

makes me happier than coming home to all of you. <333

so thank you for flooding even the darkest corners of my life with bright light, supporting my phantom fics and being wonderful,

uncle nina xx

[bangcakes]

.

[rachielynne728]

I’m thinking I seriously need to write down the scene in my head for my novel because I’m so excited about it! Send me some encouragement please!!!!

Ooh, I can't wait to read your novel!! I have faith that you'll be able to get the scene down

[pepprs]

idk how to reconcile my new self with my old self. also i fucking hate waiting. GRAGHHHHHHHHHHHHHHH

[quietmarie]

What is Async Anyway?

Explaining async/await and general concurrency concepts in programming languages.

A lot of modern languages have async/await syntax built directly into them, and the construct can be extremely useful. Examples of languages that include these concepts are JavaScript, C#, Python, and Swift, and even modern relatively low-level languages like Rust have this syntax. Even though it's usually thought of as a more advanced feature, I think it is really not that hard to use once you get the hang of it, and it is super useful and rewarding when you really understand it.

This is going to be a bit of a long and pretty technical post, but I hope it can give you some confidence to know what async/await really does when you use it, and maybe it can help you use it more effectively. Keep in mind that I will not be able to go over everything in super deep detail, and that I am going to simplify stuff, but it should give you an idea how these systems work.

I am a little curious about eventually following this up with a post looking at how these systems compare under the hood in different programming languages, so let me know if you'd be interested in that.

Big post under the cut.

Parallelism and Concurrency

Computers today can do many things at the same time. And I mean that literally: in one instant, a modern CPU can be working on multiple instructions. That's because a single CPU has multiple cores that can all execute code (mostly) independent from each other. This is called parallelism, and the way we as programmers interact with that is through threads. Most programming languages, especially "lower level" ones, have a way for programmers to create a thread that will run some part of your code. Creating a thread is telling the computer that it can, and should, run the code in your threads in parallel (although various systems such as the OS still have discretion over when and if that actually happens).

Parallelism is not quite concurrency tho. Where parallelism is about your computer literally doing multiple things at once, concurrency is about your computer doing multiple things, but not at once. With concurrency, you kind of pretend you're doing a parallelism. But in reality, stuff doesn't happen at the same time. Instead, your system (runtime) does some work on task A a bit, then on task B, then maybe again on task A, etc., but doesn't work on the two at the same time. So, in a concurrent system it might look like task A and B are progressing simultaneously from the outside, but work actually only happens in sequence.

Let's Talk About I/O

I/O stands for input/output and describes data in your program that comes from elsewhere, or that gets sent elsewhere. So for example, user input is I/O. And similarly, a web request can be I/O, whether you send it or receive it. So let's use that as an example: you send a web request to some API to fetch you the cutest bunny images and facts:

But the service is taking its sweet time to respond.

Fact: Loading bunny fact…

With how we did it here, we halt execution of the entire thread until the response comes in (at least in most languages, more on that later). In this case, we call get a blocking method because it, well, blocks the thread without actively doing useful work.

What if we could instead use the thread for other tasks instead of just sitting there, twiddling our thumbs and waiting on the server? This smells of concurrency…

Callbacks

Callbacks are a way for programmers to avoid that period of thumb twiddling. The new getWithCallback function now returns immediately, but it doesn't return a value. Instead, we have to register the code we want to run once the server responds with the function:

The function we pass to getWithCallback is called the callback, and it gets called by the client* only once the response arrives. Oh look, here it is:

Fact: A rabbit's life span is about 8 years, though sterilized rabbits (those who are spayed/neutered) can live as long as 10-12 years.

*"The client calls it" is a big simplification, there might be a lot more stuff happening here. But the important bit is that the client magically does not need to block to wait for the response.

Promises and Futures

What JavaScript calls Promises and what a lot of the other languages call Futures is essentially sugar sprinkled on callbacks - it makes our callback code a little nicer. Callbacks can commonly create a concept called "callback hell", where you have to call a function that takes a callback inside the function that takes a callback inside the function that takes a callback…

(Code modified from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises)

To avoid this, functions now can return a Promise instead of taking a callback. Promises represent the promise that, while a concrete value might not exist right now, it will in the future. Once the value exists, we say the Promise resolves. The code above with Promises would then look like this:

It still doesn't look perfect, and there are things you can do to make it look a little nicer, but it's so much less nested. The callback in the then function will be called once the value is ready, and the callback itself can also return a Promise. The then function then returns a Promise which will get resolved once the future from the callback is resolved. Many other languages have a concept similar to JavaScript's Promise, and it's often called something like Future or Task (because it would be too easy to have consistent naming across languages).

Now keep in mind neither of those solutions above are really "concurrency" in the definition we used above. This is because the thread we call, for example, getWithCallback on still completely belongs to us. We could keep using it, and we would not get interrupted to execute the callback. Depending on the language and runtime, the callback might get executed on a different thread, or the runtime might have to wait until we are completely done with what we were doing to then use our thread to call it. The same thing goes for the callbacks in the then method of promises.

Async/Await

And async/await is just some sugar and magic fairy dust on top of Promises (or Futures or whatever). It makes our code look like it should be blocking, but in reality it isn't. Here's what our bunny image code looks like with async/await:

So here, a couple things happen. First, the Promise is created and the web request is initiated. Then, the Promise is awaited. For that, (if the Promise is not resolved at this point already,) the task first yields, meaning it tells the runtime that it is not doing any useful work at the moment, and that the thread it ran on can be used for other tasks. The runtime then makes a note of where to continue execution when that Promise resolves, and looks around for other tasks that currently need executing to put them on that thread. After a while passes, the Promise resolves, and once the runtime has some resources available for us (maybe because another task just yielded), execution on our original task is continued with the API response.

Fact: A rabbit's teeth never stop growing! Many people believe they need to chew to keep their teeth short. While they do enjoy chewing, it's the normal wear from where their top and bottom teeth meet that keeps a rabbit's teeth short.

This is more in line with the concurrency we sought out above. We can interleave other computations while our task is still running, but during times where it is not doing any useful work. (Still, because you may have multiple threads your tasks can run on and move between, it might not always be 100% technically accurate to call this system concurrent.) This is also why it is important to not block for long in async contexts: if you're hogging the thread for too long, you're stopping other tasks from progressing and throwing a lot of the benefits you gained from doing it concurrently in the bin. Most async runtimes will give you some option to run expensive or blocking code elsewhere, so that you can keep the benefits you gain from async.

So that's the explanation what async/await does, and the broad strokes of how it works. If you have any more questions regarding the topic, feel free to ask! I think it'll be fun to occasionally write a longer post on interesting things I've learned, so if you have topic suggestions, don't be afraid to tell me!

Further links and sources

Don't Block The Event Loop! - Why you should avoid blocking in Node.js, and what pitfalls to look out for.

I got the bnuuy images and facts from the animality API. The licenses on the images are not super clear, but I'll assume it's okay for me to use them here with credit because it's an open API.

I lifted the definitions and some of the explanation for parallelism and concurrency from Steve Klabnik's talk on Rust's Journey to Async/Await. The talk is more technical and very focused on Rust, but it's a great talk.

I referenced the mdn web docs at various points, they're a great resource.

I created the code screenshots using the carbon app.

[skywitchmaja]

sometimes it does feel like everyone in world is conspiring to piss me off. but at the same time.. people also say nice things to me, so it’s hard to say really

[eve-is-a-terf]

this tumblr popped up on my feed last year about October and I thought I’d give it a hate read and then I was like. Hm. Damn this makes sense. And that’s what peaked me lol.

wow, congratulations on being radicalized into our cult lmao!! jk, i love to hear other people's peaking stories, and so many come from hatereading. i always wonder how many TRA lurkers on radblr eventually become radical feminists themselves haha

[neon-angels-system]

anyway. sometimes the meowtuals posts and it is a Battle not to respond with a very long infodump about mental health

[joshuamj]

in regards to last reblog (specifically my tags on it), very friendly reminder that i would love to receive asks, i promise u will not be bothering me. Just be prepared cuz depending on what u say i may ramble on and on.

[ichigosoju]

🍡

[killmymind]

about to overthink for a second.

[protect-namine]

I love our designer soooo much. I love working with designers. I love talking with them while we have different perspectives (I ask questions to make sure a design is feasible on a technical level, they talk to me about research and design and how what we're doing is being validated with the people who will actually use the stuff we make). I just love being the person who executes someone's designs

[determinate-negation]

I have a question, and i mean this neutrally. When a gfm says it is “verified” and the verification is (as it often is) simply a blogger reblogging the post with no info, how are we meant to understand the gfm was verified? the handful of palestinian bloggers on here that verify gfm cant exactly spend so many hours for every campaign to make absolutely sure its legit. I mean they are human and most likely in troubled conditions themselves (or have family in difficulty). So we cant expect this vetting to be that thorough. How are we meant to know they didnt just rb the post without checking, or fall for the scam themself?

the palestinian and arabic speaking bloggers who have been verifying campaigns have been giving info on how they verify, mostly i think through messaging people in arabic and asking them stuff but i dont know for sure. i know that some arabic speaking bloggers on here have said that they dont want to post publicly in detail how they verify people because scammers will see and figure out how to look more legit. there also is a specific palestinian dialect of arabic that people who arent actually palestinian will most likely not speak.

please refer to things like the vetted fundraiser list or other fundraisers on @/el-shab-hussein @/nabulsi @/sar-soor blogs as i think those are some of the most authoritative bloggers on here for this. if something is verified by multiple people its likely its real.

i dont really know what else you want people to do. i understand your concern but your skepticism is just based on your belief that the people verifying this are too busy to really look into it. you also can look into peoples accounts yourself you know. reverse image search their photos, look up their name to see if they have other social media. a lot of people might have instagram or facebook but only recently made a tumblr. just use some critical thinking and information literacy for gods sake instead of immediately being suspicious of everyone to the point where you are accusing random people of being scammers just because they dont know how this site works. or on the opposite end, reblogging things like insulin paypal campaigns which are the most common scam on here. just think and use context clues pleaseeeeeeee. because accusing someone of being a scammer without evidence and spreading that information could actually have life or death outcome. i just dont answer asks that seem ambiguous and arent verified, i think thats better than potentially hurting a real person asking for donations by publicly calling them a scammer or reporting their blog