mirabilos

There is still quite some amount of hubris in this.

If A writes software under L0 and gives it to B and is “nice enough” to allow B to use it privately for free, there’s some entitlement to the software.,

You’re overlooking that, in a contemporary environment, you’re standing on the shoulders of the giants (and all the small ones) who came before you. It’s absolutely presumptuous to write code in our time and not publish it under an OSS licence.

It’s misleading because it pretends that you need zero licences for it.

Nor is it Ⓕ Copyfree compatible, and none of the BSDs would ever touch it either.

So that leaves you with adaption by unwashed unorganised masses who wouldn’t care about licence terms at all.

Just find something that brings bread on the table. Doesn’t even have to be software-related, could be, idfk, gardening.

Eh, you can use a fixed-width font in GUI apps, too. In Kontact, for example, you just press “x”.

FixedMisc is still the best font

meh, give me ed over vi and emacs any day

“modern” seems to be a curse word these days, all the time I find it being used it’s used to describe something despicable like the systemd ecosystem.

Slack? Ugh.

When my employer turned off the company-internal Jabber server in favour of, out of all things, Hipchat, I moved my team mates to IRC. (They also seem to all know at least some vi, even the trainee.)

I am the author. And I am not an academic interested in bringing out a lengthy article with explaining the interpretations and all.

I am, in this instance, pragmatic: explaining what’s bad, why it’s bad, what we need to do right now, and that’s it, and now I’m trying to work on a solution with the GitHub people.

If this is not enough, do your own research. In my referrers, there have popped up some Russian sites that (according to Google Translate) did some of their own research (and came to similar conclusions). Ex-Debian’s joeyh did, too.

Sorry about that, I was more concerned with getting the explanation into more than 140 chars and out to both people and GitHub and getting in touch with GitHub than with writing a lengthy article.

And all this besides $dayjob which suffered on the day, so I’ll probably need to work the weekend to catch up.

The licence per se is not disallowed.

If you create a work from scratch and decide to put it under GPL and upload it to GitHub (thus granting extra rights), that’s just fine.

It’s only you cannot currently upload SOMEONE ELSE’s GPL’d work (including your own derivate thereof) to GitHub.

True. But CC0 is deprecated by CC themselves and CC requested the OSI to not approve it. It is unclear whether there will be a successor.

But any of the BSD/MIT-ish licences should be close enough to a “gift” for this to work (well they do protect the author/licensor a bit more, but…).

“how these rules came to be and what they try to achieve”

That’s not my point here.

The intent behind the rules and what they’re trying to achieve is GOOD and A STEP UP from the previous ToS.

HOWEVER, they have language that IS problematic for almost ALL copyleft and/or attribution-requiring works that include contributions from people who did not upload it directly to GitHub themselves. THAT’s what I’m discussing.

As things are right now: yes, especially for GPL works, “probably not” for BSD or MIT works.

I _am_ working with them to get it fixed, but they enacted the new terms prematurely, so _currently_ the mess is there.

This just shows that two lawyers did not even read my article and just comment on it demeaningly.

Please do note that D.5 also covers “reproduce”, which _is_ “distribution of code”, _and_ that I address this point in my article.

So, in short: If you need to give lots of money away, get a lawyer, but even then you’re not getting what you’re paying for. They also only cook with water, they also are just erring human meatbags.

Someone intelligently (hah) decided to link to the (1 MiB) page with the entire wlog posts of the last decade (plus CSS, webfonts, …) instead of to the permalink of the one article (15K), and then over https.

The webserver is a first-generation Celeron 2.4 GHz (Dell PowerEdge 750, AIUI) with 1 GiB of RAM, running MirBSD (not the fastest OS out there) with Apache. So, no surprise.

Yes, one of _those_ Celeron CPUs with so few L2 cache it can be discounted as having none.

For that, it does remarkably well (though 「ls -l /var/www/logs/」 surely shows the traffic ).