moody

https://hj.9fs.net/moody

9front, vocaloid and old games. I guard the nightly 9front builds.

Plan 9 only alt: moody (npub16lf…a673)

pronouns: he/him
github: https://github.com/majiru
code: https://only9fans.com/moody/usr.html
website: https://posixcafe.org

Public Key

npub1juzmcp2ud36d9c6zpd6r9st0jgv76ufecmknq4r9dk2zy7e259sqjjeyat

NIP-05 Address

moody_at_hj.9fs.net@momostr.pink

Profile Code

nprofile1qqsfwpduq4wxcaxjudpqkapjc9heyx0dwyuudmfs23jkm9pz0v42zcqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsz4hct2

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1juzmcp2ud36d9c6zpd6r9st0jgv76ufecmknq4r9dk2zy7e259sqjjeyat

Show more details

Last Notes

2026-08-10 17:28:20 UTC

After trying to get a hold of anyone in the wireguard project to take a look at my implementation for 9front over the past 2-3 months (and one email of intent with a rough sekeleton PoC over a year ago). To be clear there's no expectations here, but after the FreeBSD debacle I get the impression they want to ensure some bar of quality for implementations with the wireguard name so I figured I'd ask. Ah well.

2026-08-07 19:37:33 UTC

The ported and trimmed ml-kem code now runs and passes all of the wycheproof test vectors:
https://shithub.us/moody/mlkem-wheat/8cd56dd073eff14a4be0b3bdd1d1ef718a1031de/wych.c

2026-08-06 19:16:56 UTC

- reply

Fixed.... phew.

2026-08-06 03:29:55 UTC

Of course I forked mlkem-native right before they added more test vector coverage and now it's catching bugs I should have caught during my trimming....

2026-08-04 15:50:32 UTC

flan% wc -l mlkem.c
1961 mlkem.c
flan% mk
6c -FTVw main.c
6c -FTVw notrandombytes.c
6c -FTVw mlkem.c
6c -FTVw verify.c
6c -FTVw randombytes.c
ar vu mlkem.amd64.a mlkem.6 verify.6 randombytes.6
ar: creating mlkem.amd64.a
a - mlkem.6
a - verify.6
a - randombytes.6
6l -o 6.out main.6 notrandombytes.6 mlkem.amd64.a
flan% 6.out
Shared secret: 776c74df301f8d82525e8ebbb40095cd2e92df6dc933e7866259f531c7350ad5
[MLKEM-512] OK
Shared secret: e91377840e6b6694eaa9f01c97ff68874e8b0c520b00c2cde37c4fc239626e70
[MLKEM-768] OK
Shared secret: 5d9e235fccb2b3499a5f490a56e3f0d3fd9b58bda28b690f91b57b88a5a80b90
[MLKEM-1024] OK
flan%

2026-07-30 17:31:51 UTC

- reply

I've been trying to wrap my head around this stuff. Right now I'm just messing around but if other systems start enforcing PQC (looking at you ssh) or for stuff like TLS I'd rather have some idea of what's going on.
CC: @npub19av…rp6r

2026-07-30 16:33:13 UTC

- reply

thanks khm. Clearly I've got some more reading to do.

2026-07-30 16:06:07 UTC

How is https://radar.cloudflare.com/post-quantum going to claim all this shit about post quantum while I still connect using an AES128 block cipher? I thought due to Grover's algorithm AES128 is now considered broken if your threat model includes PQC?
https://hj.9fs.net/moody/s/post-65c436019d283edc35976e0ea4f522c3.png

2026-07-28 15:50:41 UTC

- reply

Of course there is low hanging fruit on all these codebases. Not a ton of people wake up and think "let me digest the domain information for some specific susbsystem in a kernel and audit it for bugs". There are certainly some but the process is grueling and time consuming. We incentivize hackers with promise of recognition and in some cases monetary awards and even then stuff moves slowly.
But this is selling both the problem and the solution, and people have been wringing alarm bells to make this stuff systematically better for longer than I've been alive. To throw that out and say "yeah give up guys it's over just pay the troll tax if you want your project secure" is dismissing all over the work we have made thus far.
I've spent time looking at this like stack canaries for 9front, looked at how to better handle memory and I admit that getting this stuff right is hard and it requires a lot of work but the work you put in to that will pay more in dividends than just flipping the chess board and outsourcing it.

2026-07-28 14:43:32 UTC

6l -o 6.out main.6 test_only_rng/notrandombytes.6 mlkem.amd64.a
flan% 6.out
Shared secret: 776c74df301f8d82525e8ebbb40095cd2e92df6dc933e7866259f531c7350ad5
[MLKEM-512] OK
Shared secret: e91377840e6b6694eaa9f01c97ff68874e8b0c520b00c2cde37c4fc239626e70
[MLKEM-768] OK
Shared secret: 5d9e235fccb2b3499a5f490a56e3f0d3fd9b58bda28b690f91b57b88a5a80b90
[MLKEM-1024] OK

2026-07-26 22:55:02 UTC

- reply

it was a copilot Linux binary. I find it funny that they specifically avoided mentioning that.
Arguably them having their own mascot there is worse because it means they paid for the privilege.

2026-07-23 22:55:13 UTC

- reply

Spirits are def the best domestic cig I've found here. So I'm with you there. I need to get better at hand rolling cinap has to reteach me every 9front hackathon.
CC: @npub1nt0…5520

2026-07-23 22:49:50 UTC

- reply

Or look close enough to a system they already support to make it work ala openbsd.
CC: @npub127u…p52c

2026-07-23 22:35:02 UTC

I was traveling when the linux llm shite broke so I didn't get much of a chance to scream in to the void so here I am. I have said as much before, but I think people underestimate what percentage of their definition of 'usable computer' is only possible by the grace of companies. If your idea of usable operating system precludes a modern web browser I hope you have friends at google or mozilla. If your idea of a usable operating system is one with working modern GPU drivers I hope you have friends at Nvidia or AMD. In other words, corporate interests have already captured your favorite popular operating system and have tied their own insurmountable(by outsiders for the most part) work to the very definition of what a ie functional linux system is for desktop use.
Point is, if you want if you want anti-llm operating systems and software, you know where to find it, you just cant expect it to coexist with corporate interests and perhaps we could be a bit more honest about how much that impacts what folks define as a 'usable' system.
I say this, posting from a linux install, so I sit comfortably in my glass house. However I think we need to stop fooling ourselves in to thinking linux or any product propped up by corporate involvement as anything but a corporate product. Expect no better of Torvalds than you would the CEO of Microsoft, their money comes from the same place after all.

2026-07-17 21:19:20 UTC

Feeling like a cig summer.

2026-07-17 19:05:05 UTC

Linux bad

2026-07-17 15:24:17 UTC

- reply

9front as well!
https://git.9front.org/plan9front/9front/b8126cd97f5e52580ffa328f8ba3bbf39b3569ec/lib/legal/contributing/f.html

2026-07-02 03:55:56 UTC

Still not "done" but its close enough that I feel comfortable sharing here: https://shithub.us/moody/wg/HEAD/info.html
wireguard for 9front in ~1300 lines of C

2026-06-28 21:56:53 UTC

- reply

Thanks for taking the time to both acknowledge my concerns and provide your own perspective on how you view these problems. I wish you all the best in your efforts to tackle these issues. :)
CC: @npub1p8f…tcuc

2026-06-28 20:42:45 UTC

- reply

Yes it is the Linux kernel with its GPL license and millions of dollars per year donations from Microsoft which is truly the bastion of user freedom! I just love buying a new phone or car running a Linux kernel and being able to load up my brand new modified-by-me kernel on it the same day I buy it :D! Even better that all the companies using the Linux kernel to profit would never be able to use that kernel to restrict my freedoms! That simply can't happen with the all mighty GPL :D. Never mind the fact that some modern Linux distro's default to using google or cloudflare dns! The code shoving your bytes up for them to see is GPL! Never mind that Google takes a peek at all the text in any sort of Android push notification, its running a GPL kernel baby!
No, no clearly it is OpenBSD with its dumb idiot stupid BSD license that is really trampling user freedoms >:(. They are so stupid don't they understand that if they simply used the GPL like Linux they too could never ever ever be possibly used to hurt someone's freedoms. Gosh I am so cool to have portrayed them as the dumb idiot cuck and myself as the smart GPL user.
CC: @npub19yg…w8um

2026-06-28 19:53:26 UTC

- reply

I don't think you need to make perfect the enemy of good, but it has been decades and the best improvement we've had to this idea is the AGPL which closes one loophole. I mention these deficiencies because I feel like they are often understated, and while effective at some level, time would be better spent thinking about how to push this method of "attack" (shrink wrap contracts that have all the right clauses you want), than to continue to promote something which falls short.
However it's worth noting that many of these same organizations who are the primary caretakers of GPL code, like the Linux Foundation, are not interested in fixing these loopholes. To them its a feature that hyperscalers dont have to show you their secret linux kernel sauce. Its a feature that Android can be arbitrarily locked down without people having recourse (yes I know Graphene and its great but I think its telling that they only support Pixels).
CC: @npub19yg…w8um @npub1p8f…tcuc

2026-06-28 19:22:28 UTC

- reply

No I am neither misunderstanding or misreading it. As you've also pointed out many users of the GPL think it does things it does not, it appeared to me that the blog author here also misunderstands the GPL and that's what my first point was, that the GPL as written does not do what the author thinks it does. My basis for thinking the author misunderstands that is as follows: they think the GPL stops corporations from doing bullshit, corporations are doing bullshit with GPL code, I don't know how the author blindly ignored all instances of that.
Second I am not afraid of 'the scary bad words' my point is that having a misunderstanding and using _any_ inflammatory dialogue about those who disagree with you is low brow at best. When you couple that with a misunderstanding of the GPL license you get something that is barely worth linking.
To use specific examples from their post, they point to MINIX not being GPL and that being used to violate freedoms. To which I give a counter example of all of the privacy violating portions of Android. Android, despite using a GPL kernel, is locked down to high heavens, full of vendors not respecting GPL requests, and an active participant in the surveillance state more often than not. So I ask how did the Linux kernel being GPL prevent this from happening?
CC: @npub19yg…w8um

2026-06-28 19:00:34 UTC

- reply

Then it does not serve the purpose that it is being attributed to by this blog post or in similar discourse. So I don't see how this blog post is persuasive. "I use the GPL because I think it does something it doesn't and the people who don't agree with me are cuckholds" is not the flex you think it is.

2026-06-28 16:57:42 UTC

- reply

Ah yes the GPL, which has prevented large companies like Google, Microsoft and Amazon from selling said GPL software back to you......
Attempting to use IP law and shrink wrap contracts as a way of combating multi billion dollar companies is not going to be effective unless you have a comparable legal war chest. Even less so at an international level.
I understand the desire not to have corporations profit off your work without you getting a cut, but one look at the Linux foundation tells you that if that is the stated goal of the GPL, it failed.

2026-06-23 19:38:55 UTC

- reply

or even a vm. The system deserves more than being relegated to a glorified toy taking up space in your junk drawer.

2026-06-06 00:15:38 UTC

- reply

As someone who has spent a decent bit of time with 9front I can not recommend this work as a medium to learn about the Plan 9 operating system unfortunately. The author has also admitted to using LLMs for some of this work.

2026-06-01 17:21:06 UTC

All I wanna do today is play some Minecraft and listen to Dr. Menzes talk about PQC.

2026-05-22 01:51:50 UTC

- reply

This was not "hidden" I was pretty up front about it in irc. But feel free to point and laugh at me as you typically do.

2026-05-21 17:20:46 UTC

My comment on the recent "Acme AI agent" thread on 9fans stating that I'm done was censored (for some reason, not even remotely heated) so instead I am posting some thoughts here.
I have over the past maybe 4 years or so attempted to rebuild the bridge somewhat between 9legacy folks and 9front. This was in-part driven by iwp9 happening and generally having a good time getting to meet folks outside of the immediate 9front sphere. Part of this was driven by the fact that having two semi-hostile groups is confusing for newcomers, part of this was in hopes to reduce duplicate work, part of it was looking to allow us to do more by working together. I was not here when this fissure between these two groups started, so I thought perhaps we could bury the hatchet and everyone would be better off.
Trying to do this is messy, and I'll be the first to admit that I'm no saint, if you go looking you'll find plenty of heated posts from me to 9fans. However, slowly bit by bit, I felt like things were slowly improving. Folks were airing grievances and for once it felt like there was some actual listening and improvements. One part of this was the 9front git force push to get rid of some jokes that haven't aged well, the final list of which was done in conjunction with the p9f for something everyone agrees with. The hopes of doing that was that with this clean up we could finally get some recognition on the main websites (p9f.org et all), however despite us doing the work of the force push nearly a year ago(which involved a risky and involved change to our update mechanism) there has been no change to any recognition.
As we'll see this becomes a recurring theme, expectations that 9front developers and maintainers should shoulder the lion-share of the work burden for doing something. Over the past couple of years we've gotten drive-by PRs made by some 9legacy folks, and when there is any sort of additional questions or requests for changes the response we get is almost one of insult. I want to be more charitable but it comes across as "how do you question MY change to your shitty fork". As soon as someone says anything the result is "well I'm just going to take my toys and go home then". The final boss of this was this vibe coded crapola PR sent to us for us to roll back a bunch of uses of our new interfaces in git (many of which were done to make the code more maintainable) to make it compile out of the box on 9legacy.
Not to mention that after being clearly stated that 9front does not accept computer generated software, no one was willing to answer the question of if they used it. No one wants to admit anything inconvenient. No one wants to communicate or solve problems together. They don't want to make 9front better, they want to use it for their own uses and make that our problem. So I'm sorry but I just don't to work with the p9f and their community if this is the result. Other 9front community members warned me this would be the outcome but I wanted to believe otherwise.
Its important to note that I dont have anything against any of these folks personally, I'd happily have a drink with anyone, at the end of the day we have something in common if we're still using Plan 9, but liking someone and working together are two different things. I also want to make a carve out for Richard Miller, who has carved his own path and continuously been working (mostly) in the open, large amount of respect for him keeping on.

2026-05-21 16:35:33 UTC

I was wondering why I was getting noise about this article I wrote from 2 years ago, turns out it was reposted to lobsters two days ago (and then cross posted to reddit). Despite my article being a reflection of how poorly the conversation around this vague "philosophy" is, and how the history is a bit more nuanced than people expect, all of the comments opt instead to just state their own ideas in vague relation to this vaguely defined philosophy and all that is created is more of the same noise I was complaining about in the first place.

2026-04-01 04:16:11 UTC

https://hj.9fs.net/moody/s/post-492137853c8e08d97813097c2b3124ca.png

2026-03-31 15:21:10 UTC

- reply

The change in question[0] was even made by an employee of Anthropic.
[0] https://github.com/tmux/tmux/pull/4744

2026-03-30 02:58:39 UTC

& knuckles
https://hj.9fs.net/moody/s/post-d9a53c48dcd0a6f71df985111cbf5cff.png

2026-03-26 05:32:13 UTC

For those wondering, yes you can indeed calculate a mega drive rom checksum from the comfort of your 9front rc window:
% { echo 'n=0'; xd -2w streetsofrage.md | grep -v '[0-9a-z]+ $' | sed '1,32d;s/^.* /n=trunc(n+0x/g;s/ /+0x/g;s/$/,16)/g'} | pc | tail -n 1
0x9409

2026-03-24 04:05:05 UTC

Part of the reason I played around with the TMSS is because of these statements about this Sonic 3D Blast 814 prototype from tcrf.net[0].
Essentially stating that the ROM contained the string "Nosegay is a word." somewhere in the high end parts of the rom, and this was done specifically as a way to bypass TMSS checks. To be clear neither this or any of the Phys-Q dev kit games actually use this value, likely just bundled in with the provided software kit. Perhaps a known "legal backup" to be deployed after a C&D.
Looking through the tmss disassembly it seems like it would work, it only checks that next 4(5) bytes at 0x100 contain either "SEGA" or "SEGA" with a leading space. However you have two leading bytes you need to stuff before 0x100, which would bleed in to a copy of the ErrorTrap interrupt handler address, which very possibly is not used at all on hardware. However you still have to deal with the TMSS register inside of the IO controller itself which must be filled with 2 values containing exactly "SEGA". You could fill this straight from the rom header data without having to embed an explicit "SEGA" constant again. So it seems like yes, NOSEGAY is a valid mega drive rom header as long as you define the header to start 2 byte early.
I was curious because the overdrive demo uses a header value of "SEGA MEGA DRIVET", so I was curious what the exact checks are.
[0] https://tcrf.net/Proto:Sonic_3D_Blast_(Genesis)/814_Prototype

2026-03-23 21:56:54 UTC

My rabbit hole for last night: https://git.9front.org/plan9front/9front/598072cc6d9e221e47dc1a5958fb0b11d074db40/commit.html
games/md now can fully make use of a standard mega drive tmss rom. Not sure I've seen other emulators do this but I'm not super well versed. Would be fun to take it as a demo challenge, just 4k of rom to do something with.
https://hj.9fs.net/moody/s/post-8b26cd2efeed72406bc96fa2661e5d98.png
https://hj.9fs.net/moody/s/post-a2b9096a198f308666ab9ac53a30ba34.png

2026-03-14 05:52:50 UTC

SEGA mapper in games/md.
https://hj.9fs.net/moody/s/post-4267117f9715a3fd3ce9a66b889ad88a.png

2026-02-04 23:20:26 UTC

Reading the latest UTC notes, it seems the C2PA (a group tasked with marking AI content with some sort of watermark, sponsored by some of the worst offenders ironically), has decided the best way to tack on "metadata" to plain text as AI is to encode arbitrary data into a string of Unicode variant selectors[0] slapped onto a Zero-Width No-Break space (U+FEFF). This is not only a relatively ineffective watermark being completely trivial to strip, but is a pretty flagrant abuse of variant selectors.
[0] https://spec.c2pa.org/specifications/specifications/2.3/specs/C2PA_Specification.html#embedding_manifests_into_unstructured_text

2026-01-31 01:01:50 UTC

I did not expect 9fans to start posting lots of AI generated code, but in hindsight I should have seen it coming.

2026-01-19 15:28:46 UTC

- reply

I'm not aware of any issues (at least that I've seen or heard about). I know vulture sometimes does rolling upgrades when a vm is restarted, did the issues coincide with that?

2026-01-15 17:43:21 UTC

- reply

Just a bit, let's see if it captures my attention enough to max this time.

2026-01-14 19:19:32 UTC

The reason why 9front work has been slow lately.
https://hj.9fs.net/moody/s/post-5e636e40861bf0540cb1ca62ce8f75fe.png

2025-12-20 04:31:20 UTC

- reply

Hellaphone lives again.

2025-09-11 19:52:54 UTC

- reply

but but but what about my USE flags? How else am I going to get my software with 2000 knobs tuned to just my liking?

2025-09-10 03:24:33 UTC

Day 1 Unicode v17.0 support on 9front for normalization, grapheme break and word break.

2025-07-19 01:41:36 UTC

Testing the beta for Unicode v17.0 for 9front, thankfully this time no changes are needed for our normalization algorithm. All lights are green, and we're prepared to launch on release day.

2025-05-01 06:15:23 UTC

I've been mulling over the idea of attempting to create a custom build of 9front for the purpose of using it as a networking appliance. A NAT router box, some p2p vpn thing, etc. Something akin to OPNsense in a way. Would people be interested in that? What would you do with it? Is this a terrible waste of time?

2025-04-10 04:57:21 UTC

note: someone will make fun of you for this
https://hj.9fs.net/moody/s/df9a512e928a36d29a8accdccf119627.png

2025-03-09 19:39:34 UTC

- reply

Fantastic.

2025-03-08 18:52:03 UTC

- reply

There was an initial pass for unicode support, to at least not barf on it, but there was some lingering issues that prevented its use in identifiers.

2025-03-08 05:45:37 UTC

9front's yacc now supports Unicode in identifiers, can your water buffalo do that?

2025-02-09 00:29:47 UTC

I may have mentioned this before but wanted to again in case people haven't seen, 9front does have a riscv64 userspace (albeit not very well tested) and what we're really missing is someone working on a kernel (even if only for qemu). I did a decent chunk of that work and would be willing to act as support for the userspace(compilers libraries and so on) portions if someone wanted to try taking on that project. There is a start to a kernel, enough to jump in to virtual memory. I've still got the kernel portions of the power9 port to work on but considering the userspace stuff is at a decent place acting as support is doable.

2025-02-06 03:20:42 UTC

[@robpike@hachyderm.io](https://hachyderm.io/users/robpike ) During the original work on Unicode support in Plan 9, was there any consideration for the Non-Spacing Marks, like the Diacritical attaching runes? I'm just curious if it was due to a lack of approval of those portions of the standard or if it was avoided out of the amount of technical work needed to support it given the current code.

2024-10-10 11:27:23 UTC

Happy teto day
https://hj.9fs.net/moody/s/a2d217ab5e5f66b5f2c25ce671cf46ee.jpg