Remote
moody
@moody@hj.9fs.net
snac 2.95
9front, vocaloid and old games. I guard the nightly 9front builds.
Plan 9 only alt: @m00dy@mastodon.sdf.org
Plan 9 only alt: @m00dy@mastodon.sdf.org
0 Followers
0 Following
22 Posts
Joined February 02, 2024
pronouns:
he/him
github:
website:
Replying to
The change in question[0] was even made by an employee of Anthropic.
[0] https://github.com/tmux/tmux/pull/4744
teto should have been the 9front mascot over cirno
fyi https://git.9front.org/plan9front/9front/2e21c09e8cdbca26aa3b069699239467e1fabc40/commit.html
Thanks to @khm@hj.9fs.net for helping draft these rules.
Thanks to @khm@hj.9fs.net for helping draft these rules.
Also can confirm the dspico can boot the inferno-ds code, albeit it's more than a bit jank.
I have no excuse now to not write a GBA library for 9front.
& knuckles
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
% { 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
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
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
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.
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.
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 want 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.
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 want 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.
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.
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
Linux bad
Feeling like a cig summer.
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.
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?
Correction: I'm an idiot. Reference: https://words.filippo.io/128-bits/
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%
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....
Replying to
Or look close enough to a system they already support to make it work ala openbsd.
CC: @lanodan@queer.hacktivis.me
Replying to on tech.lgbt
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: @asj@tech.lgbt