ChanceNCounter

It occurs to me that bak depends on an XDG-compliant, Unix-like system, which should always have `diff`. It's probably reasonable to just change the default config value to `diff`.

Clearer: bak doesn't *demand* XDG compliance, but it falls back on the XDG spec when the XDG environment variables are absent. Point is, not-Windowsness means `diff` should "always" exist.

(rolling branch until end of current run. 6 months at a time of abandonment is too long, but if it's gonna keep happening...)

Oh, no I'm not! Sorry, I didn't mean to leave that impression. I was trying to diagnose this problem before installing the skill to a potato.

I like the notion. I couldn’t help noticing that the image above depicts an overcapture that might not be avoidable.

Came to my attention because I’m the OVOS license compat nerd, and this analysis includes our Piper plugin in addition to Piper itself (heritable licensing is a big headache) The...

The question with respect to Piper, and I’m still commenting pre-analysis, would be if it’s a combined work, not whether it’s derivative. The static vs. dynamic linking distinction hasn’t been...

The basic concern is the unlikely, but ever-present possibility these factors could combine: 1. Anyone who contributed GPLed code upstream *could* have a gripe 2. The FSF will provide pro...

There are two ways to inherit the GPL: by creating a derivative work, such as by forking a GPL project, or by creating a combined work, such as by incorporating...

Well… there is a perspective from which the introspection was the hardest part with LF, and that was a Python problem. Once we figured out a way for developers to...