Lightnews — Scholar-powered news

puppy @duckinator.bsky.social · 16h

oh, @kayila.bsky.social has one of those, and i think that's the entire reason she acquired it.

puppy @duckinator.bsky.social · 16h

me: [fidgeting with the 5lb sledge hammer that i've kept by my desk for like 3 months]

@kayila.bsky.social, perfectly describing what she is witnessing: "the autistic urge to hold something slightly heavier than you should currently be holding"

1 4 13

puppy @duckinator.bsky.social · 18h

AND THAT'S HOW I LEARNED GIT ARCHAEOLOGY.

3

puppy @duckinator.bsky.social · 18h

Let's say you used git 1.x to work on a repo with that used this general workflow:

feature/bugfix branches -> development -> main/master

And you, oh I don't know, made a feature branch off development and force-pushed that feature branch, but happened to have a 3-year-old copy of `master`?

Yeah.

1 3

puppy @duckinator.bsky.social · 18h

Context for those who are blissfully unaware:

`git push -f` does what `git push` does, but disables some checks.

Prior to git 2.0 (which is from 2014), `git push` with no arguments defaulted to pushing every branch.

1 4

puppy @duckinator.bsky.social · 18h

"git push -f, 2013"

🏰meg⚔️ @Birthright Audiobook! @impavid.us · 4d

In honor of spooky month, share a 4 word horror story that only someone in your profession would understand

I'll go first: Six page commercial lease.

1 4

puppy @duckinator.bsky.social · 1d

Is this why everyone gave up on putting separators between their navbar links starting around a decade ago?

puppy @duckinator.bsky.social · 1d

Hey #CSS / #flexbox folks:

On pup-e.com I have a `nav ul` rule with `display: flex` and `flex-wrap: wrap`

With flexbox, is it possible to only put a character between each item that's on the same row?

atm I put a mid-dot between each item, but it looks like shit if it goes over multiple lines.

A screenshot of the navigation links on my website. The first line has a mid-dot at the end, and the second line does not, so they're misaligned.

2

puppy @duckinator.bsky.social · 2d

the hard part will be the gemspec side, but i'm super excited that i was able to pull off even a proof-of-concept for this part

1 2

puppy @duckinator.bsky.social · 2d

Also: all of this is just syntactic sugar for existing functionality.

source "https://gem.example"
gem "@foo/bar"

=>

source("https://gem.example/@foo") { gem "bar" }

AND

gem "https://gem.example/@scope/gemname"

=>

source("https://gem.example/@scope") { gem "gemname" }

6

puppy @duckinator.bsky.social · 2d

What if gem hosts had NPM-like scopes & your Gemfile could be:

source "https://gem.example"
gem "@duckinator/jim"

OR:

gem "https://gem.example/duckinator/jim"

... what if a PoC patch was 25 lines, and a 1-line kludge meant you can test it against a production server?

github.com/gem-coop/gem...

A screenshot of running `bundle install` against various Gemfiles.

It shows that, with my patch, you can use scoped packages similar to what NPM provides, if you're using GitHub Packages.

1 4 24

puppy @duckinator.bsky.social · 3d

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 · 24d

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.

2

puppy @duckinator.bsky.social · 3d

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.

2 19

puppy @duckinator.bsky.social · 3d

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 9

puppy @duckinator.bsky.social · 3d

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 11

puppy @duckinator.bsky.social · 3d

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 · 4d

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 20

puppy @duckinator.bsky.social · 4d

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

1