| Profile | https://www.godfat.org |
| GitLab | https://gitlab.com/godfat |
| GitHub | https://github.com/godfat |
| Taiwanese |
| Profile | https://www.godfat.org |
| GitLab | https://gitlab.com/godfat |
| GitHub | https://github.com/godfat |
| Taiwanese |
@rozeboosje yeah, as far as I can tell, the translation is fine.
But sharing a video where the entire audio and even the lip movements have been faked to make it believable, hiding the fact that this is not the original but an interpretation – that's just dishonest.
Subtitles/voiceovers adequately serve the same purpose without pretending to be the original source.
Towards an amicable resolution with Ruby Central
https://andre.arko.net/2026/04/02/towards-an-amicable-resolution-with-ruby-central/
Last week, three members of Ruby Central’s board published a new statement about RubyGems and Bundler, and this week they published an incident report on the events last year. The first statement reports that Ruby Central has now completed a third audit of RubyGems.org’s infrastructure: first by the sole remaining RubyGems.org maintainer, the second by Cloud Security Partners, and the third by Hogan Lovells. In all three cases, Ruby Central found no evidence of compromised end user data, accounts, gems, or infrastructure availability. I hope this can conclusively put to rest the idea that I have any remaining access to the RubyGems.org production systems, or that I caused any harm to the RubyGems.org service at any time.
禪與 NPM 維修的藝術
RE: https://thepit.social/@peter/116329254798253700
I remembered I kept arguing with the review bot that we don't need fallbacks or error handlings due to various reasons with regard to the context of the code. For a few times the review bot referred to the merge request title rather than the actual code :/ Eventually I won all the arguments and the review bot conceded defeated, but I wasn't really satisfied but annoyed, thinking that this was quite counterproductive.
I kept arguing partially because I had concern others might mistake.
If i can slip in a quick PSA while my typically sleepy notifications are exploding, these are all very annoying things to say and you might want to reconsider whether they're worth ever saying in a reply directed at someone else - who are they for? what do they add?
{thing} itself is people being surprised at {thing}": unless the person is saying "i am surprised by this" they are likely not surprised by the thing. just saying something doesn't mean you are surprised by it, and people talking about something usually have paid attention to it before the moment you are encountering them. this is pointless hostility to people who are saying something you supposedly agree with so much that you think everyone should already believe it{thing}"{thing} might be bad, but {alternative/unrelated, unmentioned, non-mutually exclusive thing} is even worse": multiple things can be bad at the same time and not mentioning something does not mean i don't think it's also bad{thing} is bad also think {alternative/unrelated, unmentioned thing} is good": closely related to the above, just because you have binarized your thinking does not mean everyone else has.anyway if the mental image you are conjuring for your interlocuters positions them as always knowing less than you by default, that might be something to look into in yourself!
I didn't really like being called software engineer (even when I highly appreciate software engineering) because I felt it's missing the idea of design, creativity, and craft. Looking at the incident of Claude Code leak though, (chuckle) that's way too creative for my taste. I already appreciate the term software engineer more lately, and I think I'll appreciate more and more in the future given the era of LLM generated codes.
At least I am entertained!
I joined RubyCentral to release a postmortem, and today I'm delivering my report on what happened. The hope is to provide more transparency and closure, 194 days since the incident on September 18, 2025.
I've named the incident "RubyGems Fracture." For full details, read my report. #ruby
https://rubycentral.org/news/rubygems-fracture-incident-report/

By: Richard Schneeman This document attempts to give closure to the Ruby community about the events that led to the incident, September 10-18, 2025, which I’ve named “RubyGems Fracture.” Preamble I joined Ruby Central’s Open Source Committee on October 22nd, 2025, after the GitHub access changes. I was