Notices by Giacomo Tesio (giacomo@snac.tesio.it)

Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Wednesday, 25-Feb-2026 19:11:47 JST Giacomo Tesio
in reply to
- Tim Bray
@timbray@cosocial.ca

It's so funny, if you think about it.

After all, #Dijkstra wrote
The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence.
So it's basically a race:
- COBOL to cripple the LLMs
- LLMs to cripple the global finance
🤣

#LLM #vibecoding #COBOL #AIbubble
In conversation about 4 months ago from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Sunday, 08-Feb-2026 01:24:55 JST Giacomo Tesio

The documents provide smoking-gun evidence that Meta, Google, Snap, and TikTok all purposefully designed their social media products to addict children and teens with no regard for known harms to their wellbeing, and how that mass youth addiction was core to the companies’ business models. The documents contain internal discussions among company employees, presentations from internal meetings, expert testimony, and evidence of Big Tech coordination with tech-funded groups, including the National Parent Teachers Association (PTA) and Family Online Safety Institute (FOSI), in attempts to control the narrative in response to concerned parents.

“These unsealed documents prove Big Tech has been gaslighting and lying to the public for years
https://techoversight.org/2026/01/25/top-report-mdl-jan-25/

#BigTech #GAFAM #Google #Meta #TikTok #Snap #teens #mentalhealth #privacy #surveillance #addiction #drugs
In conversation about 5 months ago from snac.tesio.it permalink
Attachments
1. Domain not in remote thumbnail source whitelist: techoversight.org
  
  TECH OVERSIGHT REPORT: UNSEALED COURT DOCUMENTS SHOW TEEN ADDICTION WAS BIG TECH’S “TOP PRIORITY” - Tech Oversight Project
  
  from techoversighteditor
  
  New documents show the tactics Meta, Google, Snap, and TikTok execs used to disrupt learning, prey on minors, and co-opt the PTA to control the narrative with parents WASHINGTON, DC – Today, The Tech Oversight Project published a new report spotlighting newly unsealed documents in the 2026 social media addiction trials. The documents provide smoking-gun evidence […]
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Wednesday, 12-Nov-2025 22:29:21 JST Giacomo Tesio
in reply to
@happyborg@fosstodon.org

More a lossy compression than a zip archive. You know, the "hallucinations" are just decompression artifacts.

But yes, doesn't change a dime as for the #llm being a derivative work of the human readable source (as Debian ML Policy describe it).

@amszmidt@mastodon.social
@doctormo@floss.social

In conversation about 8 months ago from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Wednesday, 12-Nov-2025 18:39:32 JST Giacomo Tesio
in reply to
- Alfred M. Szmidt
- Martin Owens :inkscape:
@amszmidt@mastodon.social

The way #LLM are voiding classic #copyleft has been experimentally demonstrated years ago, when #GitHub #Copilot was caught distributing well known #AGPLv3 code with a permissive license and wrong author attribution.

Also, technically that incident demonstrated how Copilot's model itself is a derivative work of copylefted works: if a lossy compression of copyrighted material is still subject to authors' #copyright, encoding such compression as arrays of floats that can be executed by virtual processors with a dedicated architecture (so called "inference" engines) does't change its nature of derivative work. Similarly violating copyrights of millions of authors at once doesn't free you of such rights.
That's basically why #OpenAI and friends are so scared by current lack of sustainable business models for their #LLM: they need money to keep Judges away.
But anyway I still have to find a single person that debate with technical competence and in good faith the derivative nature of LLMs from the text corpora compressed in their models.

As for the Hacking License not being a Free Software license, it's debatable after a careful read since the only thing you cannot do with the software is to prevent others from enjoining the same freedom it grants you.

Yet I've never claimed it is Free Software because, sadly, I'm forced to move beyond Free Software by its own limit.

OTOH I'm proud that it's not an #OpenSource license as I'll never submit it to #OSI corrupted #gatekeepers.¹

As for #FLOSS, it's a term designed to confuse free software values with corporate propaganda while marginalizing hackers: its a leaking abstraction designed to fool developers and exploit their naive groupthinking. Having been fooled myself. Never again. 😉

____

¹ The way OSI tried to #openwash the #OSAID, with an over complicated process that doubled #Meta's lobbyists' votes to exclude training data from the requirements confirmed my opinion about them.

@doctormo@floss.social

In conversation about 8 months ago from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Wednesday, 12-Nov-2025 16:58:21 JST Giacomo Tesio
in reply to
- Martin Owens :inkscape:
Still, #LLM are voiding the #GPL (and #AGPL) reciprocity.

That's why years ago I wrote the #HackingLicense https://encrypted.tesio.it/documents/HACK.txt

It was designed with automated corporate #exploitation of #FreeSoftware in mind: it's goal is to balance #freedom and #communion, and it share with those that accept it much more than permissions, while being a stromger #copyleft and an explicit shrink-wrap contract.

Unfortunately, it's not compatible with GPL, because GPL is much weaker.

The fundamental issue of Free Software, the one that let people create the #OpenSource narrative and permessive licenses to exploit programmer ideals and #freelabor, was that #RMS, as an American grown up during #ColdWar, was too fond of the freedom-vs-communism propaganda to understand how lack of rules means the rule of the rich.

The problem is not commercial use of free software but commercial exploitation of free labour, as @doctormo@floss.social correctly stated.

The Hacking License does not prohibit commercial use, but requires recipient to share their own #copyright with the users of any derivative or dependant work they create as a contractual binding.

It's modelled after the research of #ElinorOstrom about Commons governance and the #Hacker ethics based on the value of #curiosity.
In conversation about 8 months ago from snac.tesio.it permalink
Attachments
1. Untitled attachment
  
  Invalid filename.
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Thursday, 03-Apr-2025 21:17:18 JST Giacomo Tesio
in reply to
- Ekaitz Zarraga 👹
@ekaitz_zarraga@mastodon.social

Indeed if you were leading #Guix, I'd likely be a user and contributor (I think you know I have the technical skills required).

And I also know other people working there, people I respect despite not being always aligned with their opinion (for example I had a long debate with a friend that work on Guix a few months ago about the right to be mentioned with the preferred name by a transitioned trans developer whose code was archived with their dead-name and #SoftwareHeritage was refusing to update. I think hackers have the right to be named as they wish in their works and no script, tool or hash chain matter more than this right).

Yet there's a huge difference between a technical or even philosophical argument and a (politically motivated) personal attack in form of a shitstorm.

Courtès might even be the best #scheme hacker out there, with a solid architectural vision of how to make #linux more reliable.

But I chose free software for political goals that he actively damaged with that attack to RMS.

In conversation about a year ago from gnusocial.jp permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Thursday, 03-Apr-2025 17:10:37 JST Giacomo Tesio
in reply to
- Ekaitz Zarraga 👹
@ekaitz_zarraga@mastodon.social

The #Guix leaders are indeed the reason I don't even give it a try despite some great people like you working on it.

I will reconsider when I'll read a public apology for this personal attack to a neurodivergent #hacker such as #RMS.

It worth to remember how that "joint stab in the back" was published while RMS was under attack because he dared defend Minsky's memory from the same sort of mob justice that was then redirected (and amplified on #BigTech social media) against RMS himself.

Some of those "leaders" who signed that "joint statement" a couple years later signed an even worse attack built on top of lies.

These sort of personal attacks have clear political goals, "incidentally" aligned with BigTech interests.

Now @zimoun@sciences.re could try to sort me among #Stallman fanboys to reinforce his beliefs, but in fact I'm pretty critical of RMS work: ultimately I think he based free software on a cold-war biased ideology, without a proper balance between communion (aka sharing strongly protected commons) and freedom. This huge error left space to #opensource and to the current use of #FreeSoftware by all sort of large corporations to abuse and subdue people.
Another (related) issue has been the total lack of a cohesive architectural design for #GNU system: RMS was too (inconsciously) fond of free market ideology to lead the movement's technically, and this lack of cohordination was turned by #ESR to the "bazaar" (not so subtle) sublimation of free market, to ease corporate exploitation of the high skilled labour of #hackers.

But in fact, with all of his political errors, he's still the most coherent and commited free software activist out there.

So I will consider Guix again when they will publish a joint apology with the same visibility the back-stab had in 2019.

In conversation about a year ago from gnusocial.jp permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Saturday, 25-Jan-2025 19:15:41 JST Giacomo Tesio
in reply to
- Liam @ GamingOnLinux 🐧🎮
@gamingonlinux@mastodon.social

who control the platform own users' minds, what they can read, who can read them, what goes viral, who becomes influencer, who is harrassed and what opinion spread among each segment of population.

#Bluesky is just like #twitter: even without #musk, you can only serve the owners' interests, either with what you write or what you read.

With true #decentralization and chronological timelines people don't get reduced to servants.

To me this is much more important than "following" people. In fact, I don't find bootlickers much interesting, and to get a huge number of followers on centralized platforms you must serve their owners' interests one way or another.

In conversation Saturday, 25-Jan-2025 19:15:41 JST from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Saturday, 25-Jan-2025 02:00:21 JST Giacomo Tesio
in reply to
- Liam @ GamingOnLinux 🐧🎮
@gamingonlinux@mastodon.social

Don't trust Bluesky's fake decentralization.

In conversation Saturday, 25-Jan-2025 02:00:21 JST from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Tuesday, 07-Jan-2025 22:27:29 JST Giacomo Tesio
in reply to
- The Real Grunfink
- OCTADE
@grunfink@comam.es

Actually that would enable #snac usage in a specific educational use case: schools.

I think kids and teens might be able to learn how to use social-networks in a defederated #fediverse instance, being able to do their typical errors in a protected environment.

However I know no school so brave to experiment on this, because of all kind of issues they might have to face, from sexting to bulling.

Yet, I think that it might help kids grow more aware of the risks and implication (and maybe even more #privacy aware).

On the technical side: you could have a defederated Snac if you make it available over a VPN or local network only. Also, I suppose that messing crypto keys would isolate the instance's inbox. All hacks, though.

@octade@soc.octade.net

In conversation Tuesday, 07-Jan-2025 22:27:29 JST from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Sunday, 22-Dec-2024 08:42:24 JST Giacomo Tesio
in reply to
- Nemo_bis 🌈
@nemobis@mamot.fr
I mean that the license was instrumental to attract certain kind of people and keep other away.

It worked very well in this regard, with two exceptions: you and a developer who I respect but blatantly violated the license creating a derivative work under AGPLv3. However by his own admission, he didn't even tried to read it.

You were the most enigmatic of exceptions. I think we were (and are) in deep agreement from a political perspective, yet you seemed too fond of gatekeepers' rethorics around license proliferation.

I wonder if after OSI push for OSAID you opened your eyes about the real goals of such gatekeepers.

In any way, I still hope we will find new occasions to do politics together again. 😉

In conversation Sunday, 22-Dec-2024 08:42:24 JST from gnusocial.jp permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Sunday, 22-Dec-2024 01:24:13 JST Giacomo Tesio
in reply to
- Nemo_bis 🌈
- Antonin Delpeuch
@nemobis@mamot.fr

Incidentally, that was exactly the first choice I did when I created the #MonitoraPA observatory.

And I successfully used the #HackingLicense to that aim.

Yet, you hated it.

Maybe you didn't understood the kind of people the observatory was for?
(despite we were quite explicit about it)

@pintoch@mamot.fr

In conversation Sunday, 22-Dec-2024 01:24:13 JST from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Thursday, 19-Dec-2024 00:32:38 JST Giacomo Tesio
in reply to
- Marcos Dione
- Elena Rossini 🌈
@mdione@en.osm.town

Guys, you cannot imagine how much I can relate!

🥱

DNS are quite fundamental to the Internet, @_elena@mastodon.social so unfortunately a proper configuration is a sort of rite of passage, just like learning that it might take a couple of days for any update to propagate, so getting them right in the first place is just as wise as tricky.

Fortunately you are not going to face the burden #Google's #GMail imposed to all of us by self-hosting your email server, that is way worse than a website or a fediverse node!
Consider self-hosting your email server like the last level big-boss in your favourite adventure game.

Anyway, if in the future you'll want to try a simpler (and likely cheeper) alternative Fediverse software, I just published a short tutorial on snac here: https://encrypted.tesio.it/2024/12/18/how-to-run-your-own-social-network.html

It also discuss some of the vulnerabilities of the #fediverse that you might not be aware yet (but that can all be mitigated by #selfhosting your instances, so you are on the good track anyway 😉 )
In conversation Thursday, 19-Dec-2024 00:32:38 JST from snac.tesio.it permalink
Attachments
1. Domain not in remote thumbnail source whitelist: www.tesio.it
  
  How to run your own social network (with Snac)
  
  Short tutorial on how to join the Fediverse for cheap.
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Wednesday, 18-Dec-2024 20:27:19 JST Giacomo Tesio
- The Real Grunfink
Finally out a little #tutorial about running your own #fediverse instance on cheap shared hostings with @grunfink@comam.es's #snac.

https://www.tesio.it/2024/12/18/how-to-run-your-own-social-network.html

#permacomputing #retrocomputing #hacking #cgi
In conversation Wednesday, 18-Dec-2024 20:27:19 JST from snac.tesio.it permalink
Attachments
1. Domain not in remote thumbnail source whitelist: www.tesio.it
  
  How to run your own social network (with Snac)
  
  Short tutorial on how to join the Fediverse for cheap.
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Tuesday, 17-Dec-2024 02:57:33 JST Giacomo Tesio
- The Real Grunfink
@grunfink@comam.es I have a couple little feature requests that I think might slightly improve the usage of #Snac with cgi-fcgi on cheap shared hostings:

1) add to server.json an option to configure a folder where to write logs (or at least to save them in a dedicated folder in base dir) instead of standard output. Within such folder, I'd name them after the start date of the server (e.g. snac_2024-12-13.log). When the option is not defined, I'd preserve the current behavior (log to stdout).
2) when running as a server, acquire an advisory lock on the pid, and if you cannot acquire the lock, just exit because someone else is still handling requests for that basedir.

In conversation Tuesday, 17-Dec-2024 02:57:33 JST from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Tuesday, 17-Dec-2024 02:57:31 JST Giacomo Tesio
in reply to
- The Real Grunfink
As for 1) I just noticed the log/ folder that exactly does what I need, sorry for the noise @grunfink@comam.es

2) might still be useful on race conditions, when two different requests to cgi-fcgi find that snac is not running at the same time and both try to start it: we don't want to have two instances of snac racing so the second should happily exits.

In conversation Tuesday, 17-Dec-2024 02:57:31 JST from snac.tesio.it permalink
Embed this notice
Giacomo Tesio (giacomo@snac.tesio.it)'s status on Tuesday, 10-Dec-2024 09:52:07 JST Giacomo Tesio
in reply to
- The Real Grunfink
Hello from my brand new #Snac instance running as a #FastCGI on a cheap shared hosting.. without FastCGI support!

Turns out all you need is good old cgi-fcgi and a starter script. I'll send you a PR with a proper example as soon as possible.

I think this shows how Snac is the cheapest and easiest to install #fediverse server, lowering the bar to self-hosting #privacy friendly instances for schools, group of friends or families.

And using it from #fedilab is just as easy as any other instance.

Thanks for the great work @grunfink@comam.es!

In conversation Tuesday, 10-Dec-2024 09:52:07 JST from snac.tesio.it permalink

Public

Notices by Giacomo Tesio (giacomo@snac.tesio.it)

User actions

Following 0

Followers 0

Groups 0

Statistics

Feeds