Hoshino Lina (星乃リナ) 🩵 3D Yuri Wedding prep!!!

Hacker & Mad Scientist VTuber!

💍 Cyan Nyan 星乃しお 🩵✨ 3D Yuri Wedding 2026 (npub1rzf…w4kn) 🩵 | We are Tokyo Hacker Girls (npub1k6r…8c3g) ✨

ママ : https://bsky.app/profile/heripiro.bsky.social | パパ : https://twitter.com/otozuki_teru
All the links: https://lina.yt/me

YouTube: https://lina.yt
Twitter: https://lina.yt/twitter
Bluesky: https://lina.yt/bsky
GitHub: https://lina.yt/gh
Sponsor Me!: https://lina.yt/sponsor
Buy me a Ko-Fi!: https://lina.yt/kofi

Public Key

npub1cxqje22r8ewnr30rt625d58cr8gpdjnw405cq5765m2qsvghnmpquz6wtz

NIP-05 Address

lina_at_vt.social@momostr.pink

Profile Code

nprofile1qqsvrqfv49pnuhf3ch34a92x6rupn5qkefh2h6vq20d2d4qgxyteassprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntgre4ll

Publishing to

relay.momostr.pink

Author Public Key

npub1cxqje22r8ewnr30rt625d58cr8gpdjnw405cq5765m2qsvghnmpquz6wtz

Show more details

Last Notes

2026-08-10 22:45:31 UTC

- reply

Not exactly, what you're describing has more to do with tracking. For example, my new model overdoes it and I actually want to turn it down or remap it a bit. All that is configurable and adjustable by the user already, it's just a lot of people don't bother to dig through the settings and just use whatever the defaults were.
What I'm describing is specifically about the physics (hair, clothes, things like eye bounce, etc.) feeling more "bouncy" than you'd expect.

2026-08-10 09:30:37 UTC

One thing I haven't figured out yet is where this mystery factor of 3 comes from.
These two lines of code are emulating what happens when the Live2D physics engine applies velocity as linear motion, then clamps down to a fixed radius, every frame.
The arctan thing was a first approximation (taking the velocity vector as tangent to the current position, length = angular velocity), but then the factor of 3 makes it correct.
https://media.vt.social/media_attachments/files/117/070/511/220/454/352/original/50755c6cb76bd056.png
https://media.vt.social/media_attachments/files/117/070/511/230/292/208/original/6acd14b9611cc56f.png

2026-08-10 07:11:07 UTC

- reply

One interesting thing I verified is that the "1/5 angle input momentum boost" thing Live2D does is absolutely essential to having it behave as designed.
I suspect that behavior is part of what people call the "Live2D physics feel". It basically creates energy from thin air!
So for example, if you rotate a still pendulum by 45 degrees, it will swing over MORE than 45 degrees on the opposite side, because energy was created. Sometimes a lot more. With some settings it'll even loop around!

2026-08-10 07:11:07 UTC

🚀🚀 WE'VE GOT PHYSICS~! 🚀🚀
Sorry I didn't stream this, it was really just fixing bugs in the Rust version of the engine that I rushed last night ^^;;
(and adding mobility, which turned out to just be dv -= v * fps * (1 - mobility))
#Live2D #Ayagami
https://media.vt.social/media_attachments/files/117/069/962/592/257/076/original/d9fb63648f54390c.mp4

2026-07-19 14:57:09 UTC

Cyan: *Holding a book* what do you call the thing that marks a page, like a bookmark?
Me: ... a bookmark
Cyan: No like a physical one
Me: Where do you think the word comes from?!?!?!?!?!?!
(This seriously just happened)

2026-07-19 08:35:03 UTC

Just got this in the mail~
I might have a new project starting to cook ✨

2026-07-13 11:56:15 UTC

- reply

Huh, TIL. That might be good enough. Do you have a link?

2026-07-13 09:39:17 UTC

Are there any compact CJK sans fonts with proper variant glyph coverage?
I just added Droid Sans Fallback (3MB) to demo.ayagami.rs, but that only has SC variant glyphs (Japanese etc will look weird). I wonder if there are any better options that aren't huge?
I don't really care about obscure glyphs, just BMP is probably fine since this is only used for model part labels and the like. But it would be nice to choose SC/TC/JP/KR variants based on locale or a heuristic or something...

2026-07-11 01:16:36 UTC

Cyan: I'm reading about quantum physics!!
Me: Ooh!
Cyan: Yeah, it's a book in Chinese! I learned about the shiny element!
Me: Shiny element???
Cyan: Shiny element!! You know, the dead cat....
Me: ????????
Cyan: There's proton, neutron...
Me: Electron? Photon???
Cyan: YES!!
Me: 🤦‍♀️

2026-06-29 09:46:57 UTC

RE: https://vt.social/@lina/116822363262715333
Aaaaa I went over 12 hours a bit and I thought YT would cut off the beginning wait screen, but it cut off the end!!!
I'll upload the last bit from my local recording later ;;
#note1x7d…w8lp

2026-06-27 13:43:18 UTC

STREAM: Making Live2D models move in Rust! 🦀
My from-scratch Live2D renderer works!!! 🚀
Let's add masking and parameters to make the model move!
🕐 Jun 28 13:00 JST / 04:00 UTC
▶️ https://youtube.com/live/wgG4hcBsOJo
#VTuber #ENVTuber #Live2D #Rust
https://media.vt.social/media_attachments/files/116/822/363/168/318/093/original/576191b6e6d8bb5f.png

2026-06-26 07:47:25 UTC

- reply

RE: https://mastodon.gamedev.place/@valorzard/116815283756835205
@npub1mpu…lk4h Having used emscripten and done similar things with other languages, it was infinitely easier in Rust. For starters, wasm is *natively* supported in Rust, you don't need a third party project like emscripten to use it.
I see from your timeline that you have Opinions about languages. Please keep them to your timeline and don't just barge into random threads to "well akshually" them, it's not nice.
#note1wt8…f30e

2026-06-26 07:31:48 UTC

- reply

This is not using any high-level middleware. This is written against the low level WebGPU API and wgpu-rs lowers that to the various backends.

2026-06-26 07:19:19 UTC

- reply

The abstraction is written in Rust for Rust first and foremost. I could have said "the power of the Rust ecosystem" but that would be splitting hairs.

2026-06-26 07:06:19 UTC

BTW, the open source Live2D renderer I'm building is fully cross-platform!
Thanks to wgpu-rs, it runs on Vulkan, Metal, DirectX 12, OpenGL ES, and even inside a browser with WebGL or WebGPU!
The power of Rust 🦀
https://media.vt.social/media_attachments/files/116/815/139/839/622/664/original/cf969506384cb5ea.png

2026-06-19 08:35:35 UTC

RE: https://vt.social/@lina/116774959127914284
I don't like people who go "OMG you touched AI I hate you" either, I think that's a toxic way to fight back against AI.
So the strict rules here are about RE+copyright risk specifically, I'm not going to say people who ask ChatGPT programming questions are the devil.
The full policy explicitly mentions using AI for translation and accessibility purposes as OK examples, because there's nuance to the world and better and worse ways to use LLMs.
I'm not a moral arbiter for everything potential contributors do not do I want to become one.
But yeah, if someone intends to throw an OpenClaw or similar agent directly at my project, they will be shown the door (and permanently banned), because that's not just a copyright/RE risk, it's also immensely rude and inappropriate to do without consent, to any project.
#note10qk…aqew

2026-06-19 04:47:49 UTC

So I spent some time writing an AI policy for Ayagami.
TL;DR AI is incompatible with black-box/clean-room RE. If you have *ever* used AI in a Live2D/MOC3 development project, you cannot contribute, for the safety of the project.
Even if you stop using AI.
I am not hardline anti-AI; I dislike AI but this isn't a policy to screw over people who use AI. This is simply logical.
AI is trained on GitHub, including Live2D's non-free source code repositories. If you have ever read that code, you may not contribute. AI has read that code.
If this were any other project things would be different, but I am keeping things strict to avoid tainting the project with non-cleanroom code, for legal safety.
AI models are tainted, and it's transitive. Using AI models to work on MOC3 file structures taints you.
Keep in mind this ONLY applies to code/subjects relevant to MOC3/Live2D. If you ask Claude/ChatGPT/Gemini a *general* question about Rust programming, for example, that doesn't taint you (as long as you don't talk about MOC3 or Live2D or paste relevant code).

2026-06-14 03:32:33 UTC

- reply

And even then modern emulators almost never have bit-identical rendering output to the original, if nothing else because there is not such standard for *GPUs*. No, your AMD does not render the same exact pixels as your NVidia. The official Khronos test suites have error margins.
So trying to get bit-identical output to the Live2D SDK would be a complete waste of time, because the GPU you're going to feed that data to isn't going to give you bit-identical behavior either.
This isn't like a physics engine that has to run a 10 minute game replay 1:1 without desync.
"But Live2D has physics"
Pendulum physics are convergent, not chaotic/divergent. Small errors in the simulation do not accumulate over time. This is a non-issue here.

2026-06-14 03:22:17 UTC

- reply

"What about projects like Wine?"
Wine has a test suite, with large numbers of tests they do not pass. That's how you know it's not copied from Windows code.
"Emulators?"
Emulators go to great lengths for compatibility, which is needed for things like game replays not to desync and cross-netplay. This takes a HUGE amount of work over many years to achieve legally, with people devoting months or years just to crack one single mystery.

2026-06-14 03:14:09 UTC

With my MOC3 work, I should clarify that my goal is not to *clone* any software from Live2D, including their SDK. I have no intention to provide a "drop-in replacement" for anything.
I believe prioritizing that would be the wrong mindset and goal for this kind of project.
There *is* value in drop-in compatibility layers! However, when you set out to do that, it means most likely your motivation is to get out of paying Live2D for their SDK license, in existing use cases.
If you are not already a Live2D customer, there is no need for that.
Why clone any interface, UI, API, or anything else from Live2D otherwise? That would presume that those designs are the best way of doing things. They almost certainly aren't!
What matters is being compatible with the file format, not cloning the ecosystem around it.

2026-06-13 12:37:48 UTC

STREAM: Let's build a Live2D MOC3 loader & renderer in Rust
Now we know how it works, so let's implement it!
What Rust graphics API should I use~?
✨ Important FAQ✨
https://lina.yt/moc3faq
🕐 Jun 14 13:00 JST / 04:00 UTC
▶️ https://youtube.com/live/iT3A0AhK3YE
#VTuber #ENVTuber #Live2D
https://media.vt.social/media_attachments/files/116/742/833/258/445/233/original/eba88c671dee768c.png

2026-06-08 11:59:49 UTC

Posted long thread over on birdsite/bluesky about the legality of black box RE etc etc
https://bsky.app/profile/lina.yt/post/3mnrdw4sonc2h
Y'all probably don't need it here since you all know how this works, this is for the VTuber peeps who don't know reverse engineering proprietary file formats is, like, a cornerstone of FOSS and not something to be legally challenged lightly.
But yeah TL;DR if they actually try to sue me for looking at their file format without even touching their software... I'm not going to just fold and give up.

2026-06-08 06:29:21 UTC

I think the next step for the Live2D MOC3 project, after a bit of write/modification testing, will be to start writing a loader for the file format and a prototype OpenGL renderer, in Rust.
Why GL? Because it's easy, cross platform, and I need a standalone testing app.

2026-06-03 12:36:39 UTC

So let me get this straight... rsync made a *security release* fixing a bunch of CVEs, it regressed some stuff, people looked at the commit log, saw Claude sign-offs, and started a mob on the sole maintainer?
Yeah, this stuff is what gives legitimate AI criticism a bad name.
I don't like it, you may not like it either, but when people are throwing LLMs at legacy codebases and finding CVEs by the dozen, and a sole maintainer is trying to keep the house from falling apart... if you're attacking them, you're firing at the wrong person.
You know what's a bigger cancer on this world than AI? People incapable of seeing any nuance in situations. And this applies to absolutely everything. I'm absolutely exhausted of extremist takes. From every single side and point of view, in every single debate, AI related and not.
You all seriously need to touch grass, and learn to stop being outraged all the time over every single thing in this world.

2026-06-02 06:26:24 UTC

Should I?

2026-05-27 13:22:48 UTC

Mystery encryption key: p3s6v9y$B&E)H@Mc
Any idea where this comes from? There are a few web hits, including this list of similarly-shaped strings: https://pastebin.com/0UTJYhBA
It feels like it's some kind of poor rand() LCG-ish thing trivially converted to ASCII, but I'm really curious if anyone has a good guess.
A certain popular VTuber software uses it as an XOR pad obfuscation for its config files... (I derived it statistically, didn't look at the code)

2026-05-17 11:33:03 UTC

- reply

Ideally:
- Good quality (no smearing/bloom etc)
- 480p30 or better
- No other faces in background
- Nothing significant obscuring face (narrow mic OK)
- Reasonably expressive
- Person mostly faces camera
- Reasonably zoomed in (face is at least 128 pixels across).
- CC or PD

2026-05-17 11:03:13 UTC

Sooo I want to work on the FaceKit face tracking stuff on stream, but I obviously don't want to show my camera...
Any suggestions for "talking head" videos that are expressive and won't get me in copyright trouble? ^^

2026-05-17 08:05:45 UTC

- reply

The "free software" crowd comes to mind, you know, the FSF purists buying 10 year old laptops because they're "100% free" while their home has hundreds of microcontrollers running proprietary firmware, in everything from dishwashers to their computer mouse to the EC in their supposedly 100% free laptop. They invent arbitrary rules like "ROM doesn't count" that actually go against the goals and spirit of their supposed moral values.
It's a farce and I can't take those people seriously, nor anyone who seriously believes "zero AI involved in my software" is a viable thing going forward.
Go support projects that don't embrace AI and stop worrying about the supply chain, because that's a lost cause and acting like it isn't is a losing battle that leads to madness.

2026-05-17 07:55:37 UTC

- reply

It is a choice if you are willing to make extreme trade offs, that no existing established project the size of Rust can make and survive.
You as an individual are free to make whatever choices you choose, but I do hope those choices are at least self consistent, because 90+% of the time the people complaining about this stuff and saying they're going to do something about it are just virtue signaling and then not actually willing to make all the compromises required to maintain an internally consistent position.
To be clear, I don't like any of this AI slop stuff either, but I'm not going to switch to NetBSD because of it, and the tiny minority of people who are aren't going to make an impact on the field.

2026-05-17 07:06:28 UTC

- reply

If the goal is "no AI generated code in my dependency tree", then that was a battle lost before it even began. Multiple core dependency projects are allowing AI.
Given the state of the world re AI usage, there was no way that battle was going to be won. You'd need something like "AI is ruled illegal/copyright infringing across the board in some important jurisdiction" for people to consider it toxic enough to not touch and fork each and every project whose maintenance team disagrees.
The way FOSS is interconnected, it is simply not possible to "hard partition" the dependency tree on moral concerns at scale. Pretty much the only thing that can do that is a legal code red, and it seems the lawyers have decided AI isn't one (even though many disagree).

2026-05-14 10:02:47 UTC

I worked at a fairly big tech co years before the AI boom. People did large scale refractoring across huge code bases back then. With refactoring tools. And properly written robots.
Applying changes to code at scale, opening PRs automatically, basic interaction with human reviewers, making sure tests pass, getting things merged when ready. All that already existed before LLMs. And it was actually reliable and not capable of hallucinating terrible things.
It's like we've forgotten how to automate things without LLMs and openclaw now...
https://media.vt.social/media_attachments/files/116/572/336/675/614/438/original/85051466ec49ab35.png

2026-05-12 15:03:02 UTC

🚀 IT WORKS!!!! 🚀
ARKit iPhone face tracking, without an iPhone. Just a webcam on any Mac.
All the blend shapes. All the features. No magic camera required. It just works.
Now I just need to plug this into VBridger/VTS and clean things up a bit ✨
Logs: https://gist.github.com/hoshinolina/ba7548a50563146fa1caf3d2bd8ea3be
https://media.vt.social/media_attachments/files/116/562/184/028/866/183/original/cc2979e62d14d28f.png

2026-05-11 13:45:28 UTC

I told Reddit that ARKit face tracking is just really good webcam tracking, and gave them a simple test that proves it.
They're all downvoting me without doing the test.
Look what I just found... the ARKit face tracking code is hiding in macOS. I'm going to make this work.
https://media.vt.social/media_attachments/files/116/556/242/333/968/393/original/4ef82e62316af6ba.png

2026-05-07 08:30:13 UTC

Typical ML argument: "If I can read something legally, why can't I train an LLM on it?"
Humans are capable of reading things and later writing a similar thing that is still a copyright violation. If I go and write a book that follows the plot line of Star Wars, that's still a copyright violation, even if no text is literally the same. If I play the melody to a song on my piano and release it without the appropriate mechanical cover license, that's also a copyright violation.
The reason this does not happen often is that, as humans, we are aware that that's plagiarism and there are rules.
LLMs have no such awareness and routinely output things which are blatant copyright violations when appropriately prompted. That means the model weights encode that work, and therefore, are themselves a derivative work.
Your brain encodes a massive amount of copyrighted information. You are not a walking copyright violation because humans aren't data, can't be copied and distributed en masse, have human rights, etc. This is why "mind reading machines" are a classic dystopian plot point (monetizing your thoughts etc).
An LLM is not a human, does not have human rights, nor human privileges. It is data, and if it encodes copyrighted information, that's a derivative work. If you aren't following the license of the training data, that's a copyright violation.

2026-05-07 08:19:27 UTC

- reply

> Can it be met?
"I can't realistically do what I want without violating the license" does not, in fact, mean you get to violate the license.
> Also if a document can be legally read, then why can it not be used for training?
This is the "ML erases copyright" argument. The point of copyright safe models is not assuming that model is valid.

2026-05-06 14:53:53 UTC

There's a thing about Edge storing passwords unencrypted in RAM going around. While that could be improved, you should know that:<li>If an attacker is reading your RAM, you have bigger problems than your password list (like, for example, your cookies, which are more powerful than passwords because they can bypass 2FA)</li><li>No browser guarantees passwords do not stay in RAM unencrypted after use. It is near impossible, there are too many layers of software involved that aren't using secure RAM erase.</li><li>The prompting for your password/screen lock/whatever when you view passwords in the password manager is just to stop casual snoopers. It is trivial to bypass, just go to a login page with autofill and read the password through dev tools. Yes this works (tested in Chrome). No screen lock password needed (unless you enable requiring that for every autofill).</li>
So yeah, Edge probably shouldn't store the entire password store in cleartext in RAM all the time... but if RAM dumps are in your threat model, you really have bigger issues anyway.

2026-05-06 07:30:28 UTC

- reply

This is rootful and publishPort does not work with internal networks. That's the whole reason I ended up here. Don't ask me why.

2026-05-06 06:31:23 UTC

- reply

If the model weights were licensed CC BY-SA themselves and the source training data were thoroughly documented and attributed (that's the BY part) then of course it would be a legitimate derivative work of the training data.
That is not the case. Not a single ML model I've found is attributing anything to its training data to copyright standards, nor considering things like license incompatibilities.

2026-05-06 03:30:54 UTC

- reply

OK so apparently setting DNS to 0.0.0.0 means setting the upstream DNS so that works to close off DNS.
And then I can use firewall-cmd to configure container networking policies, except for some reason the firewall zone is hardcoded to "trusted" by podman so I have to use that one...???

2026-05-03 23:53:53 UTC

- reply

Not to argue with the general point, but I don't think those block diagrams are useful to making it. The DDR one is basically just "this is a DDR memory block" with no detail.
DDR is more complicated in terms of control logic as far as I know, and modern versions like LPDDR5 *also* have on die ECC (not because radhard, just because the bits are so dense they finally stopped being able to pretend perfect memory is practical, long after flash/etc had to).

2026-05-01 06:10:59 UTC

Why are AI people so monumentally *bad* at copyright?
I'm looking for ethical/copyright-safe training data sets. Common Corpus sells itself as that... but then I go read the paper and they include CC BY-SA scientific papers and GPL stuff from GitHub, and then in models trained on that dataset they proudly state:
> Only trained on open data under a permissible [sic] license [...] By design, all Pleias model are unable to output copyrighted content.
Um, no?? CC BY-SA is not public domain, it's a copyright license. You can't train on CC BY-SA content and then claim your model is any more copyright-safe than whatever Google and Meta are releasing. It just means you're violating the copyright of people releasing content under open licenses only.

2026-04-21 03:55:28 UTC

Well this is ✨interesting✨!
Turns out, macOS already supports what it needs to run Intel binaries with a non-Rosetta emulator, after Rosetta dies.
It's behind a private entitlement for now, but still!
Wine+FEX+ARM64EC anyone? ^^
https://media.vt.social/media_attachments/files/116/440/663/385/326/510/original/864a6e3222c30852.png
https://media.vt.social/media_attachments/files/116/440/663/553/078/399/original/01e9e8ecd9c80188.png

2026-04-16 07:04:52 UTC

A friend asked Gemini to do a security assessment of a recent open source macOS app (look through code, developer behavior, user forums, etc).
It spat out a 2,500 word essay painting the whole thing as a massive backdoor, talking to C&C servers, reading your chat messages, bypassing macOS security, the works. Entirely coherent on the face of it, overdone but it *could* have been real and someone not in infosec would easily buy it.
100% hallucinated. Gemini wrote an entire infosec fanfic based on nothing. Worst thing I found on the real repo was a symlink traversal bug that was quickly fixed by the dev.
This was using the "Deep Research" function in "Pro" mode on an "Ultra" account.

2026-04-14 14:05:29 UTC

- reply

I beg to differ. @npub1rzf…w4kn and I are definitely yuri.

2026-03-31 12:34:23 UTC

- reply

Try the COPR here!
https://copr.fedorainfracloud.org/coprs/hoshinolina/streaming/
After enabling it, just `sudo dnf install proaudio-setup` and rebooting should do the magic. You can run `sudo proaudio-setup check` after to verify that everything is configured properly.
Let me know how it goes!

2026-03-31 12:07:32 UTC

I've been working on a little tool to automatically optimize Fedora for real-time audio processing. 🎶
Is anyone interested in testing it? Bonus points if you know what audio buffer sizes and xruns are (so you can tell if it helps) ^^
https://media.vt.social/media_attachments/files/116/323/703/217/665/020/original/9bf51e97a5c0c89a.png

2026-03-26 08:14:34 UTC

TIL Linux loses IRQ SMP affinity configuration when you sleep/resume (x86). This seems... less than ideal?

2026-03-15 03:25:55 UTC

RE: https://social.treehouse.systems/@ariadne/116213132813239860
Read what Ariadne is writing about LLMs. This all tracks with my intuition, that OpenAI et al are a big grift.
You categorically do NOT need millions or billions to train a useful LLM that can communicate in human language. LLMs are *good* at language, it's in the name!
The reason these companies are burning massive amounts of money and using increasingly massive models is they've taken "look, this tech makes for a cute chatbot that can do useful stuff" and turned it into "if we make it bigger it'll be SMARTER!"
And the thing is, that's true... to a point. When you stop treating the LLM as a *language* model and start trying to turn them into an all-knowing entity that has memorized the entirety of human knowledge and can do anything you prompt it for all with the same model (or a few collaborating models), you quickly hit diminishing returns. And you end up with a thing that's kind of smart (not really) and kind of knows everything (not really) and convinces everyone to throw insane amounts of money at you because you're fundamentally using the technology for something it wasn't intended for.
The way we fight back is with small home-grown "LLMs" (SLMs?) that run on a MacBook and train on a few GPUs and *training/fine tuning them for specific purposes*.
The whole AIBro approach of just using prompting and in-context learning with a single all-powerful model is just patently absurd.

2026-03-09 11:45:13 UTC

- reply

I might still do a monthly challenge or something in the future so people who want to have fun and learn can have fun and learn. That's still okay.
But CTFs as discrete competitions with winners are dead.

2026-02-19 14:51:36 UTC

Okay so I finally got around to reading the Fluxer dev's (long!) blog post and... his take on federation is literally the exact same thing I independently suggested.
10/10 this guy knows what he's doing. This is going to work.
(Also fully agree with his "why not E2EE for messaging" section)
https://media.vt.social/media_attachments/files/116/097/853/738/250/531/original/0d42d9ce205a4af4.png

2026-02-17 11:40:22 UTC

- reply

Essentially, I don't have the energy to argue with these kinds of people forever, nor am I comfortable seeing them free to reply to me with their terrible takes (which are nonetheless "appealing" to some naive readers without context, plus bring in more people like them).
I'd rather just not use a site/platform with this issue.
Technical arguments are fine, but having people with takes like "'large' communities like yours should not exist" ('large' = my 1600 member Discord server) or "Discord is bad and you can just choose not to use it" (using the word "Wintel" in the same comment, while comparing using Discord to drinking lead in a linked past comment... you know exactly what kind of person this is) is just... ew. Gross.

2026-01-03 02:03:37 UTC

I'm spiraling a lot this morning again... thinking about how nobody in the entire Linux Graphics community stood up for me really, really hurts. Not even close friends.
I don't post about this stuff often but that doesn't mean I'm not suffering...

2025-12-17 15:37:20 UTC

No single person has ever reinvented all the wheels and built something genuinely useful.
You can reinvent all the things for fun and for education, but then that's all you will achieve. Enjoyment and education. That's fine, if that is your goal.
If you want to actually build something people will use, you have to stand on the shoulders of giants. You get to reinvent one thing, and reinvent that one single thing well.
Believing you can single-handedly redo the work of thousands of people across dozens of (sub)fields, and do a better job than them, so much so that people will actually believe your work is superior and choose to use it, is pure lunacy.
Unless you can recruit your own team of hundreds or thousands of people, of course... but for that you have to be a (very) good leader.

2025-12-08 03:21:27 UTC

I knew this was going to happen, but it's still extremely funny having to write this update to my [original doc](https://asahilina.net/luna-story ).
I wonder if any of her users/contributors noticed any of this?
https://vt.social/media/media_attachments/files/115/681/778/291/913/053/original/c01153d8d4ac999f.png

2025-12-05 07:01:15 UTC

Honestly, some days I wonder if I should just switch to Windows... what's the point of an OS built around a kernel that is this toxic?

2025-12-01 04:36:24 UTC

RE: https://vt.social/@lina/115431232807081648
Addendum to this whole thing: I learned that Karol is telling people that there is evidence against me, but that sharing it would put people in danger, so he can't.
In effect, this means that the Freedesktop CoC team is actively choosing to judge people based on secret evidence, without giving them any opportunity for due process or defense.
For whatever it's worth, I have no idea what that evidence could possible be. It might be forged, or unreliable. I am deprived of any opportunity to defend myself against it.
Needless to say, this is not how any CoC team should conduct itself, and every member of and contributor to the Freedesktop ecosystem should be concerned. What happened to me could happen to anyone.
#note1h82…mg9c

2025-11-20 04:01:24 UTC

RE: https://mastodon.social/@Signez/115575839585586269
This code in CloudFlare should have followed the same standards you would for things like kernel code, and that means no unwrap() allowed unless you can prove the bad condition never happens (like unsafe code requires a comment proving safety).
Memory safety is half the battle. The other half is panic safety, but you need to opt into that one (there are several ways depending on how strict you want to be).
#note16qz…dw5y

2025-10-30 02:45:08 UTC

I love @npub1rzf…w4kn so much 🩵

2025-10-04 17:34:30 UTC

- reply

I think the idea is one is for your account proper and the other is for the frontend, but yeah it's weird...

2025-09-21 05:03:01 UTC

- reply

I'm actually kind of wondering if I got into this habit partially to make things easier to see on stream, and then it stuck because it's more comfortable! ww

2025-09-21 04:59:51 UTC

I just realized something... When I use HiDPI monitors, I often end up zooming in websites, text editors, and consoles. But I don't want to set the display scale larger (than 150%), because I want menus and widgets to stay smaller. I want the main content area to be easier to read, but keep things around it denser since I don't look at them as often.
Does anyone else do this? Should it be some kind of system setting even? ^^

2025-09-12 08:46:18 UTC

- reply

My personal opinion is that non-generative AI is not copyright-transitive the same way software is not copyright-transitive.
A Word document does not carry the copyright of Microsoft Word, because Microsoft Word is just a tool providing non-creative input to the document.
An AI model for face detection does not carry the copyright of the training data, because the training data is just a tool providing non-creative input to the model.
The training data *might* have been used in violation of some terms or license, but that is a *different* question to whether the resulting model itself is infringing on its copyright. Just like using a pirated version of Microsoft Word doesn't make the documents you make with it copyright violations.
It's GenAI where things change, because the output and the functionality of the model becomes (ostensibly) creative. And that's what copyright cares about, creative works.

2025-08-23 04:05:32 UTC

- reply

I should try this....

2025-08-20 02:30:38 UTC

- reply

wait WHAT? Nobody told me this!!!

2025-07-22 07:56:46 UTC

For anyone working in Japan or considering it: YSK your visa is NOT tied to your employer:
- You can freely leave and find another job.
- You can stay job seeking for the duration of your current residence permit.
- You can be self employed with local clients.
Some employers lie about this, don't fall for it, and NEVER give them your residence card! It's yours, not theirs!
Nobody is going to kick you out of the country just for losing your job. Know your rights.
As long as you follow the rules, pay your social security, pension, and taxes, and make enough to earn a living in Japan, immigration generally does not care about what you're doing.
There is paperwork to be filed and laws to follow, but as long as you do that, you can stay!

2025-07-03 03:15:48 UTC

Reddit is going crazy about the Switch 2 using "encryption", to lock out third party docks, but as far as I can tell that's misinformation.
Nothing in the logs looks like encryption, it's just a proprietary protocol. Manufacturers clone those all the time!
Not following standards is not nice, but saying this dooms third party docks or has any DMCA implications is nonsense. In fact the article already points out one compatible third party dock.
https://www.reddit.com/r/gaming/s/0gZWh2I5Tb

2025-06-18 09:26:12 UTC

There's this whole article about KiCad being broken on Wayland... but apparently it's all just a distro packaging problem???
https://www.kicad.org/blog/2025/06/KiCad-and-Wayland-Support/
The article doesn't mention XWayland at all, but **KiCad works perfectly under XWayland** as far as I can tell, and that is the default on at least Fedora! wxwidgets (the toolkit KiCad uses) is still flaky under native Wayland apparently, but **it is perfectly okay to keep using XWayland for now, and you should!** Apps and toolkits should not switch the default backend to Wayland until all major regressions are fixed, that's kind the whole reason why XWayland exists!
If you are on a distro that enables KiCad Wayland support by default and you experience the issues in that blog post, you don't need to (and probably should not) switch to an X11 session. Just launch KiCad as GDK_BACKEND=x11 kicad and it should run under XWayland just as well as it does under X11 sessions.
Some distros are dropping support for the legacy Xorg server and X11-native sessions, but **nobody is dropping support for X11 apps and XWayland, and nobody should be concerned about running apps in X11 mode for as long as it's needed!**

2025-05-27 11:35:59 UTC

Looks like a 20-core (16p 4e) M1 Ultra (2022, 3.0GHz) is slightly faster than a 16-core (32-thread) AMD Ryzen 9 7945HX (2023, around 4.3GHz real clock) at building Chromium/CEF.
The M1 Ultra is pulling ahead by around 5% in terms of source files, right now.

2025-05-05 05:16:40 UTC

For over one year I've been harassed, threatened, doxxed, misgendered and abused by Luna the Foxgirl, author of Inochi2D.
Due to her attacks and manipulation of others, I no longer feel safe contributing to Linux GPU drivers, and I will be retiring my current model.
https://asahilina.net/luna-abuse/

2025-04-02 06:46:19 UTC

- reply

They keep crafting new accounts...

2025-04-01 17:10:37 UTC

- reply

https://vt.social/media/media_attachments/files/114/263/814/026/420/779/original/67ccf1154e8bf679.png

2025-04-01 17:08:14 UTC

- reply

There's a huge DM spam wave from Nicole, the Fediverse Chick... google it ^^

2025-04-01 17:00:20 UTC

I really should just throw a quick patch onto vt.social to reject messages containing "Fediverse Chick"...

2025-03-22 09:26:51 UTC

- reply

No other open kernel has the hardware support to really be a Linux alternative... the BSDs will work for some things, but there is a huge difference in hardware support, especially for desktop and embedded. Things like Redox are essentially at the research kernel stage and not practically usable yet.
You can drop in another init system and write a few init scripts and switch to something other than systemd, but I think Linux is a de facto monopoly right now...

2025-03-20 10:30:42 UTC

- reply

If you don't believe me, look at what happens when you configure an EQ with a reeeeally high Q (super steep/complex frequency response), and play back a click through it!
https://vt.social/media/media_attachments/files/114/194/293/504/019/267/original/159fd79ec11da4c4.mp4

2025-03-20 10:18:40 UTC

I was thinking about DSP stuff in another thread and it just hit me that... an EQ can be expressed as a FIR filter, and a reverb impulse response is the same thing, and you can go back from the IR to its frequency response.
That means a reverb filter and an EQ filter are actually the same thing. A reverb is just a really complicated EQ. 🤯
(I know some/many EQ filters are IIR, but they can always be approximated well enough as a FIR with enough taps)

2025-03-18 15:25:41 UTC

For personal reasons, I no longer feel safe working on Linux GPU drivers or the Linux graphics ecosystem. I've paused work on Apple GPU drivers indefinitely.
I can't share any more information at this time, so please don't ask for more details. Thank you.

2025-03-16 23:59:50 UTC

- reply

Those things just work for me on KDE Wayland, it's X11 that is kinda broken... ;;

2025-03-12 12:45:11 UTC

- reply

Are you doing the math in the Y/C domain or some other colorspace? I get the feeling the best way to try to approach this would be to take the raw 7800 color values (4+4 bit) as input, build up a line buffer of the composite color signal with a lot of oversampling, and then try different mixing approaches for Y/C and pulse shaping/delays for the input signals. Then you run it though a composite decoder to produce YUV/RGB only at the output.
Once you have something close with that method you could probably optimize it to be less brute force, and at that point you could generate as many samples as you want since you'd have a reference implementation ^^

2025-03-12 10:39:57 UTC

- reply

Did you read this page? Apparently both the generated colors and the artifact colors vary from console to console and even with temperature... so I'm not even sure if there's such a thing as a proper ground truth!
https://7800.8bitdev.org/index.php/Atari_7800_Color_Documentation

2025-03-11 15:35:28 UTC

- reply

By lookup texture I meant for the color mixing. So like, if you manage to get enough data points to have a reasonable dataset of how different colors mix together, it could just be implemented as one or more textures indexed by luma/chroma or some derived components if you can't come up with an analytical construction that's accurate enough.

2025-03-11 15:09:48 UTC

- reply

I think you're going to need more data for this... have you compared output of RF machines vs. composite or s-video modified ones?
I think there are too many factors involved to figure it out from some game screenshots... what I would do is create a bunch of test patterns with many colors/artifact patterns, try them out on a real machine (or multiple, with different output setups), and use them to try to figure out what the color mixing curves/function is. At the end of the day you could even just turn it all into a lookup texture.
Here is some discussion on some of the subtleties of the TIA video output: https://www.retrosix.wiki/tia-video-faults-atari-2600 (since you're dealing with mixing the chroma and luma signals, those subtle timing issues probably play a part in how they mix)

2025-03-09 20:24:33 UTC

- reply

I don't think your hypothetical "compromised userspace" scenario applies to the ESP32 in any practical usage. These are integrated chips where the the user host code runs on the same chip, I think even in the same address space. So if that is compromised, the Bluetooth side is compromised regardless of the existence of the vendor commands.
In principle you could use an ESP32 as an external Bluetooth controller exposing HCI of course, and then the concern would apply, but I don't know why anyone would do that when dedicated Bluetooth chips designed to be used as HCI dongles exist.

2025-03-08 20:11:24 UTC

- reply

It is a nothingburger. It's basically "if you can write firmware for the device and access the Bluetooth HCI (host) interface, you can do undocumented things outside of the Bluetooth spec". To access the HCI interface you need to already be writing custom firmware.
It's not a remote attack, it does not bypass firmware signing. The things you can do are things you can already do with various other hacked/special-purpose devices, or an SDR.

2025-03-02 14:50:20 UTC

- reply

If you want true horrors look at GPU ISAs... ;;

2025-02-03 16:36:54 UTC

How do you change the frame rate to a simple constant and properly regenerate timestamps with ffmpeg, without transcoding or duplicating or dropping any frames?
Every time I try to do this, the only way that works is converting to a raw bitstream format and back. Is there really no way to tell ffmpeg to just throw away all timestamp and FPS information and just recreate it from scratch?
The closest I got is -bsf:v setts=ts="N/TB_OUT/30" but that only changes the timestamps, not the container timebase/frame rate, so it still shows up with weird numbers like 17.42 fps, 17.42 tbr, 1k tbn. I tried -r, -video_track_timescale but they don't work.
I ended up doing it with mkvmerge, which is super easy: mkvmerge -o out.webm --default-duration 0:30fps input.webm. This does what I want, which is clean timestamps with no weird rounding errors or duplicated frames at the beginning/end and a proper timebase 30 fps, 30 tbr, 1k tbn. But it means I need to round-trip through mkv if the container is something else...

2025-01-31 21:35:44 UTC

Cyan: Babe can you make me a sandwich?
Me: Sure! Do you want it hot or cold?
Cyan: With lots of Lao Gan Ma, hot.
Me: ...I meant temperature...

2024-12-05 21:38:41 UTC

Me: You know what I want now?
Cyan: What?
Me: Chocolate~
Cyan: What do I look like, a cacao tree??
Me: ........ Σ（・□・；）

2024-11-17 13:27:24 UTC

I swear that's how it works!!!
How did you get into programming? ✨
#CyanTechMeme
https://vt.social/media/media_attachments/files/113/498/523/223/672/422/original/c371fda29ffd7c51.jpg

2024-11-16 22:12:09 UTC

The new art gallery page is looking good!
Now we just need to add all the commissions and fanart to it ✨✨
#TokyoHackerGirls #AsaCyan #VTuber #ENVTuber
https://vt.social/media/media_attachments/files/113/494/925/520/370/066/original/dfe87f463a497219.png

2024-10-28 12:25:19 UTC

I've seen this one come up a few times in PL threads too... despite what some believe, Go is not a memory safe language!
Specifically, Go is not memory safe if your program uses goroutines. Go does not protect against data races, which trigger UB and memory unsafety.
See: https://go.dev/doc/faq#atomic_maps
Also: https://blog.stalkr.net/2015/04/golang-data-races-to-break-memory-safety.html

2024-10-22 16:10:15 UTC

I just hit 1K followers!!! Thank you everyone!!!!! 🩵🩵🩵
It's crazy how fast things are growing here on Bluesky!! How long will it take to hit 2K? 🚀
https://vt.social/media/media_attachments/files/113/351/938/349/457/310/original/c24cc33856c25019.png

2024-10-19 19:08:30 UTC

x112virtgpu is so cursed!!!
Today we somehow ended up more broken than we started... ^^;;
More debugging next stream~!

2024-10-18 10:07:53 UTC

- reply

Your argument basically reduces to "some people like C better and would've enjoyed doing what you did in C and done it just as well".
Unfortunately, we know that is not the case, and nobody can write correct, complex C code. With Zig not implementing important features Rust has that make writing correct, complex code easier, the only logical assumption is that it also would've not worked out nearly as well.
If someone wants to prove me wrong, they are welcome to write a complex GPU driver in Zig and see how that goes...

2024-10-18 09:33:30 UTC

- reply

Please read the rest of my thread. It's not just about it being *possible* to delegate nested deinit to an object, it's about the compiler writing that deinit code for you most of the time. I don't want to have to manually write a deinit function for a complex object with 20 members.
On top of that, just because you *can* do that with Zig doesn't mean the language encourages it. The standard library types don't do it, and you're stuck manually writing cleanup code as I said.
At the end of my post I already said I'm not saying Zig is a bad language, but it definitely isn't the right language to bring to the Linux kernel because it doesn't solve the problems we're trying to solve.

2024-10-18 08:39:28 UTC

- reply

That's because println!() may panic, which might have to drop the value when unwinding the stack. So the error is correct, the problem is that it's hard to escape the panic problem.
In Rust for Linux, we don't use use unwinding panic, so it might work as intended there... but I'd have to try it.

2024-10-18 07:52:22 UTC

- reply

Copying a thread I tweeted about `defer` vs. `Drop`:
> with defer:
> - whilst a bit error-prone, destruction is bound to the context and you can have non-intrusive destructors, you'll need this for APIs where you need a context to destroy a resource, so storing it in each object is infeasible
This is a valid argument and I actually have run into this myself! It's a real annoyance in Rust...
... but the thing is, this is the exception, not the rule. 99% of the time automatic Drop is what I want.
One of the neat demos I did of how Rust is better than C is that my Rust OF abstractions take care of refcounts for you, even across iterators and such. All the explicit refcounting (that nobody gets right) disappears.
In Zig, it'd come back, just as "defer" everywhere instead.
It *is* possible to forbid Drop in Rust for a type and require explicit destruction, and I'd rather do that for the 1% of cases where I need it, than have to defer the other 99%.
The Zig approach really doesn't scale for complex data structures. You can't have a generic vector or map, and just destroy it. You need to write explicit code to iterate through it and destroy every element. That's a real major pain...
Much of the time I don't even have Drop impls for my objects, or they just do one trivial thing. 99% of the cleanup code is generated by the compiler recursively calling Drop on all contained types. Having to type that out would be a lot of time wasted writing error-prone code...

2024-10-17 19:30:29 UTC

- reply

Operator overloading is the one I could live without... but it still would have been very annoying to have to use functions to do all the complex GPU power management calculations that I built on top of a simple soft float implementation (no real floats in the kernel!).
I have nothing against Zig, it looks like a neat programming language and it definitely has its place!
... but I don't think that place is writing complex operating systems and drivers today. At least I'm pretty sure it wouldn't have worked for my Apple GPU driver.

2024-09-11 06:20:36 UTC

Cyan: 4000 messages that day... how many seconds per message is that?
Me: *Thinks for 5s* about one message every 20 seconds
Cyan: *ignores me, uses a calculator*
Cyan: ~20 seconds per message...
Me: Told you
Cyan: How did you do that??
Me: 86400 sec per day / 4000...
Cyan: o_o