Lightnews — Scholar-powered news

puppy

@duckinator.bsky.social

440 followers 46 following 160 posts

a pile of small dogs in a meaty land vessel • KC1QGV • they/them prone to creating technological cognitohazards #rustlang, #rubylang, #pythonlang, #cprogramming

Posts Media Videos Starter Packs

Pinned

puppy @duckinator.bsky.social · 16d

behold, my latest technological cognitohazard github.com/duckinator/j...

jim/lib/jim.rb at 528d641d02b32a5104ef24a3b6d70fd3f52eb835 · duckinator/jim

jim likes gems. Contribute to duckinator/jim development by creating an account on GitHub.

github.com

2 3 4

puppy @duckinator.bsky.social · 10h

I stumbled across this just now, and it reminded me of what I said in the immediate aftermath of this shit on the 19th:

bsky.app/profile/duck...

puppy @duckinator.bsky.social · 21d

To me, there is a difference between being nice and being kind.

Being nice is avoiding confrontation and keeping the peace.

Being kind is grabbing your friend by the shoulders and telling them how they fucked up, and what they need to do to make it right.

When being nice fails, be kind.

puppy @duckinator.bsky.social · 16h

Every step of the way, we have engaged in good faith.

Every step of the way, they decided to treat us as disposable and shit on our reputations.

Ruby Central needs to take a real good look in the mirror, stop digging themselves into a deeper hole, and make some very significant and public changes.

1 15

puppy @duckinator.bsky.social · 16h

Until Ruby Central starts acknowledging when and how they fucked up without trying to shit on other people's reputations as a diversion, we will keep seeing these clown shows.

1 5

puppy @duckinator.bsky.social · 16h

Putting people in an organization that GUARANTEES they never have accurate & complete information is a recipe to turn missteps into circus acts.

But to make it worse, Ruby Central is acting like they're more interested in starting new conflicts than resolving existing ones, consequences be damned.

1 7

puppy @duckinator.bsky.social · 16h

The first SIX PARAGRAPHS of "Why Did Ruby Central Treat This Event as a Security Incident?" should have been ONE SENTENCE:

"Ruby Central was informed some credentials were not rotated after an operator's access was revoked."

Everything else is noise to distract from their operational mistakes.

André Arko @indirect.io · 1d

Ruby Central said some really concerning things today. I don’t think they’re representing the situation accurately. andre.arko.net/2025/10/09/t...

The RubyGems “security incident”

Ruby Central posted an extremely concerning “Incident Response Timeline” today, in which they make a number of exaggerated or purely misleading claims. Here’s my effort to set the record straight. Fir...

andre.arko.net

1 1 16

puppy @duckinator.bsky.social · 1d

Communities build out, not up: pup-e.com/blog/build-o...

Defaulting to rubygems[.]org already causes dependency confusion.

By embracing the idea of multiple smaller gem hosts, and making our tools accommodate that in a secure way, we address risks from centralization *and* dependency confusion.

Communities build out, not up

pup-e.com

puppy @duckinator.bsky.social · 1d

It's difficult to figure out the right balance.

Too little structure, and everything is run on norms and cooperation — so the second someone doesn't cooperate and violates those norms, you're fucked.

But on the flip side, too much structure makes a project collapse under its own weight.

puppy @duckinator.bsky.social · 1d

Yeah. I've seen this problem everywhere from "5 teenagers set up a small IRC network and shit goes sideways" back in like 2005-2007, up to the Gittip crisis a decade ago (no way to replace a leader who was harming the project), to the last month with Ruby Central and RubyGems.

1 3