GauntletWizard

Haruhi already did it, though it's sadly been lost to time: https://www.reddit.com/r/anime/comments/3xmlb2/spoilers_haru...

I loved the Endless Eight, personally, but I watched them one a day after the event was over. Having read the LNs, I knew what was coming as soon as I got a whiff from the internet of the first episode, so I just held off, waited until it was over, and enjoyed.

I'm always happy to discuss sound cards with mixers, though! As a supporter of the Bloop Museum[1], I think that the "What might have been" if we had dedicated hardware for playing dozens or hundreds of sound files at a time is an interesting question. There's a lot of experimentation in the audio space that has kind of died out, because audio is so cheap - While over in in graphics, we're still seeing interesting advancements and dead ends.

[1] https://oldbytes.space/@bloopmuseum

This turned out to be entirely the right approach, though, and it was probably pretty obvious even at the time. Sound Cards with built in mixers have all but died out. Everything they did has been eaten by software,

Even at the time, few games used an API where they managed multiple channels directly; Software mixing was commonplace from the 90s. Any game that wanted to play battle sounds was not relying on the mere 6-8 channels that cards from that time could handle.

Our modern Pipewire based workflow is remarkably simple and remarkably effective, and it's significantly an evolution of PA.

SEEKING WORK | Seattle | Remote OK

I am a Site Reliability Engineer (SRE), Google Style, with experience at both large and small organizations. I can help you build a Platform Engineering practice from the very beginning. I'm looking to help small dev teams increase their velocity by implementing best-practices of Devops: CI/CD, Kubernetes Deployments, and effective Monitoring frameworks.

My resume: https://resume.gauntletwizard.net/ThomasHahnResume.pdf

My LinkedIn: https://www.linkedin.com/in/thomas-hahn-3344ba3/

My Github: https://github.com/GauntletWizard

Do also check out "The Day the Earth blew up", a love letter to the classic cartoons that simultaneously feels like a featuring film, and a cartoon short. Not the best thing I've ever seen but I'd give it a solid eight out of 10.

I'm so glad Coyote is finally getting a release. It was top of my watchlist all through 2022-2023, the test screenings went over fantastic, and I've heard a lot of people involved in the movie saying that it turned out great.

The decision from WB to shelve it was just cruel; It was 100% paid for and the work to complete it was ongoing and completed, even after it was shelved. A deep flaw in our tax system that it could ever be better to trash completed work than to try to find a buyer.

When I had the brief displeasure of working on HDFS at Facebook, we took a series of customer meetings to figure out how to get our oldest customers to upgrade their clusters. I was in a meeting with the photos team about what their requirements were and what was blocking them from upgrading, and they were very frank - they asked if the upgrade preserved the internal struct types associated with blocks on the disc servers. They didn't actually use hdfs as a file system, they allocated 1 GB files with zero replication, then used deep reflection to find the extent that comprised them on the discful storage servers, then built their own archival backup file system on top of that. I was horrified. The some of the older hats on the team were less surprised, having had some inkling of what was going on, even though they clearly didn't understand the details. Others considered it tantamount to sacrilege.

I think about this a lot. What they had built was probably actually the best distributed file system within Facebook. It was similarly structured to unraid, and had good availability, durability, and space saving properties, but the approach to engineering was just so wrong headed in my opinion that I couldn't stomach it. Talking about it with other Java programmers within facebook, nobody seemed to mind. Final was just a hint after all.

The atomic weight of Uranium is 238; the atomic weight of Oxygen is 16. By weight, Triuranium octoxide is ~84% Uranium. Even if you're only counting the uranium in the Triuranium octoxide, that's still 60+% of the total mass coming from Uranium Atoms. I'd take that purity any day.

Whenever I get mad at GitHub Actions, I refer to it by it's true name: VisualSourceSafe Actions. Because that's what it is, and it shows. If you check out their Action Runner's source code[1], you'll find the VSS prefix all over, showing it's lineage.

[1] https://github.com/actions/runner/blob/6654f6b3ded8463331fb0...

You may want to wholesale import The Jargon File. Badly out of date at this point, but surprisingly relevant and of more than moderate value as a historical reference.

Yes, Chrome introduced support in mid 2023, and it's now well rolled out. Firefox has had support for longer.

https://issues.chromium.org/issues/40685439

This is a pretty nice guide, though it misses some steps I'd consider important. If you're making a CA for internal use today, I would highly encourage you to use Name Constraints. Name Constraints allow you to specify that your CA will only be used to sign domains you pre commit to. This means you can add your internal CA to your system trust stores on all of your corporate systems and not worry about it being abused to MITM your employees connections to the wider internet. (If that is a feature you'd like to have, I would be happy to expound further on why that's a bad idea)

I'm giving a workshop in a few weeks at Bsides Seattle[1] about this - Pick up a Yubikey and come play with PKI with me.

[1]https://www.bsidesseattle.com/2025-schedule.html

Saml is insecure by design. Others have said it better before me, such as https://joonas.fi/2021/08/saml-is-insecure-by-design/, but the quote I got from an old thread here was "Sign Bytes, not meanings".

Parser differentials are expected and even necessary. What you intend to get from a signed response is very meaningful. A dilemma in modern TLS is that sometimes you want to trust one internal CA; That's the easy path. Sometimes you want to accept a certificate from a partner's CA, and you've got multiple partners - and you can no longer examine just the end certificate, but the root of that chain is equally important in your decisions.

This is also why I recommend whenever possible against AWS Sig algorithms; V4 is theoretically secure, but they screwed it up twice - SigV1 and SigV3 were insecure by design, and yet somehow made it past design review and into the public.

These are dang short compared to Java's FooBarBazBeanFactoryFuncClassImpl. The point you may be responding to is that "Short variable names" are themselves contextual. If you're doing a simple loop:

  for i := range personlist {
    person := personlist[i]
    ...
  }

Is more readable than

  for personNum := range personlist {
    person := personlist[personNum]
    ...
  }

because it makes clear that the i is basically irrelevant. The latter isn't bad style if you're three loops deep, because i, j, k is a bit harder to keep track of which is which.

Right, but a ton of well-meaning but cure-is-worse-than-disease "Web Application Firewall" tools still block it

They no longer teach Rhetoric at schools. Rhetorical arguments have been completely forgotten and debased in the public mind.

Rhetorical arguments are more important than ever in the age of AI, because AI is our attempt to simulate that. Probabilistic AI mimics rhetoric (inexpertly). It uses past knowledge to predict future behavior (rather, just the next token) based on probability.

To be clear - I'm not arguing that logical argument aren't important; I am a logical person, and prefer logical arguments to rhetorical ones. I prefer the certainty. I still recognize the need for rhetoric. Not everything is certain, and you have to make decisions based on probabilities and unknowns.

I trust Tailscale with my network traffic. I also trust a $50 cheap chinese 10G switch that I bought off amazon with a terrible and surely insecure management interface. Which is to say - I don't, but I don't need to trust it far.

I do have enough trust in their client that's installed on my machine to believe that it's not actively malicious. I do trust that I can find my other devices, and trust tailscale to keep a list of them, and not randomly add other devices that I don't know, but I don't have perfect trust of that. All my internal services are still E2E encrypted over the Wireguard link; They run HTTPS with an internal cert authority. There's not ports open on them that shouldn't be, and while it's possible that one of them still gets popped, it's much less likely.

It's pretty sad. I'm in the process of moving, and while I did so, I shucked much of my DVD collection - Everything is in three ring binders now, because they're so much more convenient, and much smaller in my storage.

While I was doing so, a bunch got ripped and transcoded into Jellyfin. It's pretty great, having them available all the time. Piracy is obviously an option, but it's not a great one.

What? I really want out of my DVDs, though, is the assurance that I've got the same DVD as other people do. Advent of AI, there's no reason that I couldn't be being fed a different version of every show I watch than everyone else. I know. They could be rendering stuff in real time. It's not that far off. The nice thing about a hard copy is that it can't be changed on you.

There's other ways of doing this of course, but having talked to library scientists of late, they are not nearly the right kind of paranoid for what I'm afraid of.

SEEKING WORK | Seattle | Remote OK

I am a Site Reliability Engineer (SRE), Google Style, with experience at both large and small organizations. I can help you build a Platform Engineering practice from the very beginning. I'm looking to help small dev teams increase their velocity by implementing best-practices of Devops: CI/CD, Kubernetes Deployments, and effective Monitoring frameworks.

My resume: https://resume.gauntletwizard.net/ThomasHahnResume.pdf

My LinkedIn: https://www.linkedin.com/in/thomas-hahn-3344ba3/

My Github: https://github.com/GauntletWizard

And the fact that these scam centers primarily target rich western countries that are at political odds with the CCP?

I made it to College half a semester off from being a Junior. You can get a ton of college credit before college; and then I quit before I flunked out because I never learned study skills.

Browser support for it is pretty new, which is why it's so often missed. It only happened in mid/late 2023.

I've been shopping a talk since then about how to set up a name-constrained root certificate, and what it should look like. It's still hard! CFSSL is my go-to tool, and it doesn't have support. I had to fork it to make it work. OpenSSL has support, but it's configuration is like all OpenSSL configuration - Poorly documented and nonstandard, mixing INI objects and object-refs.

Yes, actually - You can hear how individual that scream is and how small the applause is compared to the rest of the clapping, and how the crowd goes more silent as he brings up that point.

The correction says "Nominated" not won, but it's still a really interesting story.

I would also recommend everyone see Christopher Tin's acceptance speech for the Grammy for "Baba Yetu" https://youtu.be/TM_WzFnmtac , the first piece of videogame music to win a Grammy - There's an awkward silence as he mentions it, and I remember articles at the time about artist who felt "Cheated" because it went to a Videogame score, because they felt it was somehow lesser.

I could have sworn I saw a Youtube video version of this article, but I can't find it in my history. I was reminded of another unusual end of line station, though: One you can't leave, because it's inside the campus of Toshiba.

https://youtu.be/zVpLuZxsHq0

Which part of the Youtube terms of service did it violate?

About ten years ago I did https://digthisvegas.com/ - I had a great time, definitely recommend.

SEEKING WORK | Seattle | Remote OK

I am a Site Reliability Engineer (SRE), Google Style, with experience at both large and small organizations. I can help you build a Platform Engineering practice from the very beginning. I'm looking to help small dev teams increase their velocity by implementing best-practices of Devops: CI/CD, Kubernetes Deployments, and effective Monitoring frameworks.

My resume: https://resume.gauntletwizard.net/ThomasHahnResume.pdf

My LinkedIn: https://www.linkedin.com/in/thomas-hahn-3344ba3/

My Github: https://github.com/GauntletWizard

The only thing getting pegged in stable coins are the idiots left holding the bag.

This "would get you immediately fired" at Facebook 10 years ago. It happened a lot. It only gets you fired if you get caught and you only get caught if someone complains; the security teams aren't so much asleep at the wheel as there's a mannequin at the wheel so nobody notices what nobody notices.

I am both strongly of the opinion that this was already done much better in Bazel, and that the go-native version seems clean, clear, and simple and should probably be adopted by pure go shops.

The digraph problem of build tooling is hardly new, though the ability to checksum all of your build tools and executables and mid-outputs to assure consistency is relatively new to feasibility. Bazel is a heavy instrument and making it work as well as it does was a hard problem even for Google. I don't know anyone making the same investment, and doubt it makes the slightest hint of sense for anyone outside the fortune 500.