Joel “this is bs” Drapper

@[email protected]
1.8K Followers
686 Following
53 Posts
Full-stack #Ruby / #Rails / #TypeScript / #CSS engineer, CEO of #HTMX, formerly at Clearscope and Shopify — author and maintainer of the gems #Phlex, Morphlex, Literal, Quickdraw — cohost the @rooftop podcast.
bloghttps://joel.drapper.me
githubhttps://github.com/joeldrapper/
email[email protected]
blueskyhttps://bsky.app/profile/joel.drapper.me
Show threadJoel “this is bs” Drapper3d ago
It’s also available here. They’re trying to suppress this. http://gofile.me/6g3JG/oTY79Vk3b
Access via Synology

Click here to open the link

Joel “this is bs” Drapper3d ago
I appealed the YouTube takedown but I also uploaded the video to the internet archive. https://archive.org/details/gmt-20250917-160422-recording-640x-360
Ruby Central meeting with RubyGems maintainers : Free Download, Borrow, and Streaming : Internet Archive

Meeting between Ruby Central and RubyGems maintainers right before Ruby Central seized control.

Internet Archive
Joel “this is bs” Drapper5d ago
E Corp had the video that proved Ruby Central was full of shit taken down from YouTube. Here’s another link (not mine) that still seems to be available. http://gofile.me/6g3JG/oTY79Vk3b
Access via Synology

Click here to open the link

Joel “this is bs” Drapper6d ago
Show threadJamie Gaskins6d ago

@joeldrapper @Schneems Former ShipIt maintainer here. This is indeed how it works.

Unless RC’s ShipIt wrapper overrides this, org membership isn’t the access gate. It was designed to handle Shopify’s needs. They have SOC2 and PCI compliance to think about and org-level access controls wouldn’t survive an audit of either one.

Show threadJoel “this is bs” Drapper6d ago

@Schneems source for my claim that Ruby Central was not even set up to automatically deploy the OSS code. https://bsky.app/profile/martinemde.com/post/3lztd7r7tqc2s

I also verified this with other people familiar with operating the RubyGems dot org service.

Martin Emde (@martinemde.com)

Yep, access to shipit (deployed) was controlled by GitHub auth and a GitHub team. Change the team (to say rubycentral/rubygems-deploy) and access is completely revoked. Without access, no code goes to prod. Staging was automatic, but Production required a manual button press.

Bluesky Social
Show threadJoel “this is bs” Drapper6d ago
@Schneems but wait it’s worse than that. Ruby Central didn’t automatically deploy the open source code. So it’s just the fact that we *could* set up our production system to automatically deploy someone’s code that justifies taking over their project.
Joel “this is bs” Drapper6d ago

RE: https://ruby.social/@Schneems/116214870460984841

Richard would have us believe if we set up a production system to automatically deploy someone’s open source code then that would be sufficient justification to take over that person’s open source project.

Show threadJoel “this is bs” DrapperMar 9

Why publish now? I watched this video months ago but didn’t feel it was my place to publish it in full.

However, someone else published it today so I decided to publish it to YouTube where it’s accessible to everyone and easily shared.

Joel “this is bs” DrapperMar 9
I’ve posted the full unedited Zoom recording of the meeting between Ruby Central and RubyGems maintainers that took place on 17 September 2025, *before* the takeover. https://www.youtube.com/watch?v=FjQKOIf8_Wg
Ruby Central meeting with RubyGems maintainers [unedited]

YouTube
Joel “this is bs” DrapperMar 9

Putting this out there again: if you have any information on Ruby Central, the RubyGems takeover, sponsor involvement, the board votes, the trademark battle or the FBI reports, please contact me on Signal so I can write about it while protecting your anonymity.

My username is joeldrapper.01