The write up is disingenuous, or confusing at best. It highight early on "no evidence that end user vault data was accessed or at risk".

Then further down recommends to "Rotate any secrets that may have been exposed..." and "Review GitHub activity, CI workflows, and related credentials for unauthorized access or changes".

How could they even find evidence of end user data and vault being accessed? The CLI compromises affects end user systems, which they have no visibility into.

The worst is saying there's no evidence of risk, while making recommendations based on the assumption all data and secrets on affected systems may be compromised. That's a good assumption because there's definitely a risk.

Blowing so much money on fossil fuel subsidies left the EU vulnerable to an oil crisis, greatly limit the budget available to invest in renewables or to react to such crisis.

Are you aware of the Piefed API? It's provided specifically to allow building front-ends and bots while avoiding scrapping.

Naqib (The Boys)

on Jan. 21 the EU began banning fuel made from Russia crude

Better late than never.

Separating data structure from implementation has benefits.

In languages with classic OOP classes and objects, it's often necessary to write wrappers or adapters to allow new operations on existing objects. This adds overhead and require more code.

That population figures surprises me. But Wolfram Alpha says it's roughly correct, ie 44% https://www.wolframalpha.com/input?i=population+of+USA+vs+population+of+G7+countries

More banks and businesses should support Taler.

If Visa/Mastercard get replaced by another company's centralized payment system, what prevent a large foreign corp from buying it, like they regularily do? Then we're back to square one.

Bad ideas all the way down

XMPP, Conversations is a Nice Android client.