Ina (of Hololive EN) slept in and missed her scheduled Minecraft stream - by two hours - and Kiara (also of Hololive EN) started her own stream and spent two hours roasting her.
With a cup of coffee in hand her virtual legs up on her virtual desk. Only Live2D doesn't actually do that so the legs don't move when her body does - though they do move independently which is just slightly disconcerting.
Ina still has 15,000 people waiting after now two and a half hours, and Kiara's roast got over 30,000 live viewers.
I checked The Hololive Minecraft stream index, saw Ina had streamed, clicked on the link, and thought YouTube was broken because it was showing me the "waiting for livestream" message rather than replaying it.
Then I checked my YouTube subscriptions and saw Kiara had an ongoing livestream titled "waiting for ina!!!!!!!!!!!!!!!!" and guessed something was up.
Normally Ina's Minecraft streams start around 6AM Sydney time and are over by the time I'm free of morning meetings and have time to listen to something while I work, so this actually worked out well for me.
And Ollie is scheduled to invade the EN Minecraft server at lunch time.
Update: And now YouTube is broken at least in this part of the world, from Australia to Indonesia, and Ollie had to reschedule her invasion of the EN server for the second time. Which wouldn't have gone entirely to plan anyway because she was logging into their old realms account and they've moved to a dedicated server now.
Also, this server - blogs, not Minecraft - is undergoing that weird distributed malformed requests attack again. Seems to have recovered but the load average spiked to about 50 for a while.
The New Horizons probe zipped past Pluto on July 14, 2015 at a distance of less than 8000 miles, providing in a few short hours most of the information we have about the ninth planet.*
Tomorrow, at about 4:30PM AEDT, it will pass (486958) 2014 MU69 - also known as Ultima Thule - at a distance of just 2200 miles.
As the official name suggests, Ultima Thule was only discovered in 2014. But its addition to New Horizons' itinerary is no accident. The Hubble Telescope was assigned to scan the region around the probe's trajectory to look for additional targets beyond Pluto but within range of the available propellant. A second, somewhat larger object was also found, but is further from original path and reaching it would require more of the propellant reserves. An assessment was made that New Horizons had ample reserves for what was originally designated PT1 - potential target one - but only had a 95% chance of reaching PT3.
Right now, our best picture of Ultima Thule is still in the potato-at-ten-thousand-yards category but that will change rapidly. Only not that rapidly: While New Horizons is closing in at a rate of 30,000 miles per hour, the probe is so far away that its high-gain antenna effectively has the bandwidth of an early dial-up modem.
This is what New Horizons did for our understanding of Pluto:
It remains to be seen if the valiant New Horizons will run afoul of the Mi-Go after its narrow escape during its previous rendezvous.
Artist's depiction of a Mi-Go warrior princess. Given that Mi-Go are fungi, we suspect our artist may have got into the liquor a bit early tonight.
Watch episode 1, The Woman Who Fell to Earth, and 2, The Ghost Monument. These aren't bad and establish the new characters.
Then skip episode 3 unless you are deeply into badly-scripted 50s period drama, and go to episode 4, Arachnids in the UK. It's a decently done Classic Who episode, like The Green Death, but a little more subtle.
Then skip episodes 5 and 6; they suck.
Then watch episode 7, Kerblam!, which is a good Russell T Davies-style episode which has the gumption to kill the characters who need to die to drive the story forward.
Then skip episode 8. The script for this one isn't the problem; it's the directing.
Then watch episode 9, It Takes You Away.
Then skip episode 10.
Basically it's a five-episode season, like Series 4b or when they split Series 7 in the middle. If you cut away the bad half, it's elevated to merely disappointing.
Posted by: Pixy Misa at Friday, August 03 2018 10:13 AM (PiXy!)
You could just say "stupid" and see if it skirts the edges of what I will loosely call "rules" of the banhammer.
Posted by: Rick C at Saturday, August 04 2018 07:18 AM (ITnFO)
Yeah, the R-Word is automatically detected, it seems.
Posted by: Mauser at Saturday, August 04 2018 10:08 AM (Ix1l6)
I've had about 70 "lite" suspensions (where you get shadow banned but can still post) for using words like "idiot" or "stupid". The two times I've been suspended for real were both for using "retarded".
Posted by: Pixy Misa at Sunday, August 05 2018 03:21 PM (PiXy!)
Have you considered Unicode substitution? Perhaps they won't recognize one of these:
Posted by: J Greely at Monday, August 06 2018 06:01 AM (tgyIO)
I get a ton of email from Amazon because we use AWS at work, so they get routed to a separate folder that I don't always look at straight away.
Sometimes that's a mistake. Today it was two mistakes, one confusing, one delightful.
Got an email Christmas morning,
It was labeled Amazon.
It was typed in Times New Roman,
Said my package, it was gone.
Back for return and refund,
And I'd get a check real soon.
But I don't know what they're talkin' about
Got it Friday afternoon.
The other one someone knows about, and a huge Christmas thank you to that someone. Really brightened up my day.