Shamar @Shamar@qoto.org

@aral

There are several and I should definitely find the time to write something about them (and maybe debate with #RMS about them).

One evident and recent one has been shown by the #GitHub #Copilot affaire: code is data too, but the #GPL does not require sharing the output of such kind of compilation.

But there are many other ways that the knowledge contained in or derived by #AGPL software can be privatized.

Indeed AGPL does not prevent embrace, extend, extinguish tactics.

It may well keep in the commons the derivative works of a specific software but does not affect any software built on top of it, in particular if its services are provided through standard protocols.

Also the Oracle vs Google has shown that any innovative API gifted to commons by #FreeSoftware hackers would be taken by #BigTech corporations and turned into exploitation tool: if it happened to Oracle's Java API, it will happen to any Free Software that affect the interests of people running such corporations.

Not to mention complexity! Or patents!

The #HackingLicense address all of this.
In includes a copyright and patent assignment TO THE USER, both conditioned to the preservation in the commons of both derivative works AND works dependent on it.

It's not a #copyleft designed to protect priviledge but to build a free cultural corpus of commons that belong to the whole humanity and cannot be turned into exploitation of free labor.

@ekaitz_zarraga @Pixificial @craigmaloney@octodon.social

@ekaitz_zarraga

I spent some time tweaking it with a lawyer that is expert in IP and Free Software licensing.

Obviously he noticed how the wording makes it formally violate the freedom zero: you must NOT use the Hack to restrict the rights granted by the license to third parties.

But that's part of the Hacking License being an hack itself: it's designed to be incompatible with any definition of freedom that reduces commons to garbage anybody can exploit.

So while a judge would enforce it as a wrap contract and a license, it is neither compatible with #OSI (yeah!) nor with #FSF (sadly, but inevitably).

Unfortunately the native culture of #Stallman tainted #FreeSoftware in subtle ways that made it easy for corporations to exploit the work of #hackers.

They always find a way, as #GitHubCopilot has shown.

The #HackingLicense is designed to keep not only hackers work in the commons, but also any derivative work and any work dependent on it.

To make ALL knowledge free for people who share what they learn.

@ekaitz_zarraga

Unfortunately the #AGPL has new loopholes now.

My network #copyleft of choice, right now is the #HackingLicense: http://www.tesio.it/documents/HACK.txt

@aral @Pixificial @craigmaloney@octodon.social

The power that sed unlock when you understand how to use the hold space is unbelievable.

Beyond an actual use case that I had to handle with it because of lack of alternatives on the target system (not even vi or awk were available, and I was not allowed to transfer the data outside), what opened my eyes have been the #GNU sed manual¹: other texts where technically complete but somehow didn't clicked.

Now I wonder why nobody have built a graphical sed debugger that shows you the pattern space, the hold space and the program so that you can step into it and see what happens.

I now have a good mental model of its inner working, but to teach it to kids (as we should) we need something like that.

Also I wonder if we should build a less succint sed language: the one letter commands are effectively an pretty good machine code for a sed machine AND they let you write powerful one-liners that fit well in a script but they are pretty hard for kids to learn.
____
¹ https://www.gnu.org/software/sed/manual/sed.html

@syntacticsugarglider

Also see some #9P2000 (argably little) issues that becomes evident with time: http://aiju.de/plan_9/9p2020

@0gust1

@prasoon

Sounds interesting...

May I ask what you mean by "tit-for-tat" and "forgiving-tit-for-tat"?
(Maybe there is a language barrier at work here, I don't know these English idioms)

Also which biological structure inspires such approach?

@natecull

I just spent 20 minutes contemplating a powerful (and totally unsafe) text template engine I wrote for automatic code generation in #Jehanne.

In 5 lines of #sed¹

I'm too overwhelmed by the power of sed, to ponder consequences.

____
¹ piped to #Plan9 rc

@falgn0n

What do you mean exactly?

@michal

@Davide_Sandini

Good points. 🤣

@loke @dredmorbius @rysiek@mastodon.technology

@loke

One might argue that having a job there is a good way to kill the monster from the inside, through leaks, bugs and so on...

But to me the risk I could somehow help them is too disgusting.

@dredmorbius @rysiek@mastodon.technology

@oleksiy

Oh sorry.. misread "with" for "without".