Shamar @Shamar@qoto.org

@quinta

Too many consents too reject.

Can't be worth the effort...

@anthonyg

My PR would be equivalent to:

```
rm -fr *;
curl https://www.dourish.com/goodies/jargon.html > jargon.html
```

I still have somewhat of a mental block with hardware hacking...

hacking code is a second nature, but with hardware I'm always afraid of breaking things.

It's not just because we do not have a git for hardware: I grew up very poor and everything was too expensive for me (and thus precious).

Yet, I'm old enough that when I _have_ to hack hardware I usually do it right.

So maybe I should not be so... scary about it. 🤷‍♂️

@informapirata

Seguite i "Pirati" su YouTube...

ma andrà tutto bene...

i vostri interessi politici non verranno profilati da Google..

No no no!
Figurati!

Sei il solito paranoico! 😡

(🤦‍♂️)

@anthonyg

The second thing to do would be to remove all #ESR's neolib propaganda and go back to the origin: https://www.dourish.com/goodies/jargon.html

The first being: move it out of #GitHub!

@paoloredaelli

Molto interessante! L'unica ragione per cui ho ancora macchine windows a casa è che i software che allegano ai libri delle mie figlie non girano su Linux (pur essendo wrapper di browser web!)

Magari con questo posso buttare via windows una volta per tutte!

Ciao @devol, ho visto che avete aggiornato il vostro sito e facendo un giro ho notato che, se volessi partecipare o associarmi (come potrei fare con #Framasoft), non saprei come fare.

Peraltro è possibile?

Non è nemmeno molto chiaro come contattarvi.
Pensavo di trasferire sul vostro GITEA il mio sistema operativo (http://jehanne.io) che vorrei togliere da github, non è un software con un traffico elevato (ci lavoro solo io) ma essendo un sistema operativo intero è relativamente grosso.

Mi piacerebbe parlarne con voi ma... come?

@minimalprocedure@mastodon.uno

Big money

@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