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

Hello everyone, Hoshino Lina here! I'm a developer VTuber!
I also help run VT Social!

EN/日本語｜she/her｜🎨 #HoshinoLinArt｜My gf: @cyan 🩵｜We are @TokyoHackerGirls

Model https://x.com/NananoNanase
Design https://x.com/shiranui_illust
PFP https://x.com/7783__
🦋 @lina.yt
📨 lina@lina.yt
💲https://lina.yt/sponsor

Public Key

npub14w78207els8vs5fxduhhval0r9zgujpf2khcqyfuhmkt2tlyvcyq2zuequ

NIP-05 Address

lina@vt-social.mostr.pub

Profile Code

nprofile1qqs2h0r48lvlcrkg2ynx7tmkwlh3j3ywfq54ttuqzy7tam949ljxvzqpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43qynefep

Publishing to

relay.ditto.pub

Author Public Key

npub14w78207els8vs5fxduhhval0r9zgujpf2khcqyfuhmkt2tlyvcyq2zuequ

Show more details

Last Notes

2026-05-25 13:24:53 UTC

Apple has a ton of internal system AudioUnit plugins and some of the names are amazing
BeamIt
BuzzKill
Carter
ControlFreak
Lando
LittleLateNightMode
LoudnessWarrior
LowFlow
MeisterStueck
Scotty
ToneMeister
https://media.vt.social/media_attachments/files/116/635/434/486/033/560/original/4c17a6fda9c0ffa2.png
https://media.vt.social/media_attachments/files/116/635/434/478/707/709/original/f8a843f7b50376ed.png

2026-05-19 12:53:03 UTC

- reply

@nprofile…m9jv Yeah that's what I use most of the time these days.

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-06 06:31:23 UTC

- reply

@nprofile…ya2l 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-02 06:19:13 UTC

- reply

@nprofile…tc7m Sigh...

2026-05-02 00:36:24 UTC

Why does Mastodon not have even an attempt at nuclear block? Someone can just reply to you, block you, then your server will diligently stop you from viewing their posts but everyone else still can in your replies??
Even Twitter does better than this. I get that with federation it's tricky to fully nuke a reply, but at least your local instance should be able to hide replies of blocked users from everyone else local and from queries for context from other instances??

2026-05-01 07:38:53 UTC

- reply

Replies: "This model supposedly is safe"
*Looks inside*: Huge pile of web scraped data without consent and ignoring licenses.
Seriously, this is a tragedy. LLMs are useful. You might not be able to train ChatGPT without stealing, but you can totally train a useful base model for task specific fine tuning without stealing. Why is almost nobody even trying????

2026-05-01 06:23:00 UTC

- reply

So far the only one I've seen that credibly can claim to be free of copyright concerns is KL3M (it was created... by lawyers).
Are there any others?

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-30 05:11:34 UTC

- reply

@nprofile…nx9p TBF it's about one full 42U rack, going by the numbers (photo shows half of it, looks like 10U per chassis and there's 4), so about one (large) fridge worth of servers (and many, many times the power consumption of two office towers).
Still nothing compared to LLM training of course ^^

2026-04-29 02:37:02 UTC

This is not okay. Trolling a FOSS project showing off a zero day instead of sending PRs or a proper security report... and the only justification given is that they didn't like a PR removing a feature, and haven't merged yet another PR opened yesterday??

2026-04-19 03:27:18 UTC

TIL that Docker by default doesn't rotate logs... which means that Docker by default will sooner or later crash and run out of disk space... and this is apparently intentional for "backwards compatibility"...

2026-04-04 11:10:11 UTC

Help!!! This is a cute little router right??
I'm showing it to Cyan and she says it's not cute!! How do I convince her it's cute? 😭😭
https://media.vt.social/media_attachments/files/116/346/127/010/095/146/original/9520d241ac86ff28.jpeg

2026-04-03 10:32:51 UTC

If you use Firefox in Fedora and you currently lose your home page setting after updates please get in touch.
There is some kind of extremely stupid bug going on and people have been talking past each other about it for years. I will get down to the bottom of this.

2026-04-02 23:04:21 UTC

- reply

@nprofile…6qkh "I don't use Fedora any more".
Great.

2026-04-02 08:58:17 UTC

- reply

@nprofile…6qkh I DMed the person who started that Reddit thread, but I'm going to be so annoyed if they don't want to help... "I just want them to remove the stupid homepage" is a pretty likely response...

2026-04-02 08:48:02 UTC

- reply

@nprofile…6qkh That's fair, but like, sigh.
It's really sad that in all these years nobody sat down and actually reported this properly... and we still don't know what causes it.

2026-04-02 08:41:38 UTC

- reply

@nprofile…6qkh No, that setting is and has always been there. It's a defaults change. You and everyone else seeing this bug are incorrectly assuming it is "applied on updates". It never was, and there never was any mechanism for it to be.
It is, and has always been, a bug. But everyone who hits it assumes it's evil packaging.

2026-04-02 06:01:45 UTC

- reply

@nprofile…6qkh I just tried Firefox 119 in a Fedora 39 distrobox. Upgraded to 132, no reset. Carried over the profile to 149 on F43, no reset.
I really don't understand how some people could hit this all the time and some people never saw it...

2026-04-02 05:35:07 UTC

- reply

@nprofile…6qkh I just did a manual test with FF 143 -> 144 -> 149 and it was fine...
I wonder if it has something to do with upgrading Firefox while it's running? That has a habit of crashing it, I wonder if that somehow corrupts preferences?

2026-04-02 05:14:27 UTC

- reply

@nprofile…6qkh Because apparently everyone who has it happen thinks it always happens, and nobody actually bothers to report the bug, and then someone sees it on Fedora and thinks it's intentional, and it turns into an echo chamber of people spreading FUD saying it's all an evil Red Hat plot.
If you are experiencing a bug, *especially* if you are experiencing it consistently and releatable

2026-04-02 04:56:47 UTC

This thread is such a massive failure of the community bug reporting process.
https://www.reddit.com/r/Fedora/comments/1s8jevj/a_message_to_fedora_devs_please_stop_interfering/
Apparently there's a small but significant fraction of users who see their browser home reset to the Fedora home on Firefox updates or other circumstances... and they're all convinced this is some kind of evil intentional Fedora packaging feature that hijacks your preferences on every update, and that it must happen to everyone (it does not).
So far there is one known hypothesis for why this can happen (it involves Firefox Sync), but that doesn't cover all instances because some affected users claim not to use Sync. I reported this one upstream so hopefully there will be a solution soon. Nobody had until now...
Meanwhile, not a single affected user has bothered to write up reliable repro steps or follow through with maintainers on tracking down the root cause.
I've also looked at upstream bugs and found several shaped like "Firefox lost my prefs on upgrade", but none of them were followed through to a root cause either.
Of course, when Firefox loses the home page pref and it reverts to about:home, people shrug and set it back... but when Fedora Firefox does the same and it reverts to start.fedoraproject.org, it's clearly a Red Hat conspiracy to hijack people's browsers and they demand Fedora remove the default home page branding override entirely, instead of working with a developer to get the bug fixed...

2026-03-20 13:57:22 UTC

Cyan: I feel so bad! It's Friday night and I'm not posting anything! It's the best time for engagement!!
Me: Oh, really? Is that more important than this?
*Long kiss*
Me: You can post about that~✨
Cyan: .......... you post it ><

2026-03-09 14:49:07 UTC

- reply

@nprofile…r3vy FYI your instance seems to have a very old display name cached for me (that it is using for mentions) ;;

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-03-09 11:42:19 UTC

- reply

And honestly, reading the Claude output, it's just ridiculous. It clearly has no idea what it's doing and it's just pattern-matching. Once it found the flag it spent 7 pages of reasoning and four more scripts trying to verify it, and failed to actually find what went wrong. It just concluded after all that time wasted that sometimes it gets the right answer and sometimes the wrong answer and so probably the flag that looks like a flag is the flag. It can't debug its own code to find out what actually went wrong, it just decided to brute force try again a different way.
It's just a pattern-matching machine. But it turns out if you brute force pattern-match enough times in enough steps inside a reasoning loop, you eventually stumble upon the answer, even if you have no idea how.
This sucks.

2026-03-09 11:28:24 UTC

- reply

This is, quite frankly, the same problem LLM agents are causing in software engineering and such, just way worse. Because with CTFs, there is no "quality metric". Once you get the flag you get the flag. It doesn't matter if your approach was ridiculous or you completely misunderstood the problem or "winged it" in the worst way possible or the solver is a spaghetti ball of technical debt. It doesn't matter if Claude made a dozen reasoning errors in its chain that no human would (which it did). Every time it gets it wrong it just tries again, and it can try again orders of magnitude faster than a human, so it doesn't matter.
I don't have a solution for this. You can't ban LLMs, people will use them regardless. You could try interviewing teams one on one after the challenge to see if they actually have a coherent story and clearly did the work, but even then you could conceivably cheat using an LLM and then wait it out a bit to make the time spent plausible, study the reasoning chain, and convince someone that you did the work. It's like LLMs in academics, but much worse due to the time constraints and explicitly competitive nature of CTFs.
LLMs broke CTFs.

2026-03-09 11:28:15 UTC

- reply

So it's not surprising that an LLM can solve them, because it automates the process. That just takes all the fun and all the learning out of it, completely defeating the purpose.
I'm sure you could still come up with challenges that LLMs can't solve, but they would necessarily be harder, because LLMs are going to oneshot any of the "baby" starter challenges you could possibly come up with. So you either get rid of the "baby" challenges entirely (which means less experienced teams can't compete at all), or you accept that people will solve them with LLMs. But neither of those actually works.
Since CTF competitions are pretty much by definition timed, speed is an advantage. That means a team that does not use LLMs will not win, so teams must use LLMs. This applies to both new and experienced teams. But: A newbie team using LLMs will not learn. Because the whole point is learning by doing, and you're not doing anything. And so will not become experienced.
So this is going to devolve into CTFs being a battle of teams using LLMs to fight for the top spots, where everyone who doesn't want to use an LLM is excluded, and where less experienced teams stop improving and getting better, because they're outsourcing the work to LLMs and not learning as a result.

2026-03-09 11:27:58 UTC

There's a lot of discourse on Twitter about people using LLMs to solve CTF challenges. I used to write CTF challenges in a past life, so I threw a couple of my hardest ones at it.
We're screwed.
At least with text-file style challenges ("source code provided" etc), Claude Opus solves them quickly. For the "simpler" of the two, it just very quickly ran through the steps to solve it. For the more "ridiculous" challenge, it took a long while, and in fact as I type this it's still burning tokens "verifying" the flag even though it very obviously found the flag and it knows it (it's leetspeak and it identified that and that it's plausible). LLMs are, indeed, still completely unintelligent, because no human would waste time verifying a flag and second-guessing itself when it very obviously is correct.
But that doesn't matter, because it found it.
The thing is, CTF challenges aren't about inventing the next great invention or having a rare spark of genius. CTF challenges are about learning things by doing. You're supposed to enjoy the process. The whole point of a well-designed CTF challenge is that anyone, given enough time and effort and self-improvement and learning, can solve it. The goal isn't actually to get the flag, otherwise you'd just ask another team for the flag (which is against the rules of course). The goal is to get the flag by yourself. If you ask an LLM to get the flag for you, you aren't doing that.
(Continued)

2026-03-09 04:10:48 UTC

Cosmic Princess Kaguya watch-along NOW with Cyan!!!
https://www.youtube.com/watch?v=2TFNWaKnl5Y
https://media.vt.social/media_attachments/files/116/197/257/634/697/711/original/2e82218538c408d6.jpg

2026-03-09 02:14:06 UTC

- reply

Honestly it feels like AI is... something like optimizing for nitpicking "best practices" while completely missing the real issues.
Nobody writes code according to all "best practices". Error handling in the example above is an anti-pattern. This isn't a kernel. Littering your code with NULL checks for memory allocation (and functions which can only fail due to memory allocation failures behind the scenes, like fdopen) is a net negative because it achieves nothing (if small mallocs are failing you code is going to crash anyway) while making the code more obtuse and complex and hard to read, which means real bugs will slip through more often.
If you're the kind of person that cares about having more "strictly correct" code... you shouldn't be using C to begin with, but rather a language where doing that doesn't hurt readability (like Rust). But AI isn't going to give you that advice...

2026-03-09 01:17:50 UTC

Out of curiosity, I wanted to see if ChatGPT noticed the bug/mistake I mentioned here:
https://github.com/obsproject/obs-studio/pull/13198#issuecomment-4019545931
I pasted the relevant function in and... it nitpicked all sorts of irrelevant stuff about error handling (allocation failures etc), types, and API contracts, and completely missed the actual issue. It even mentioned "the use of CLOEXEC is reasonable" and the fact it conflicts with some logic branches was completely missed.
This is a function using standard POSIX APIs. This isn't even obscure code, it's doing something (spawning a process with a pipe) that has been done a million times before.
It just didn't catch this bug because this bug / a similar shaped bug wasn't in its training data. Because AI isn't intelligent, it's still just fancy autocomplete and can't think.
("But you didn't catch it either" - I wasn't reviewing the whole function when I wrote that PR, I was fixing a different bug and had some tunnel vision since I was just normalizing/extending/fixing a pattern that was already there, so I didn't notice the use of CLOEXEC earlier. But I did ask ChatGPT to review the whole function, not just the PR change.)

2026-03-04 11:05:19 UTC

- reply

@nprofile…9ula You can only add devices on a filesystem that is already mounted RW!

2026-03-04 08:21:58 UTC

- reply

I didn't actually do the dm thing (I was using an image file I could just expand), but if you actually wind up needing to do this, there's an example in the second snippet here:
https://docs.kernel.org/admin-guide/device-mapper/linear.html#example-scripts

2026-03-04 08:14:23 UTC

Someone brought up the issue of running out of space on btrfs and not being able to delete stuff. There are posts about this from years ago, but I wanted to see if it's still a problem.
The answer is... kind of, if you try hard enough and do absolutely unhinged things. I had to create a snapshot of a tiny (4GB) but full (data + metadata) filesystem with hundreds of thousands of files (with data, with xattrs, and empty to fill everything up) and then delete files without deleting the snapshot, retrying when I got an error and sync()ing the filesystem every time. At one point I managed to make the FS go read-only, and then remounting again and trying more torture in parallel shells eventually got it wedged into a state where it couldn't mount R/W at all (cannot do orphan cleanup due to -ENOSPC).
Even then, the FS was still mountable R/O (so all the data was recoverable). And even then, I found a way out: although you can't add a device to a FS that isn't mounted R/W, you can expand the base device with btrfs filesystem resize --offline, and you can use dm to glue two devices together temporarily for this purpose. I was able to mount R/W then, delete stuff the "proper" way (snapshots first), shrink again, and completely fix the situation.
So yeah, I don't think this is really a problem any more, more specific bugs notwithstanding. You have to try really really hard to cause the issue and even then there's still a way out.

2026-03-03 14:04:11 UTC

I just caught up with a friend and she was like "so your stories with Cyan are real?? I thought it might be a bit because it's so incredibly cute I wasn't sure if that was possible!!"
Yes it's real girl!!! I'm sorry I know our life is too anime to be believed 😭😭

2026-02-28 14:59:00 UTC

- reply

@nprofile…s6dx The LiDAR sensor on those devices is on the back, not the front ^^

2026-02-28 14:57:38 UTC

🩵 WEDDING ANIMATION TEASER REVEAL!! 🩵
I'm marrying @nprofile…cer5 later this year!!
We put together a professional animation for the event, come watch the teaser!! ✨✨️
https://youtube.com/watch?v=O0Xt_wctgBg

2026-02-28 05:57:32 UTC

Another common misconception: iPhones don't have "LiDAR" sensors in front.
The Face ID / TrueDepth camera is a standard infrared camera using SLS (structured light sensing).
In other words, it's a miniature Kinect 1.
Apple bought the company that built Kinect 1 to build this!
This is in contrast to Kinect 2, which uses a Time-of-Flight camera which *is* a form of LiDAR (Flash LiDAR). https://soul.art is another company using ToF LiDAR sensors for motion tracking.

2026-02-28 05:12:37 UTC

- reply

(For those new to this stuff, there's two kinds of reverse engineering: the kind you do to build an actual product/software you release for widespread use, and the kind you do for research, education, or security. The rules are really different. This would be the second kind.)

2026-02-28 04:58:17 UTC

- reply

But I'm pretty sure that, specifically, is totally possible because I did poke around and it's just a framework and some ML models that run on the Neural Engine and Macs have all the same hardware. iPads run the same chips even.
Just not really legal to actually do in prod.

2026-02-28 04:55:12 UTC

- reply

Just to be clear this would absolutely not end up with anything you could legitimately use for VTubing.
At *best* you'd get a proof of concept "download some files from iPhone firmware and run them on a Mac to see it work at your own legal risk" thing.

2026-02-28 04:52:58 UTC

Would anyone be interesting in streams researching/reverse engineering ARKit face tracking?
This would be for educational purposes only, and to demystify some things (not to outright clone it, that would not be legal). Maybe I could get it to unofficially run on a Mac?

2026-02-28 03:07:48 UTC

Cyan: Help me find my bra~
Me: *digs through clean clothes pile*
Me: I can't find any... how do you always lose your bras??
Cyan: Hmm... do you think there might be one in the refrigerator?
...............
Me: Just where do you keep your bras???????

2026-02-22 06:51:40 UTC

- reply

@nprofile…zvpj Time to take a snip at the butt end of a smaller PCIe socket? www

2026-02-21 14:37:06 UTC

Me: Move over, you're on top of the futon
Cyan: *moves over just a bit*
Me: *pulls hard* nngngnngngng *gives up*
Me: Why do you always do this???
Cyan: It's hard getting under~
Me: But you have to fix it later anyway!!
Cyan: *I* don't 😏
Me: 🤨🤨🤨

2026-02-19 15:16:01 UTC

- reply

I'll still be mainly on Discord while this and other things cook but... watch what this guy's doing. He gets it!

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-19 03:28:45 UTC

If you're wondering what distro to choose, I keep hearing good things about Nobara, which is a Fedora derivative focusing on gaming out of the box. I haven't tried it myself yet, but I can vouch for the Fedora base it's built on.
https://nobaraproject.org/
I personally recommend the KDE edition!

2026-02-19 03:11:04 UTC

Streamers! If you're considering switching to Linux, be careful choosing Linux Mint!
Mint is based on a 2-year release cycle, so your software will sometimes be 2 years out of date.
It might be stable, but you will miss out on new features. Not great for a fast-moving world like streaming!
There's nothing wrong with Mint, and the stability and slower-paced upgrades are just right for some people, but it's probably not what you want if you're streaming.
I personally recommend Fedora, which has a 6-month release cycle, but there are many other options too.

2026-02-10 03:30:17 UTC

CYAN IS TOO CUTE AAAAAAAAA!!!!!!!!!!!!

2026-02-07 07:35:12 UTC

Did you know that the tech Spout2PW uses, PipeWire, is also used for webcams on Linux these days? And also screen capture!
There are some details to work out, but it should eventually be possible to use Spout2PW streams as virtual cameras with no additional software!

2025-10-19 12:49:58 UTC

Nya! ✨️

2025-08-20 02:30:38 UTC

- reply

@nprofile…7rvs wait WHAT? Nobody told me this!!!

2025-08-13 12:45:11 UTC

@nprofile…efrv Looks like kmsro is not the only explicit sync bug in GNOME... https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8571

2025-08-13 12:01:05 UTC

Cyan and I just lost two boxes of sushi. Like, lost.
We bought three, she ate half of one, I ate the other half, and the other two are just nowhere to be found.
I checked the fridge, the trash, the floor...
????????????

2025-08-13 03:40:09 UTC

- reply

I think this is really the case where these LLMs are actually useful:
- Mindless work where it would take a human longer to automate (writing a script using a translation API)
- It would take a human longer to do manually
- There is no creativity involved other than trivial/irrelevant stylistic choices
- The major bottleneck for a human is I/O (typing/reading speed)
- There is little to no risk from invalid output/hallucination

2025-08-13 03:36:03 UTC

Used ChatGPT for the first time ever to bulk translate/rename a bunch of emote files...
This kind of thing it's actually good at ^^
https://vt.social/media/media_attachments/files/115/019/360/186/871/832/original/955faabed774f6c8.png

2025-08-06 16:13:25 UTC

Luna is so petty and shameless that she reported my receipts of her abuse to Google Docs and had them taken down.
Therefore, they are now hosted on my personal web server.
https://asahilina.net/luna-story
https://asahilina.net/luna-abuse

2025-07-29 14:01:54 UTC

- reply

@nprofile…et0z Yeah, I know. I was thinking I might be able to just "abuse" the screencast source by hijacking the PW connection with something else, or else just extract out the OBS PW stuff into a separate plugin so I can prototype with it.
Actually making this user-friendly has to wait for the portal stuff, since unfortunately the camera trick isn't going to work if it doesn't do dmabuf...

2025-07-29 13:38:12 UTC

Spout2 Windows sender demo on Proton/DXVK, texture sharing to a Linux OpenGL window!
With OBS PipeWire window capture, that counts as a Spout2 to Linux OBS solution, right?? ^^;;
Next stream, going straight to PipeWire/OBS!
https://vt.social/media/media_attachments/files/114/936/789/776/791/483/original/0798a7feafa84ea3.mp4

2025-07-29 05:09:51 UTC

Just to clarify, I'm back to streaming and development, but I have no plans to return to kernel work. I hope all my viewers understand.
What happened was too hurtful to bear and nothing has been resolved.

2025-07-27 11:26:52 UTC

- reply

@nprofile…mfsm It's Flatpak on the Steam/Proton side that would be an issue, I think OBS should be fine as long as the existing PW plugin already works with Flatpak. But I might have missed something, @nprofile…et0z knows more ^^
Also this does require Proton right now, Spout2 doesn't work with upstream Wine yet sadly.

2025-07-27 11:22:42 UTC

- reply

@nprofile…mfsm It will be a Windows service you install into your Wine prefix (no GUI). The initial version will just expose all Spout senders automatically as PipeWire virtual cameras. In the future there will be some kind of portal integration instead (which is required for Flatpak).

2025-07-27 11:18:11 UTC

- reply

@nprofile…mfsm Sure! It'll probably go through a few iterations where it's kinda janky at first (likely won't work with Flatpak at first, then it'll take a bit longer before that gets fixed)

2025-07-26 06:02:20 UTC

- reply

@nprofile…et0z That's what I plan to work on tomorrow ^^;;

2025-07-26 03:55:32 UTC

Change of stream plans! I'll be doing more Goose Game tonight with Cyan and I'm moving the Spout2 on Linux stream to tomorrow ^^
Sorry for the last minute change!

2025-07-12 03:48:00 UTC

METR: "We ran a randomized controlled trial to see how much AI coding tools speed up experienced open-source developers.
The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't."
https://bsky.app/profile/metr.org/post/3ltn3t3amms2x
(emphasis mine)

2025-07-10 16:27:45 UTC

Why do I have a few seconds of BIRDBRAIN stuck in my head in endless loop????

2025-07-08 12:25:24 UTC

- reply

@nprofile…ghnt Data is stored by trapping electrons, and electrons have some mass.

2025-07-08 12:23:20 UTC

Silly math of the day: A modern SSD gets around 0.05 picograms heavier for every terabyte of data you store in it.
(This is back of the napkin math, I might easily be off by a factor of 10.)

2025-07-08 08:17:11 UTC

Yes, a file full of zero bits transfers faster over USB2.0 than a file full of one bits.
I've known this forever but it still feels ridiculous when you actually test it and it's true!
USB truly is cursed.
https://vt.social/media/media_attachments/files/114/816/617/319/047/895/original/92a90bf41f807f8f.png

2025-07-01 15:21:37 UTC

Slowly getting set up to stream again... I have a Fedora change to OBS to enable the Browser Source ready, but Fedora infra is down for maintenance so I can't submit the PR right now ^^;;
Next I need to figure out how I'm going to run the 3D models...

2025-06-30 18:06:57 UTC

- reply

@nprofile…m3qg @nprofile…x759 @nprofile…fepu Right, that's what I would expect! PNG isn't smart enough to do literal sprite/tile mapping but zlib compression is still pretty good at eliminating the duplication, and does a better job within tiles themselves which makes up for it in other ways.
What I meant is the original "this screenshot of SMB is larger than SMB" meme probably used a really degraded screenshot, which is not the case here.

2025-06-30 12:29:25 UTC

- reply

@nprofile…m3qg @nprofile…x759 @nprofile…fepu The image is 10 kB ^^
It would actually be kind of sad if a clean PNG screenshot were larger than the whole game, since PNG should be pretty good at eliminating redundancy the same way the original game does!
I think this meme probably originally happened with degraded images (stuff like JPEG artifacts compressed as PNG again) which adds a bunch of hard to compress noise.
(Also, the game is technically 40KiB, 32K code + 8K graphics)

2025-06-29 11:35:03 UTC

- reply

@nprofile…359z This solution is built upon mature Wayland components for compositing and display backend that are mature, modern, future proof, and already work better than the Xorg equivalents today.
The bugs in the integration bits, which are comparatively simple are a lot easier to fix than legacy Xorg DDX technical debt.

2025-06-29 09:26:23 UTC

If you still need to run an X11 session instead of Wayland (e.g. for accessibility use cases not covered yet, or old school software/WMs) then forget about cursed Xorg forks, *this* is the future-proof way!

2025-06-23 13:18:13 UTC

- reply

@nprofile…7rvs Pat pat. I think Plasma 6.4 has that, which was released a few days ago? But I guess apps need to support it too...

2025-06-23 13:11:15 UTC

- reply

@nprofile…7rvs Maybe it's worth trying with a fresh user account and seeing what the experience is there? Sometimes when you've been carrying over desktop configs for many years the migrations don't quite happen right or you end up with weird setting combinations that nobody can test with current software... and switching X11 to Wayland could bring out some cursedness there.

2025-06-23 09:24:25 UTC

- reply

@nprofile…7rvs Scrambling the monitors is normal... it's a different display backend so however X11 identifies them won't map. The same thing would happen in the other direction. You probably also have to reconfigure DPI etc...
I don't know about the pen thing though, I've never tried that ;;

2025-06-18 10:14:45 UTC

- reply

@nprofile…pfgd XWayland isn't blurry on KDE ^^
I still don't know why GNOME and others haven't fixed this yet...

2025-06-18 09:54:27 UTC

- reply

@nprofile…dj52
Most of the issues KiCad is pointing out aren't Wayland protocol limitations, they are bugs in their implementation or the toolkit's (wxwidgets). Those go away under XWayland. The rest are mostly window management issues where XWayland gets to do things with extra privilege, and it also works fine.
I just tested this. The panel docking, the window position restoring, etc. all works under XWayland. If there are any specific bugs with repro steps that affect XWayland and not native X11 I'd love to know about them!

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-28 11:01:17 UTC

- reply

@nprofile…et0z Unfortunately packaging old versions of CEF is a huge pain due to needing backport patches for a lot of stuff, and I also get all the security bugs assigned to me and need to backport fixes. Plus the new CEF (133+) finally has a versioned API, which makes it viable to have a systemwide install.
So I don't think it's viable to ship the old version at this point, I already tried that once with the obs-cef fork a year ago and it was unmaintainable...
Maybe OBS can use Fedora users as a canary for issues with the new CEF?

2025-05-28 10:46:55 UTC

- reply

@nprofile…et0z Ahh, so basically UX polish stuff and the issues with browser profiles then.
I think it makes sense to delay the upgrade for official OBS releases then, so there are no regressions. But it probably doesn't make sense to delay packaging the browser source in Fedora for me, because right now it doesn't work at all, so making it work with limitations is still better than nothing.

2025-05-28 10:39:24 UTC

- reply

@nprofile…et0z What are the blockers? As far as I can tell it works fine for me (but obviously I didn't do extensive testing).

2025-05-28 10:14:58 UTC

- reply

@nprofile…et0z I mean, at least it works. I'm running it right now.
Don't those old versions have critical security vulnerabilities? Like CVE-2025-3619 (first random one I found). It doesn't sound very safe if OBS is still shipping old CEF even though it works with newer versions...

2025-05-28 10:03:40 UTC

- reply

@nprofile…et0z OBS supports the latest CEF now (136).

2025-05-28 09:57:17 UTC

So I'm trying to get the OBS Browser Source working again. I accidentally launched OBS twice... and the second instance crashed, and this popped up.
I knew CEF was based on Chromium, but I didn't know it was actually capable of launching a full-blown browser window by accident! 🤯
https://vt.social/media/media_attachments/files/114/584/849/272/293/787/original/6762ed6df356944f.png

2025-05-27 12:54:05 UTC

- reply

Final build times:
M1 Ultra: 98.1 minutes
Ryzen: 109.4 minutes
So the M1 Ultra ended up being around 15% faster!

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-12 05:18:01 UTC

I haven't been very open publicly about this before, but working on Apple GPU drivers was, indirectly, the majority of my income until now.
Due to Luna's manipulation and attacks, I'm now left coasting on savings trying to figure out how to survive long term.
I'm not in imminent danger of being homeless or anything, but it's an unstable situation, and now I worry about how long my savings will last.
If VTubing and little gigs don't work out, I might have to get a full time in-office tech job, and that would mean the practical end of my VTubing career.

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-27 05:23:35 UTC

The WireGuard MTU stuff is so tricky...
1440: safe for IPv4 outer layer
1420: safe for IPv6 outer layer
1400: safe if outer layer is IPv4 over ds-lite
1392: safe for IPv4 over ds-lite over PPPoE
But wait, FLET'S PPPoE in Japan has extra encapsulation... your PPP packets get sent through L2TP, then UDP, then IP, then Ethernet, adding 46 bytes of overhead (1454 MTU).
1394: safe for IPv4 on FLET'S PPPoE
1374: safe for IPv6 on FLET'S PPPoE
1354: safe for DS-Lite over FLET's PPPoE (does anyone do this????)
1344: round down to multiple of 16 for the MTU mismatch issue.
So it looks like to roam on WG VPNs in Japan, I need to set the MTU to 1344 to avoid problems.
(And now I know why my connections were hanging in this hotel...)

2025-04-26 11:21:28 UTC

I just discovered something really subtle about WireGuard... TL;DR if you are adjusting interface MTUs precisely, and you have mismatched MTUs between peers in some cases, make sure your smallest MTU is always a multiple of 16!
WireGuard header overhead is said to be 32 bytes + UDP + IP, so 80 bytes for IPv4 and 60 bytes for IPv6. That's where you get the default MTU of 1420 (1500 - 80, so it works with IPv6).
But that's not precisely true! Actually, WireGuard will add up to 15 bytes of padding to the data, to make it a multiple of 16, as long as it doesn't exceed the MTU on that side of the connection.
So let's say you have a server with the MTU set at 1440, but you also have a client that is using IPv4 over PPPoE. So you set its MTU to 1432, subtracting the PPPoE overhead of 8 bytes. That should be fine, since the client will figure out the right path MTU for any connections, right?
Wrong!
The TCP client and server will negotiate an MSS that gives 1432 byte IP packets within the tunnel. But 1432 is not a multiple of 16! However, the client WireGuard instance knows that there is no headroom, so it will send 1432 + 60 = 1492 byte packets, which is the maximum PPPoE MTU. But on the way back, the server thinks it can go up to 1420! 1432 % 16 == 8, so it will try to round up to 1440. Then, it sends 1500 byte MTU packets, which don't fit in PPPoE!
The fix is to either set both the client and server MTU to 1432, or to round down the client MTU to 1424.

2025-04-02 06:46:19 UTC

- reply

@nprofile…d98k They keep crafting new accounts...

2025-04-01 17:10:37 UTC

- reply

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

2025-04-01 17:08:14 UTC

- reply

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