@paoloredaelli

Non discutevo la volontà o la liceità, solo la possibiltà: usare fossil in self-hosting evita che i tuoi sorgenti vengano scaricati a strascico da GitHub.

Quanto a RMS, non uso più le GPL da un po': ho scritto la #HackingLicense proprio per superarne i limiti (anche culturali ed ideologici).

http://www.tesio.it/documents/HACK.txt

@rms @prealpinux @informatica

@amin

Very nice work!

I see the engine is a single #python script that connects to a #PostgreSQL db.

Both are cool technologies but require quite a bit of technical expertise to be self-hosted.

Over the years I've seen that projects based on less cool technologies (php, cgi-bin, sqlite...) enable both #selfhosting and #SAFEhosting, that is using cheap, local, non #BigTech hosting providers.

It's something I realized reading free software based on the #permacomputing values.

Not really a suggestion or a feature request (maybe a note to myself, for a fork when I'll have more free time), but something I think you might consider.

Another one: it would be cool to enable a sort of federation among the instances, either by simply proxying the trusted instances (and excluding the duplicated urls) on user's search, or by enabling trusted #fediverse users to add websites to be crawled.

"Trust" here is a key concept: federation should be optional and disabled by default.

Anyway: good luck and good work!

And thanks for using a network #copyleft!
(I prefer the #HackingLicense over #AGPLv3 in the age of #GitHubCopilot/CopyALot, but at least AGPL protects the work you donated to the world from direct privatization...)

@selea

@matthewhowell

Not sure if it's what you are looking for, but the #HackingLicense is a copyleft designed to also apply to any "AI model" (and any of its output) that was "trained" over a covered work: https://www.tesio.it/documents/HACK.txt

@david_megginson

"Worse" for who?

I'm very happy too if someone find a way to get rich through the code I donated to humanity.

But if to get rich he write closed (or patent-protected or..) source software that prevent me or anybody else to study and modify such code, I'm not happy anymore.

That's why I use the #HackingLicense, despite the stigma on #copyleft license proliferation: http://www.tesio.it/documents/HACK.txt

I don't give a shit if somebody cry about it not being compatible with GPL, it being hurting the FOSS and so on: you can make money for my work, but any software, AI model or whatever you build on top of it, must be shared in the same way.

@paul_ipv6 @tinker

@irenes

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

@krans @glyph @eb

@fucking_good_dpo

tranquillo Christian: solo quello che scrivo io sulla chat è sotto #HackingLicense 😉

@nemobis 🤣

I don't know... I'm not sure.

As you know, I'd be very happy to find a way to keep ALL public domain derivative work... within the commons heritage of humanity.

I even wrote the #HackingLicense to achieve this sort of legal effect (and I know you do not like it).

@mmu_man

Except one that hides to the users the source they are copying, helping them to violate any open-source license that requires proper attribution and, what's worse, any #copyleft imposing reciprocity https://video.twimg.com/tweet_video/E5R5lsfXoAQDRkE.mp4

That's why I wrote the #HackingLicense http://www.tesio.it/documents/HACK.txt so that when we will be able to prove that #Copilot distributed any work under such license, we will have to assume that #Microsoft accepted the license, that the "models" of #CopyALot are used under its terms and thus all the software that adopted its "suggestions" can be used under its terms too.

@BrodieOnLinux

@t0k

The Purpose of the #HackingLicense is to create a cultural and technological corpus that will grow and evolve completely and exclusively as a common heritage of humanity.

It's designed to cover and extend to any intellectual artifact and to go beyond the anachronistic distinction between contents, data and code.

Code is data and data is code.

However even ICs are intellectual artifacts that people should be able to donate to humanity without fear of any corporation exploiting them without giving back anything to the community.

That's why I included mask-rights after studying CERN OHL (and all the others listed here: https://wiki.p2pfoundation.net/Open_Hardware_Licenses )

@neil

For sure, as long as they are really constructive.

I invited all of the lawyers that joined that conversation to read the license, explain any issue they see (with reference to where it occurs in the license's text and the law that underline the issue) and suggest improvements that make the #HackingLicense more viral and more effective in reaching its purpose.

But obviously the invitation is open to everybody!

@ekaitz_zarraga @aral @Pixificial @craigmaloney @Curia @noybeu

@aral @ekaitz_zarraga @Pixificial @craigmaloney

Little follow up about the #HackingLicense.

It has been adoped by #MonitoraPA, an automatic and distributed observatory written in #Python with the explicit goal to be easy to hack and run for any teenager who just learnt the language from an online tutorial.

On our first run we detected 7833 public administrations' websites using #GoogleAnalytics.

We formally requested all of their DPO and Data Controller to remove it as its usage is in violation of #GDPR as established by the #Schrems2 sentence of @Curia (thanks to @noybeu).

Two weeks later, almost 4000 italian public administrations (several hundreds of schools!) that were sending to #Google detailed data about every page visit, removed Google Analytics.

More details about the project are available (in Italian) at https://monitora-pa.it

Next week we will officially run our observatory again, we will notify again PA that still have Google Analytics in violation of #GDPR, but we will also escalate to the various Authorities that Italian and European Law provide.

And obviously, Google Analytics is just a starting point!

We are refactoring our code to make it trivial to add more conformity checks even beyond the web and to run it over different data sources so that people can easily run our observatory over any set of websites, from political parties to football clubs.

And in the July's run, we hope to detect and request removal for at least #GoogleFont connections and #Facebook Tracking Pixels too.

Obviously we got several powerful enemies. #Google for first, but also several Italian lawyers and administrators that did not protected citizens personal data.

And among them, quite expected, compromised organizations like #OSI that are spreading #FUD about our license of choice without even reading it or trying to help us to improve it.

https://github.com/hermescenter/monitorapa/issues/39#issuecomment-1140274175

@t0k

Basically #FUD.

As you said, #Google does whatever it can to build ecosystems that depends on it, technically and culturally.

They did so in 2010 with #GoogleChrome through #Mozilla. It did so with #Android. And #QUIC. And #HTTP3.

#AGPLv3 has several limits (that I tried to address with the #HackingLicense) but the strongest the #copyleft the better.

Sticking with #AGPL and resisting to Google's pressure won't save your ecosystem alone.

BUT it might make their capture weaker and their abuse of their dominant position more evident.

As for AGPLv3 be harder to use, that's plain bullshit. As long as they use your software unmodified, they do not even need to host a copy of the code. They just need to provide users a link to your repository.

It's pretty easy.
But they do not want to.

In the long run, an AGPL alternative out of Google's control might enable the creation of an alternative ecosystem, and they want to minimize this risk as much as they can.

Without looking evil, obviously.

But if you look at Google from outside the USA, it's slowly becoming a huge geopolitical liability.

Europe is realizing that depending on #GAFAM means becoming an US colony.

And alternatives like your might get much more support from here.

So my suggestion is to ignore the FUD and resist Google.

@t0k

Something else: adopt the #HackingLicense http://www.tesio.it/documents/HACK.txt

As an alternative, stay with #AGPLv3.

The choice is:

- let #Google exploit your work as #FreeLabour, or
- force Google to pay to compete with you but starting from scratch

Never let the bully get what they want.

@Thelie

No legal precedence, sorry.

I wrote the #HackingLicense (with the help of a lawyer) to address the issues I see in mainstream #copyleft such as #GPLv3 and #AGPLv3.

These were my first choice before realizing their limits in protecting all evolutions of a covered work.

Few projects use it, mostly because I'm involved. For example https://github.com/hermescenter/monitorapa

@rysiek