Natsuka's Clothes.

Natsuka's clothes.

He's so cute.

Source: Matsuzaki Natsumi-sensei's Twitter.

The cover is gorgeous.🥰

Turns out the news was a paperback version of Karasu no Midoriba. Well, I Guess some Japanese may have really been looking forward to it, but I can't deny that I'm a little disappointed.

It will be released on the 9th of October.

Source: Yatagarasu series' Twitter account.

This cover art is so pretty.

idc if it's Natsuka-sama or someone else, he's so pretty I turned it into my wall.

the crazy thing is that proshipping really IS the default-- or it was for me, at least. when i was way younger, if i recognized an interesting character dynamic, i'd ship it. it started with billdip for me, and then i liked gumwin, and then i watched camp camp and was obsessed with maxvid, and when i started watching rick and morty i instantly loved rickorty. the only time i ever thought that i shouldnt ship what i wanted was when i saw people on the internet calling my ships weird or gross. i dunno, i just think i never would have been ashamed of shipping what i wanted to if anti rhetoric wasn't the norm online. i was happier when i just looked at fanart on google images and enjoyed my shows the way i wanted to. before i was ever really involved in internet culture. and i'm happier now that i've stopped feeling gross for liking the ships i like.

so to anyone out there who hides the fact that they're a proshipper just to fit into that hostile anti environment, i just want to say:

you are not gross. you are not creepy. you do not have to listen when someone calls your ship gross. the only person you should listen to is yourself. if you want to ship something, just do it. it's worth it. i promise. <3

It's a preview of what's going to happen when the internet crashes.

idk if people on tumblr know about this but a cybersecurity software called crowdstrike just did what is probably the single biggest fuck up in any sector in the past 10 years. it's monumentally bad. literally the most horror-inducing nightmare scenario for a tech company.

some info, crowdstrike is essentially an antivirus software for enterprises. which means normal laypeople cant really get it, they're for businesses and organisations and important stuff.

so, on a friday evening (it of course wasnt friday everywhere but it was friday evening in oceania which is where it first started causing damage due to europe and na being asleep), crowdstrike pushed out an update to their windows users that caused a bug.

before i get into what the bug is, know that friday evening is the worst possible time to do this because people are going home. the weekend is starting. offices dont have people in them. this is just one of many perfectly placed failures in the rube goldburg machine of crowdstrike. there's a reason friday is called 'dont push to live friday' or more to the point 'dont fuck it up friday'

so, at 3pm at friday, an update comes rolling into crowdstrike users which is automatically implemented. this update immediately causes the computer to blue screen of death. very very bad. but it's not simply a 'you need to restart' crash, because the computer then gets stuck into a boot loop.

this is the worst possible thing because, in a boot loop state, a computer is never really able to get to a point where it can do anything. like download a fix. so there is nothing crowdstrike can do to remedy this death update anymore. it is now left to the end users.

it was pretty quickly identified what the problem was. you had to boot it in safe mode, and a very small file needed to be deleted. or you could just rename crowdstrike to something else so windows never attempts to use it.

it's a fairly easy fix in the grand scheme of things, but the issue is that it is effecting enterprises. which can have a looooot of computers. in many different locations. so an IT person would need to manually fix hundreds of computers, sometimes in whole other cities and perhaps even other countries if theyre big enough.

another fuck up crowdstrike did was they did not stagger the update, so they could catch any mistakes before they wrecked havoc. (and also how how HOW do you not catch this before deploying it. this isn't a code oopsie this is a complete failure of quality ensurance that probably permeates the whole company to not realise their update was an instant kill). they rolled it out to everyone of their clients in the world at the same time.

and this seems pretty hilarious on the surface. i was havin a good chuckle as eftpos went down in the store i was working at, chaos was definitely ensuring lmao. im in aus, and banking was literally down nationwide.

but then you start hearing about the entire country's planes being grounded because the airport's computers are bricked. and hospitals having no computers anymore. emergency call centres crashing. and you realised that, wow. crowdstrike just killed people probably. this is literally the worst thing possible for a company like this to do.

crowdstrike was kinda on the come up too, they were starting to become a big name in the tech world as a new face. but that has definitely vanished now. to fuck up at this many places, is almost extremely impressive. its hard to even think of a comparable fuckup.

a friday evening simultaneous rollout boot loop is a phrase that haunts IT people in their darkest hours. it's the monster that drags people down into the swamp. it's the big bag in the horror movie. it's the end of the road. and for crowdstrike, that reaper of souls just knocked on their doorstep.

forgive me lord for I have imagined a life far more soft and tender than the one you created for me