xz / open-source libs
The majority of libs you know at the very least _started out_ as someone just noodling around on their private project and then over time turned into the go-to solution for XYZ.
But for many libs, that's just never been the goal, and pretending that not having that level of ambition is tantamount to failure is also not serving anybody.
xz / open-source libs
And "any open-source lib anywhere in the wild must be up to professional quality standards and respond to all bug reports in a timely fashion" is also a bullshit standard to apply to anything. It just doesn't work that way.
Sarei felice se si potesse, ma concretamente non si può.
D'altro canto la programmazione non deve necessariamente essere difficile: siamo ai geroglifici (che non a caso, richiedevano decenni per essere dominati e proprio per questo diventavano uno strumento di potere) dobbiamo cercare un alfabeto in cui riscrivere tutto.
L'alternativa è uno stato di minorità inconsapevole per la stragrande maggioranza delle persone, uno stato di libertà simulata (oltre che vigilata) in cui la maggioranza delle persone crede di agire nel proprio interesse individuale mentre viene manipolata costantemente tramite migliaia di automatismi con cui interagisce quotidianamente.
Hacker o robot, cittadini o schiavi.
in realtà, imparare a programmare fluentemente è condizione necessaria (ma non sufficiente) per una piena cittadinanza cibernetica, per partecipare attivamente al governo di una società costituita per il 99.99% da agenti cibernetici automatici (software) controllati da coloro che sanno programmare.
piaccia o no, non saper programmare e debuggare il software significa subire passivamente la volontà di chi sa farlo, riducendosi a ingranaggi alienati.
I think @rms did a huge error basing what was a hacker¹ movement on the value of freedom alone.
#Freedom (like #Communion) is a totalizant value, a value that can blind people from other important values, so much that it's the foundational value of #Capitalism (much like what #Communion was for #Comunism).
As we can all see that #FreeSoftware lost its political goals, being used much more to reduce human freedom than to increase it (#Google and #Facebook would not exists without exploiting huge amount of developers' work donated as Free Software, much like #GitHub #Copilot / #CopyALot), we should really move to something different.
Years ago I wrote the #HackingLicense ² to this aim, a (network) #copyleft license (and a shrink-wrap contract) that has been used successfully in a couple of projects.
It doesn't forbid commercial use of the covered works and even share the copyright with the users that comply with the license itself, BUT contractually impose a complete reciprocity, as any work that benefit in any way from the covered work must be distributed in the same way.
IOW, if you use my work under the Hacking License, I can use and distribute your work under the same terms. Even if it's a LLM, or a software including its output.
I'm not sure the Hacking License is the best tool to get back freedom, communion and #Curiosity, but at least it's a step in the right direction.
¹ http://www.tesio.it/2020/09/03/not_all_hackers_are_americans.html
² http://www.tesio.it/documents/HACK.txt
The "modern" ones (angular 2 descendants).
They don't use #Angular, the believe in Angular. It's a religion and any critical analysis of the actual issues of the framework are recived like blasphemy.
🤷
PostgreSQL maintainer Simon Riggs has died in a small airplane crash, on Tuesday.
For those who didn't know Simon, he's responsible for PostgreSQL Binary Replication and many big data features. He and I worked together at Greenplum 2006-2008. Postgres would not be the world-leading DB it is today if it weren't for him.
To be honest, I can't see any compliance issue.
You can use #MongoDB under the #SSPL, but in practice you cannot have an edge over your competitors by doing so, as they will benefit of any innovation you create to make the service more useful, easy to manage or integrate and so on.
Probably this means that you cannot drive profit from such a business, but it's not technically impossible to use it this way, just anti-economic for a cloud company.
But "anti-economic for a cloud company" is quite different from "impossible".
Indeed the SSPL say explicitly "all such that a user could run an instance of the service using the Service Source Code you make available"
You wouldn't need to release unmodified GPL code under SSPL just because you use it to provide a SSPL software as a service as long you release under such license all the code you write.
A license cannot request you to violate the copyright of third parties, so such interpretation would be bongus in court.
Ok, so let's first explain what MTU is. I guess half of you already know, in which case you can skip 2 posts ahead.
As you may expect, there's a limit of how big an IP packet can be. This limit is called Maximum Transfer Unit, and it depends on the underlying link layer, eg. for Ethernet it's usually 1500.
If your Ethernet supports Jumbo Frames, MTU can be over 9000.
If you add VPNs / tunneling layers, it can go lower, eg. Ethernet with MTU 1500 goes down to ~1420* when you add IPSec.
1/
Any example?
Don't need to explain (I know the topic quite in depth) but I'd really like to see an example of a derivative work of a LGPL covered software that was not under LGPL.
I'll be happy to analyze it with my reference lawyer. Obviously, the more example, the better...
AFAIK any modification to LGPLv3 code must be distributed under LGPLv3.
The difference with GPL is that you can include or link an unmodified LGPL work into a proprietary software and distribute the whole with a different license.
But if you modify the LGPL work itself and redistribute it (in binary or source form) you must use the LGPL license as it would obviously be a derivative work.
Even wikipedia confirms this https://en.m.wikipedia.org/wiki/GNU_Lesser_General_Public_License#Differences_from_the_GPL
Thus you should clarify the related paragraphs: using LGPL for the distribution of derivative works is not a suggestion but a requirement of the license.
Also, when I talked with a lawyer about a derivative work of a BSD software he explained me that I could distribute my modified version under AGPLv3 because I had introduced and modified several parts and my modification was under GPLv3 so the work as a whole was GPLv3, BUT I could not alter the copyright statements in the files I was copying verbatim from the original BSD project.
So my suggestion is to talk with a lawyer specialized in sofyware copyright about Redict before distributing Redis code under a different license.
@mcp @informapirata @informatica
L'AI Act, impostatato com'è sul rischio di danno e sulle valutazioni di impatto, rende leciti quasi tutti i sistemi maggiormente lesivi dei diritti individuali.
Si arricchiranno, oltre alle big tech, le imprese che si occuperanno di valutazione del rischio.
L'autorità italiana che dovrebbe fare, baloccarsi con le check lists?
L'unica cosa utile sarebbe una presa di posiziione italiana, che sancisca l'illegalità di diritto
di ciò che è già illegale sulla base del diritto vigente, al netto dell'AI Act: ad esempio, che la polizia possa usare un sistema intrusivo e non funzionante di "riconoscimento" delle emozioni.
Io lo so, ma quanti davvero ne comprendono appieno le conseguenze?
Quando #Mozilla imposta #Google come motore di ricerca predefinito, sta collaborando alla mutilazione della libertà di milioni di persone.
Milioni di persone che continuano a votare peraltro. Sei proprio sicuro che tutti ne comprendano le conseguenze?
#Google non usa i tuoi dati.
Google usa te.
http://video.linuxtrent.it/w/sWFcXj4DpWPTkvdi7jA61u?start=40m1s
"solo nelle istanza più chiuse e polarizzate" 🤣 fra cui:
https://mastodon.art/
https://lemmy.ml/
https://mathstodon.xyz/
nonché l'italianissimo
https://livellosegreto.it/
chissà se @kenobit sapeva di gestire un'istanza fra le più chiuse e polarizzate...
🤷♂️
(elenco completo su https://fedipact.veganism.social/ )