Oh no, it was "git pickaxe". For some reason, I read it as Pickaxe (classic Ruby book) saving the day 😂

Out of curiosity, what was the culprit?

...to mask it, he pretends it is we the readers are too dumb to fully grasp it, and so let's leave it all in hints and ambiguities and self-referential statements.

Reread the entire series after the first part of the movie (previous was, like, in my teens).
The first one feels like he knows a story he wants to tell, the follow-ups, while frequently inventive and sometimes deep, are all like he is trying to catch "what was my point again", but ...

Some OSINTers claim they know the weapon that did it 🤔

People tend to mark "boring politics which shouldn't have a place in engineering discussions" all kinds of things!

Not only "how taxes should be structured" politics but also "who should be imprisoned/deported/killed" politics is frequently labelled as "not something we should be interested in."

They are just in desperate need of a Dear Leader To Save Them (or Die For Their Sins).
Why would one choose Navalny and not some Ukrainian in this juxtaposition?
Simple: because there was no One Dear Leader on Maidan.
But they won't say, "We don't need a Hero to lead us, we should all become one."

...and before that: bsky.app/profile/zver...

Had that eerie feeling the last time:
bsky.app/profile/zver...

I still remember times when Google Messenger (or whatever it was called then) was XMPP/Jabber-based and you could talk to it with third-party messengers :)

But I still think it all stayed nerdy-niche and all but died today because of tech. giants decided halfway that they actually don't want to promote open info exchange standards as an underlying layer for their businesses.

...just that time via social media and mailing lists revival, no "open information exchange that time."

On the other hand, I do agree that even at their peak, RSS readers were nerdy-niche (I remember being stunned by a very tech-savvy political/social journalist who never heard of the tech).

IDK, honestly.
On one hand, I think it could've been pulled off by a tech giant.
"Subscribe to this site's updates" is nothing too nerdy, unless we are trying to sell it as "an open XML-based technology, which ...".
Eventually, we got "subscribe to this site" anyway, right?

So, I think it was not The pivotal event, just the final nail "we think this tech is dead" (and, by extension, "this approach -- having common standards to openly exchange info between apps and services -- is dead").

The Reader itself as a service was just a point in a trend (and probably the last one) of Google moving away from RSS and similar open tech.
There were times when "this site has RSS" was rendered as an icon in Chrome's address bar; IIRC, having it was an official rec. "for better indexing"

Here I strongly disagree. YAML is an extremely human-friendly format for structured data of any depth, and using whitespace is instrumental here.
One might dislike it or find inappropriate for particular task, but whitespace is YAML, not an accidental nuance of design.

The funny thing is:
1. almost the only YAML's weirdness (basically, a design mistake) for casual usage is lenient parsing of booleans
2. which was fixed in YAML 1.2 (2009)
3... which AFAIK libyaml (and, therefore, everybody who depends on it, incl. Ruby) still fails to support 😁

* pragmatically: typechecker that sees `x + y` with both only known to be `Object`, can check nothing; but if we know that `x` is `Object?` we can say that "it CAN be `nil`, and this case isn't covered"

(but I don't have experience with Ruby's typecheckers, so this one is kinda theoretical)

Just from the top of the head, I think Object? is more useful both semantically and pragmatically:
* semantically: while nil is-a Object, I think a human reader would appreciate the distinction of "here could be anything" vs "...including nothing" reminder

=>