| Github | https://github.com/armahillo |
| Tech Blog | https://armahillo.dev |
| All My Links | https://aaronh.me |
| Github | https://github.com/armahillo |
| Tech Blog | https://armahillo.dev |
| All My Links | https://aaronh.me |
Arko provides hella more clarity than RC's IR: https://andre.arko.net/2025/10/09/the-rubygems-security-incident/
The attachment is a perfect encapsulation of how badly RC effed this up, and why this takeover was not done in good faith. Not only did they not know what services were being used by the team, they didn't consider the ramifications of locking out the existing administrative team (NONE OF WHOM WERE BAD ACTORS).
I'm currently at v15.5 on my M1 Max; I thought I was current
How did we suddenly get to v26.x????
https://gist.github.com/simi/349d881d16d3d86947945615a47c60ca
Another maintainer leaves #rubygems after the hostile takeover by ruby central.
The lack of actiom and redress here is blaring. They have now had days to try and stop the bleeding, but havent. At this point it seems like a _choice_.
screenshot 🎯🎯🎯
If there was good faith here, they should revert the ousters, and maintain that state of things until these steps could be followed.
Like, come on.
These could literally just be `section` instead of `.section`!
*screams into keyboard*
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/section
If you are writing HTML and you have a sea of DIV tags, maybe quickly review some of the other block-level elements.
Tired of seeing `<div class="section">` and `<div class="paragraph">` and `<div class="main">` etc.
The <section> HTML element represents a generic standalone section of a document, which doesn't have a more specific semantic element to represent it. Sections should always have a heading, with very few exceptions.