Found out this morning it was a prank call to UCPD. All good.

Yeah, as a programmer in Library IT, I am a bit concerned by this as well (which is why I hopped on social media at why-am-I-awake-o'clock) - let me know if you find out.

What's not working: the pure JS fallback. The library I hoped would work did not. If there is anyone out there in my audience that is a WebAssembly expert, please poke me in DM.

I want to heart this because he's finally not going to be superintendent.

But that's not a great purpose in life either, really.

If there really was a looming threat, this was the worst way to handle it. The community is likely to follow projects/forks led by the people who were unceremoniously removed - so any threat they know of, but are not sharing, can't be properly acted upon. And that's a no-win scenario for Ruby.

At this point, what @rubycentral.org has done is a form of supply chain attack: taking ownership of a widely used repository, and then denying access to its existing maintainers.

This reminds me of the GitHub mass-assignment bug. That is not something you want to remind me of if you want goodwill.

Yeah, software supply chain attacks are scary. They keep me, and many others in the Linux packaging world - and the greater DevOps world - up at night.

The solution is not ripping access from maintainers that we have long-standing relationships with. This gives the opposite of trust.

Project leadership is hard, and you want people the community trusts there. *Especially* during transition periods, if that is what they are really wanting, it is vital to maintain a sense of continuity.

These moves are contrary to OSS ethos, not to mention basic human dignity.

This statement from @rubycentral.org does not give me the warm and fuzzies; transparency, equity, and collaboration in an open-source style do not happen in the dark, nor can they happen without honesty and dialogue with existing contributors.

Thank you for all your work in this space - and so many others. This was definitely not a move that was deserved nor warranted. It's been a while - would love to catch up sometime!

Did you ever figure out a better workaround? I'm seeing this with Capybara / RSpec system tests using Selenium Hub with Chromium nodes. It's totally random, and totally annoying - it makes about 1 out of every 3-4 CI runs we have fail.

They all feel the same 🎵 [drums]

Also: if you’re a privacy activist, watch NCMEC. US legislators will track to their position on this pretty quickly if things come under discussion. You can’t imagine how many doors opened for me because I was on their Board.

😂😂😂😂