MHLoppy

Call Cecilia a tree because she making that paper

I'm not exactly sure what Joe's cooked here, but it's well-animated

Pixiv album source (same res / quality as submission)

The original title is また、遊ぼう so I'VE DONE MY BEST ON THE TRANSLATION OKAY

The second US concert event, “hololive English 2nd Concert -Breaking Dimensions-”, was held on August 24th and 25th at the Kings Theatre in Brooklyn, NY, over the span of two days.

This is the first time in history that a VTuber live performance took place at the historic Kings Theatre, which opened in 1929. We hope that this report from Kings Theatre conveys the sheer enthusiasm of the show.

Bill Shorten will not be returning for an extra season of NDIS, after the current season received mixed reviews and was plagued by budget cuts.

Max Kim leads the sales and licensing for the US office. This interview was done during Anime Expo 2024

As seen in 【NEW OUTFIT REVEAL】rock and roll reaper, baby! #rockalliope

Image from Xitter

Wake up babe more Go-Getters content just dropped

From YT community:

⊹˚.𖥔【NEW ANIME MV】⊹˚.𖥔

『Go-Getters』by Mori Calliope
ED from Suicide Squad: ISEKAI

Produced by Giga x Teddyloid
Animated by Studio WIT

Actually, some insight into this MV...it almost didn't come out, but I'm just glad to be able to share it with everyone finally! Apparently, Mori and Harley can't technically exist in the same world!! So, WIT pulled some magic to still make an MV featuring the both of us, and I couldn't be happier!

As a fan of DC and Harley Quinn since back in the day, and a comic student once upon a time, getting to share this with the world means so much to me.

I hope you'll listen to it lots, and keep enjoying the animation as well! Just like I knew they would, WIT made something really special!

-Mori

Announcement: Firefish will enter maintenance mode

For those who have been supporting Firefish and me, I can’t thank you enough. But today, I have to make an announcement of my very difficult decision: As of today’s release, Firefish will enter maintenance mode and reach end-of-support at the end of the year. The main reasons for this are as follows.

In February, Kainoa suddenly transferred the ownership of Firefish to me. This transition came without prior notice, which took me aback. I still wish Kainoa had consulted with me in advance. At that time, some people were already saying that “Firefish is coming back”, making it challenging to address the situation. Also, since there were several hundred active Firefish servers at that point, I could not suddenly discontinue the project, so I took over the project unwillingly.

Over the past seven months, I have been maintaining Firefish alone. All other former maintainers have left, leaving me solely responsible for managing issues, reviewing merge requests, testing, and releasing new versions. This situation has had a significant impact on my personal life.

Frankly speaking, there are numerous bugs and questionable logic in the current Firefish codebase. While I attempted to fix them, balancing this work with my personal life made it clear that it would take ages, and I’ve started thinking that I can’t manage this project in the long run. Additionally, vulnerabilities have been reported approximately once a month. Addressing vulnerabilities, communicating privately with reporters, and testing fixes have proven overwhelming and unsustainable. Moreover, a certain percentage of users have made insulting comments, which have severely affected my mental well-being and made me fearful of opening social media apps.

I will do my best to refund the donations made to Firefish via OpenCollective, but that’s not guaranteed.

firefish.dev and info.firefish.dev will remain operational until the end of February 2025, after which they will return a 410 Gone status.

Server admins may downgrade Firefish to version 20240206/1.0.5-rc and migrate to another *key variant, or may fork Firefish to maintain.

Downgrade instructions: https://firefish.dev/firefish/firefish/-/blob/downgrade/docs/downgrade.md

Thanks,
naskya

The results from other people who have looked into [the performance difference with the Windows patch] have been mixed, it's fair to say.
[...]
After days and days of very confusing results and multiple fresh Windows installs, I think we're getting somewhere -- or at least I think we are.

[...] I can confidently say that in its current state -- at least prior to the recent patch -- [Windows] 23H2 can be a bit broken with Ryzen, or really, it is pretty broken with Ryzen [causing reduced performance in some -- but not all -- titles]. The degree to how broken does vary, and there seems to be no rhyme or reason as to why this is.

It's really confusing as to how two Windows 11 installs, on the same system, configured in the exact same way, can deliver such different results, but only in some games. In fact, the variance between the games tested is just as confusing, and it makes diagnosing the issue extremely difficult.