csh83669

I have something that looks like that. Mine is a bone mounted hearing aid. Usually there’s a little device plugged into it.

At which point if I'm expected to give a dollar to each of them, then I'm basically screwed. I've seen some licenses trying to claim "1% of your revenue if you use my package"... But if I use 1000 of them I now owe 10x my revenue to a bunch of "leftpad" libraries?

Or am I somehow supposed to give like... 10000 3 penny donations? How would that even work? The costs to "donate" a dollar to someone with modern banking (once the CC and whatever donation site takes their cut) almost makes it not worth it.

Especially once indirect dependencies get pulled in (which is a large part of the FOSS ecosystem... tons of people use ffmpeg without ever realizing they are) how does that work? If I use a library, and that library suddenly adds 20 more dependencies, do I need to shell out $20? Or am I as a maintainer supposed to divvy up any donations I get to every library I used (I bet you used a compiler to build whatever your tool is).

It's rough, and I don't see it really working for anything but a few special snowflake projects. It's just not workable at the scale FOSS has turned into. A blessing a curse I suppose.

Is this true? All the news I’ve seen is that Wade resigned but Willis will stay on. If they both quit, that’s huge news I would expect someone to be reporting.

I think this article makes a pretty big leap in the middle. There's really no reason that the operating system needs to be involved in the "Private" solution. It could just as easily be a website or a browser plugin. All you need is your government of choice to have some way to provide a token with whatever important bits necessary in it ("Yes this person is over 18 and a resident of WA"). You could even have third party sites/libraries that could read that token and verify what it contains.

The last third of the article is all based on that giant leap.

The example for me immediately showed my overlap bug with “eightwo”. There aren’t too many other ways to make this ten words overlap. 🙂

I would say absolutely. The 2004 series one of my favorite series, even if I find the end tapers of in quality in my opinion. Otherwise it’s great. Give it a watch.

It always seemed like something that could be handled by a unit test. Assuming your registration code is able to be called independently, validating it once with a test at build time seems much more useful than wasting time at every startup for something that will be more or less static.