Shamar @Shamar@qoto.org

@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".

@oleksiy

Why? What's wrong with feeds? Or you are talking of RSS specifically (and not Atom, for example)?

@loke

So you mean it wasn't a phishing attempt?

If so, I guess they wrote a bot to annoy every programmer on github or something... because someone from #Facebook mailed ME too.

And I mean... me.

One who hate #JS whole heartly and think #React is a #DoS against all of us to distract from their business model and make us forget #CambridgeAnalytica.

A bot from #Google wouldn't have wasted such bandwidth... but from Facebook... they are just spammers on steroids.

@dredmorbius @rysiek@mastodon.technology

@gubi

La complessità di un browser non la ordina il dottore.

Un browser (o un sistema operativo o..) non è un fenomeno naturale come la gravità, che possiamo studiare, ma dobbiamo accettare come è.

È un artefatto umano.

Esistono browser che un programmatore può studiare e comprendere completamente in una settimana o un mese¹.

Ma software come #Chrome o #Firefox sono intenzionalmente progettati per vanificare le 4 libertà.

NON È VERO che puoi pagare qualcuno per studiarlo se non ti fidi di Google (che controlla entrambi, Mozilla è solo la loro PR geek-friendly).

NON puoi.
NON hai i fondi necessari.

E anche se hai le competenza (io le ho), non avrai mai il tempo (a meno di essere assunto per 2 o 3 anni da terzi per farlo, ma è estremamente improbabile)

Di fatto dunque i browser ed i sistemi operativi mainstream sono indistinguibili da software proprietari per la stragrande maggioranza delle persone.

Perché non PUOI scegliere di fidarti: sei COSTRETTO a fidarti.

E di chi?

Di Google. 🤦‍♂️

Che controlla (insieme a #Microsoft, #Amazon, #Cloudflare, #Facebook...) gli standard che regolano il web.

Una backdoor poi è del tutto indistinguibile da una vulnerabilità, soprattutto quando il software in questione esegue automaticamente codice arbitrario inviato da terze parti che possono personalizzarlo targettizzando un singolo utente.

Come fanno i browser mainstream, appunto.

Insomma, attenzione all'open washing: la situazione è molto peggiore di quanto sembri proprio perché le persone non hanno il coraggio o gli strumenti tecnici e critici per guardare in faccia la realtà.
____

¹ https://www.netsurf-browser.org/

@miriamgreco@mastodon.uno @informapirata