the vessel of morganna / is on Nostr

welcome to my profile, where everything is made up and the toots don't matter

Last Notes

2025-04-09 00:25:40

just found out the content filter we use at work (for students) is bypassed by just adding "CrOS" anywhere in the useragent string. great quality code. can't believe we pay money for this

2025-04-07 15:31:07

- reply

@nprofile…z0w9 secret sunday #2

2025-04-07 15:31:07

- reply

@nprofile…z0w9 secret sunday #2

2025-04-07 08:14:43

12345678

2025-03-12 07:27:42

- reply

@nprofile…g7lp @nprofile…vdjy When your stack relies on exploiting a root-level RCE on a phone for quality control purposes, you know you're in the shit

2025-03-12 07:27:05

- reply

@nprofile…g7lp @nprofile…vdjy I don't think I could even remember a comprehensive list of bugs I faced when I did hosted PBX services years ago. We shipped more than 80 patches to asterisk alone, nevermind pjsip or other dependencies. We had patches for proprietary hardphone firmware. Configs were very carefully sculpted over years to maximise cross-vendor interop.

2025-02-28 01:27:55

OH:
"I don't like that -Ctx isn't a name I can read but I will suck it up
windows devs: I need to fit this light novel into this class name
unix devs: is it possible for me to name things less than a full character?"

2025-02-13 09:19:43

@nprofile…s37t dearest System76, my brand new Adder WS 4 arrived with the CPU/GPU HSF completely unscrewed and loose, and one of the MHF connectors on the wireless card was disconnected. I'm glad modern nVidia cards have fast throttling, because any 3D workload was pushing the GPU down to 26MHz immediately. I didn't even consider a heatsink problem because the laptop is brand new and assembled to order - I expected a QA pass before it was shipped.

2025-02-13 01:14:39

just got my new system76 machine and it has really weird gpu clock behavior under load, running furmark (native) for testing and getting decent framerate for a few seconds, then the gpu core clock throttles briefly before ramping back up? it's causing really weird frame pacing where it'll be <10ms for about 2s, then 300ms+ for a few frames, then back to full speed. temperatures look fine, and nvidia-smi confirms the core clock goes down as low as 26MHz when this happens. tried updating to the 565 series drivers and the same behavior :(

2025-02-04 20:15:13

4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4