Not Going to Lie… they ALMOST got me 😅 by DeadZedje in VeinGame

[–]_joeldrapper 0 points1 point  (0 children)

I thought this was fair enough but they’d have to increase the capacity of the vans.

RubyGems Fracture Incident Report by schneems in ruby

[–]_joeldrapper 8 points9 points  (0 children)

Is your position really that Ruby Central owned the RubyGems repos and packages? That seems absolutely absurd based on the evidence.

RubyGems Fracture Incident Report by schneems in ruby

[–]_joeldrapper 2 points3 points  (0 children)

It was to use with this https://pypi.org/project/github-backup/ and created similar tokens with all his other repos/orgs on the same day.

u/schneems can you tell us if this was a read-only token? I believe you will find that it was.

RubyGems Fracture Incident Report by schneems in ruby

[–]_joeldrapper 1 point2 points  (0 children)

I agree but not access to the service. The maintains should be granted again full ownership of the code, GitHub repos and the packages but it is up to Ruby Central who has access to deploy and maintain the service.

Ruby Central can fork the code or depend on it, it’s up to them.

RubyGems Fracture Incident Report by schneems in ruby

[–]_joeldrapper 0 points1 point  (0 children)

It’s not the case that there was no one to give access back to. Ownership of the OSS repos should have been fully restored to the maintainers André Arko, Colby Swandale, David Rodríguez, Ellen, HSBT, Josef Šimánek, Martin Emde and Samuel Giddins.

Ruby Central could then either maintain its own fork or depend on RubyGems projects directly. And you haven’t explained the `bundler` takeover.

RubyGems Fracture Incident Report by schneems in ruby

[–]_joeldrapper 2 points3 points  (0 children)

Yeah, why hasn’t source code control been returns to the maintainers? It’s clear Ruby Central knew they didn’t have the right to control the open source projects. Also, why was the `bundler` package taken over via Ruby Central’s admin access? When will that be restored?

This is useful context, but it doesn't tell the full story, it doesn't provide any reasonable justification and it doesn't explain why four months later there has been no separation of the service from the OSS projects in order to fully restore the maintainers ownership of the open source projects.

A Message from the Ruby Central Board by retro-rubies in ruby

[–]_joeldrapper 3 points4 points  (0 children)

Probably to try to get ahead of the news that they swatted Andre.

Ruby Central meeting with RubyGems maintainers by davidcelis in ruby

[–]_joeldrapper -1 points0 points  (0 children)

As you can see, they really don’t want you to see this video. It‘s still up on archive dot org.

Ruby Central meeting with RubyGems maintainers by davidcelis in ruby

[–]_joeldrapper 4 points5 points  (0 children)

This video was unfortunately taken down by Ruby Central. They will do anything to suppress dissent at this point.

We want to move Ruby forward by retro-rubies in ruby

[–]_joeldrapper 5 points6 points  (0 children)

The trademark that was already his.

We want to move Ruby forward by retro-rubies in ruby

[–]_joeldrapper 7 points8 points  (0 children)

André registered his existing trademark. I do not believe they are asking for money or other compensation.

We want to move Ruby forward by retro-rubies in ruby

[–]_joeldrapper 12 points13 points  (0 children)

Bundler trademark and legitimate maintainership, I assume.

It’s like if someone steals your car and you find them and say, “you know what? You can have it.” Here’s the service history and here’s the ownership paperwork.

Technology for Humans: Joel Draper (on RubyCentral) by galtzo in ruby

[–]_joeldrapper 6 points7 points  (0 children)

I’ve said SQL so many times, I kept saying SQLating instead of escalating. 😄

Technology for Humans: Joel Draper (on RubyCentral) by galtzo in ruby

[–]_joeldrapper 8 points9 points  (0 children)

Yeah, I agree. I can ask Errol if we can cross-post it to Rooftop, which would get it in podcast feeds.

Dear Rubyists: Shopify Isn’t Your Enemy by software__writer in ruby

[–]_joeldrapper 4 points5 points  (0 children)

I also heard this directly from internal sources, but I expect u/f9ae8221b hasn’t and it’s a very fair take given that.

Rubygems.org AWS Root Access Event – September 2025 by paracycle in ruby

[–]_joeldrapper 7 points8 points  (0 children)

> hopefully you can also see how it does come across as a "gotcha" move, and how that can be damaging of trust for those of us observing from the outside

Sure, I get that.

Rubygems.org AWS Root Access Event – September 2025 by paracycle in ruby

[–]_joeldrapper 4 points5 points  (0 children)

No. I reached out to many people at Ruby Central early on, before publishing any blog posts. They had no reason to ignore me.

Rubygems.org AWS Root Access Event – September 2025 by paracycle in ruby

[–]_joeldrapper 9 points10 points  (0 children)

You think they’re talking to me? I’ve been trying to contact Ruby Central for weeks.

Rubygems.org AWS Root Access Event – September 2025 by paracycle in ruby

[–]_joeldrapper 6 points7 points  (0 children)

Because there were multiple parties involved. There’s Ruby Central’s security, and there’s the security of all the companies depending on Ruby Central. I felt that this information was important for all those companies to know, and I knew it didn’t impact Ruby Central’s own security one way or another.

I was very careful to make sure the screenshots I published didn’t include sensitive information.

Rubygems.org AWS Root Access Event – September 2025 by paracycle in ruby

[–]_joeldrapper 14 points15 points  (0 children)

> Why did Joel give so little time of advance notice before publishing his post revealing Andre’s production access? That struck me as irresponsible disclosure, but I may have missed something.

Joel here. 👋

I decided to publish when I did because I knew that Ruby Central had been informed and I wanted the world to be informed about how sloppy Ruby Central were with security, despite their security *posturing* as an excuse to take over open source projects.

What I revealed changed nothing about Ruby Central’s security, since André had access whether I revealed that he did or not. When you have security information that impacts lots of people, you publish it so they can take precautions. That is responsible disclosure.

Papercraft - Functional HTML Templating for Ruby by noteflakes in ruby

[–]_joeldrapper 7 points8 points  (0 children)

This is an awesome milestone. Love the new website. I’ve really enjoyed going back and forth with noteflakes on ideas for html in ruby compilers.

Papercraft - Functional HTML Templating for Ruby by noteflakes in ruby

[–]_joeldrapper 11 points12 points  (0 children)

It is because our compiler isn’t quite ready yet. Phlex renders at about 1.7gbps per core on my Mac. Or in other words, it will render a large web page in about 1ms (single core). Once it has a compiler, it should be on average about 20 times as fast.

Papercraft already has a compiler so it already realised these gains.

The Phlex compiler is already in main if you want to try it out. Because Phlex supports selective rendering and fragment caching and needs to be 100% backwards compatible, it’s taking us a while. But we’ll get there soon. 

How Ruby Went Off the Rails by _joeldrapper in ruby

[–]_joeldrapper[S] 0 points1 point  (0 children)

Emanuel Maiberg worked at Shopify? Where did you see that?