from Shad0w's Echos

#blog Why are you using tiny screens and phones to access porn? They are great on the go, but you gotta expand your horizons. Let's talk about screen gooning. As someone always looking to expand my porn addiction, I leverage technology. I won't bore you with all the technical details, but I'll keep it simple.

I have a 4-monitor setup at home for my porn PC. Right now, I have 9 porn videos playing at once, giving me a mild overstimulation as I type this. My center screen is where my main window and all the action takes place for interacting with the porn world.

But as I focus and get deeper into my gooning session, I do something really simple that's a game changer.

I double-click on the video with the good scene and let it go full screen. I savor that moment in full as porn blasts my ears in my headphones, and then the world goes simple again. Once that moment is over, I go back to my many multiple mini video screens and wait for the next amazing scene to come into focus again.

Also, adding on that I'm trying a new edging posture where I don't tense my crotch muscles when I masturbate. Still trying to break that habit, but boy, that's a game changer too!! Keep edging, everyone!

 
Read more... Discuss...

from Abstracciones

cómo es si nadie lo ha empezado

y en cierto momento del sueño te das cuenta / sabes que no hay descanso

reordenando sus famélicos fantasmas determinados asuntos que permanecen sin resolver

no hay final entiende

y caminando desde siempre sobre el piano calle abajo la tos la sensación las moscas del pan tienen algo que decir los topos la última palabra

entonces viene a mi memoria el arte de alimentar ausencias dando duro al otro y al que pase vertebrando turbulencias como el que encuentra su estrella en el abrigo

ese sueño que arrastra a otro

parte de mí y oreja nuestra resonando como un tambor o un clavo en la mejilla de uno y en la de otro

 
Leer más...

from Theo Chevêche

La forêt urbaine, un dimanche de novembre

La forêt urbaine, le dimanche matin, accueille un défilé de coureurs. Le mois de novembre, le ciel gris du nord-est, cette froide humidité qui emplit l'air, rien de tout cela ne semble perturber le flot continu des baskets qui tapent le sol comme une grosse pluie frappe aux carreaux.

Qui aurait l'idée saugrenue de passer par là en marchant se trouverait vite submergé·e par la marée. Ils courent, vieux hommes solitaires, groupes tonitruants, garçons hurleurs, femmes en short aux jambes rougies de froid — ils courent, chasuble tout propre sur le dos, bandeau de trek sur la tête, montre connectée au poignet ou téléphone intelligent savamment accroché au bras.

Il faut saluer la détermination des adeptes du jogging qui, comme nous le découvrons aujourd'hui, occupent leur dimanche matin à courir en boucle dans cette forêt aménagée de périphérie. C'est un peu comme une messe moderne au grand air. On s'habille pour les circonstances, on retrouve ses connaissances, ou l'on poursuit seul la quête de soi-même et le salut de sa santé.

Toujours est-il qu'à chaque vague nous nous écartons du chemin, nous stationnons dans les feuilles mortes, nous attendons, comme les tortues que nous sommes face aux lièvres qui courent et courent.

Heureusement pour nous, les lièvres dans leur course suivent religieusement la grande piste dégagée, tandis que notre lenteur nous laisse voir des chemins de traverse dans lesquels nous nous glissons bientôt. Soudain, tout est calme. On n'entend plus que l'autoroute indistincte, au loin, mais on peut se laisser croire que c'est le vent qui souffle en lointaines rafales — magie de l'imagination.

Nous errons par les petits chemins de terre, tournicotons entre les arbres couverts de mousse, traversons une passerelle au-dessus des bolides lancés à 130 km/h sur leur grand chemin de bitume, et nous songeons avec frayeur qu'il nous arrive à nous-mêmes d'être passagers de tels monstres de technologie.

Nous laissant porter par les sentiers qui serpentent devant nous, nous déroulons nos jambes en même temps que nos pensées. La marche est propice à la contemplation autant qu'à la discussion. Et le regard vagabonde, s'étend aussi loin qu'il le désire. J'aperçois dans les fourrés un arbre mort qui offre le couvert à de gigantesques champignons blancs. Plus loin, ce sont des arbres vifs, coiffés d'orange pétant, de jaune acidulé, de pourpre sage, qui bordent le chemin, et nous foulons un tapis de mêmes couleurs, où s'entassent des feuilles à profusion.

Et c'est ainsi que l'automne défile, au rythme d'une marche tranquille, dans la forêt de périphérie.

Image

#SilentSunday #forêts #élogedelamarche #automne

 
Lire la suite...

from Roscoe's Quick Notes

Raiders vs Seahawks

NFL Sunday.

Today's game of choice in the Roscoe-verse has the Las Vegas Raiders playing the Seattle Seahawks. Two reasons I'm choosing this particular game: 1.) Fernando Mendoza, and 2.) the Pittsburgh Steelers game is playing too late for me to follow.

And the adventure continues.

 
Read more...

from Rippple's Blog

Stay entertained thanks to our Weekly Tracker giving you next week's Anticipated Movies & Shows, Most Watched & Returning Favorites, and Shows Changes & Popular Trailers.

Anticipated Movies

Anticipated Shows

Returing Favorites

Most Watched Movies this Week

Most Watched Shows this Week


Hi, I’m Kevin 👋. Product Manager at Trakt and creator of Rippple. If you’d like to support what I'm building, you can download Rippple for Trakt, explore the open source project, or go Trakt VIP.


 
Read more...

from Abstracciones

si apenas es comprensible es que es así y no es necesario entender

sencillo / a golpe de pecho el latido el latigazo

y el testigo que mira al que se arrastra con más peso del que lleva pupilas propias de una lenta hipnosis la piel huracanada

notas que los labios se humedecen como pétalos al alba presente aquí para cualquier cosa o simplemente para lo que venga

porque es tan alma esta carne espíritu enraizado en el espacio inmaculado

/ canta al dulce pájaro sonido breve que se agota

dame esa esperanza que es hija de la raíz que el tiempo acorta la que crece en espinas

y quédate por favor como si el deseo de esta carne pudiera ser amable permaneciendo luego en el gozo eternamente en rama

 
Leer más...

from Schykle's Blog

Addressing double standards and unrealistic expectations

A few weeks ago I had shuffled between a few laptops trying to find one that I really liked. I spent a lot of time dealing with issues that I don’t think most people ever really have to consider, but I also ran into issues I think people just accept because it’s the default computing experience. Linux is ugly but Windows may be uglier.

My own failures

I’m no saint. I have a long history of being obsessive over the very specific way my apps, desktop, and underlying system are built and installed. When things are great they’re really great. The level of control I have when running Linux has made me feel like I can really push the boundaries and eventually get a Perfect™️ system. Unfortunately, the fact that it’s so flexible and that there are so many options has also allowed me to very quickly give up the moment I run into an issue. Strange issues with how one app is working that I can’t quite figure out? Nuke and pave. New install of another distribution. I see another distribution implement the boot loader in a way I like better? Nuke and pave. New install of yet another distribution... Obviously, this isn’t healthy, and I’ve been thinking a lot about this and how it differs from how most people use their computers, but also how there are core similarities that perhaps give Linux a bad rap.

Accepting slop

The other side of this coin is on the Windows side of things. Every time I’ve booted up a new machine, I am very quickly infuriated by the absolute drag that is the Windows initial setup. Multiple reboots, the insistence on using a Microsoft account, having multiple subscription services beg for my money and vaguely suggesting that my data could be lost if I choose not to use OneDrive, and then partner prompts for McAfee or OEM data collection... the list goes on. This is the Windows experience. This is the experience every single person goes through when buying a new PC. I haven’t even mentioned the part where updates after you set up the machine take anywhere from three to seven reboots to eventually completely finish.

If I experienced even half of this during my first run on a fresh Linux install, I’d genuinely just wipe the drive and move on. Despite my own issues with being far too willing to just throw things away, I think this is a completely valid reaction. What’s interesting to me is that Windows users don’t do something similar. Obviously the reasons are nuanced and complex, but boil down to just a few key factors:

1) There are no other options. Windows isn’t an ecosystem of distributions with different implementation details, it’s just one thing. 2) Most users don’t know just how bad it actually is. They have nothing to compare it against. 3) Most users are not inclined to do something about it. Whether it be lack of technical experience, knowledge, and the association of the computer as a thing that includes the software, rather than just the hardware itself.

Okay, so why not just wipe the drive and do a clean Windows install from an ISO. It’s easy enough to download and write to a flash drive...

The double standard

This is where things get quite interesting to me. I’ve done the ‘install Windows from an ISO’ thing so, so, so many times. One thing I’ve learned by doing this is that the driver situation on Windows is quite dire. Booting into any modern machine with a fresh ISO often leaves me with something (or many things) missing. Not having any network drivers is the most common. Intel, MediaTek, Broadcom... all the same. Sometimes they are present, but then my touchpad drivers don’t exist. Alright, I can just use the keyboard. Oh! There’s no driver for my... SSD? What?

This very specific experience was an eye-opener for me regarding the perception that folks have of Linux based on (often outdated) experiences with a missing device driver when installing Linux. When someone writes a Linux ISO to a flash drive and gives it a shot, missing Wi-Fi drivers is usually an instant mark of failure. No consideration is given to troubleshooting because on Windows, that just wasn’t necessary. Because people turn on their PCs with the drivers that came pre-installed by the OEM, they have no clue that the same exact issues are present on Windows, if not worse. The only difference is that they didn’t do the installation themselves.

Ogres have layers

The conclusion that I’ve come to is that there is a direct connection to the unfair expectations that are thrust upon Linux distributions when folks try it out and the overall pressure that Linux distributions and Linux software are under by the general user base. Aside from the reality of passionate people exhibiting passionate expression, I think Linux being seen as a safe haven or a revival for peoples’ machines is also responsible for the harsh criticism it receives for minor issues. It apparently takes so much to push users to the point of actually trying another operating system (otherwise why would they continue to deal with the hellscape that is Microsoft’s equivalent to an eBay storefront for their services that they’ve disguised as an OS), that when they attempt to try something they assume will fix things, any issue is a sign that things must not actually be any better and it’s easier to give up than to trod on.

This extends so much deeper than just the initial experience. It cascades onto desktop software. Issues with an app? Typical Linux experience. Issues with the desktop? Typical Linux experience. The pressure on Linux is higher because the expectations of it being perfect generally ignore the fact that Windows is inherently flawed in both similar and different ways.

None of this matters... BUT!

All this is just to say that I recognize how much harsher I personally have been on Linux at times because my expectation is that things should be so much more perfect than they are. I also recognize that I’m not alone and the unrealistic expectations that others set are also quite weighty and paint an unfair picture of the Linux desktop.

My goal here is ultimately just reasoning through all of this because the reality of most situations is that the grass is only green if you water it. The thousands upon thousands of contributors working on Linux software from the kernel to the desktop to services and apps are all watering that grass. A massive community of people passionate about building great software and this is an incredible contrast to the Windows ecosystem which has continued to be stuffed by Microsoft. The difference is that people just don’t know any better.

I hope that comes as some form of comfort to those of you who are working on and/or enjoying the wonderful things we have here on Linux. There’s always room to improve and none of it is perfect, but the pressure and the expectations are often unrealistic and extreme. The work you’re doing is incredibly valuable to so many people.

Much love!

side note: in case anyone is looking for shims, I’ve included this footnote to mention them. Shim. Shim sham. Shimmy!

 
Read more...

from The Morning Patrol with Mastelek💪

eddy explains the single point of failure

I left my Samsung phone on the table at home when I packed eddy to go to church.

The church is the road on the Cradle loop.

Well over halfway there, is when I suddenly realised the phone was missing.

Bliksem!

I told eddy. You know how screwed we are when we don't have a phone. Everything is now driven by that little rectangular piece of technology. Banking, communication, navigation, authentication, photographs, appointments, even proving that you are who you say you are.

Ja, said eddy. Single point of failure.

The phones disappear & everyone will be walking around like zombies.

Hell, eddy, you make me feel like I'll be kaalgat on the ride today without my Samsung.

The breeze was up & I was concentrating hard on slipstreaming behind the cyclists in front of me. There was no time for meditation or philosophical discussions. Not when you're trying to conserve energy & stay tucked in behind someone's rear wheel.

But the thought stuck.

As I was driving back after the ride had finished, I started thinking about my parents & their generation. How many of them, and their acquaintances, had already kicked the bucket. Having only had that spawn of Satan in their hands only at the end of their stint on Earth.

Except for Oom Etienne Bruyns.

He was still alive & kicking in Ballito.

When I got home, I decided to give him a call via the Devil’s tongue.

He answered. Still alive, he confirmed, although he'd had all his knees & hips replaced. He still managed the occasional round of golf, which he rather wonderfully described as moer en soek.

We had a good chat about the old days.

About Ouma Joey & Oupa JT. Joey was his godmother. About how my mom's boet had artificially inseminated one million cows.

Phew!

That's a lot of cows.

He asked about my sister. I told him how worked up she'd become about retiring that she eventually ended up in hospital with diabetic shock.

Work is not worth that, we agreed.

Poor & alive is better than dead & rich.

I was going to tell him about eddy & how a bicycle has absolutely no concept of wealth or money. It doesn't care about your bank balance, your job title or how many properties you own.

It only cares whether you can keep turning the pedals.

But I thought the Oom might think I'm bossies.

He had already asked me how to spell psychosomatic when I explained that this was what I thought had contributed to Lyn's hospital stay.

After the call, I unloaded eddy & put him on his stand in the bedroom.

I had something to ask him.

eddy, what drives us humanoids to experience these psychosomatic issues that eventually manifest themselves physically?

Is it a modern thing? Or have we always been like this? Is it our sentience? Our ability to think about tomorrow, worry about yesterday & somehow make ourselves miserable in the present?

We have evolved to become incredibly sophisticated. We can put people on the moon, communicate across the planet in milliseconds & carry the universe's information in our pockets.

Yet we can also worry ourselves sick about a retirement date, a bank balance, a meeting, a missed call or something that hasn't even happened.

Perhaps that's the irony of being human.

We have minds capable of imagining almost anything, including our own demise. And sometimes the body gets caught up in the imagination.

Our brains don't always distinguish neatly between a physical threat & a perceived one. Prolonged stress can affect hormones, sleep, blood pressure, digestion, immunity & all sorts of other bodily functions. The mind and body are not independent. They're are like the branches & roots of a tree. The tree of Life. Maybe that is why all the hippies have it as a tattoo?

And perhaps we've simply become very good at creating threats where none exist.

I looked at eddy.

He had no comment about my retirement plans, no concerns about the economy, no outstanding invoices & absolutely no interest in whether I had remembered my Samsung or what tattoo I was going to burn onto my ass.

He just stood there.

“Mastelek, you humanoids have an extraordinary ability to suffer twice. First, you imagine something terrible happening. Then you suffer when it happens. Sometimes it never happens at all.

“You spend so much time worrying about keeping everything together that you forget to actually live.

“A bicycle doesn't worry about the hill ahead. It doesn't worry about the hill behind. It just deals with the road underneath its wheels.

“And one more thing, boet.

“Your phone might be a single point of failure, but your head is a whole gemors of unnecessary problems.

“Perhaps you should leave that Samsung at home more often.”

Bliksem.

I think eddy might be onto something.

Ronald Bartels | LinkedIn | Instagram

 
Read more...

from Chemin tournant

Les phrases dans le cerveau, leurs débuts plutôt, d’un dire attendu venant du vide de soi, patienté jusqu’aux nerfs, finissent en tronçons de bois que des mains engourdies jettent au bas-côté. La ville se tient muette, à ne rien tirer d’elle, planquée, souterraine, nous laissant seulement courater sur son dos. Hors Éros, qui la guette, la pense, voudrait l’écrire ou la parler s’il savait le faire, en dépaysager l’urbain ? Et ça paraît si futile ou vain, qu’on se retient de sacrer son nom puis de maudire, outre soi-même, les gens qui vont sans voir tout du long d’elle, de son multicouloir immobile.


La vie solitaire de É. Sambòko prend la suite des #Didascalies de Fenêtre sur ville. Un personnage est apparu, qui déplace la perspective de la ville et de son écriteur. Sambòko veut dire “chaussure” mais aussi “énigme” si l’on oriente autrement l’accent. Où va É. Sambòko ? L’on ne sait.

#LaviesolitairedeÉSambòko

 
Lire la suite... Discuss...

from An Open Letter

Today I had what I consider my first real birthday party. I don’t even know where to start. I hosted a lot of different events and games, And I think overall people loved it! There were a lot of really fun moments and people kept asking me about how much effort I put into it. When it was time for cake, I went to the car to grab something for a second, and when I had come back the lights were off, and everyone was gathered around the table. Honestly, I was really afraid and I had went to the bathroom right before, and I felt like I was going to cry and I was horribly anxious. How do you tell someone who has felt like they have slipped through every crack in a room that suddenly everyone sees them? And in such a beautiful way. I felt like I was just going to cry from them singing, happy birthday, but then they told me to prop up my phone and record. And when they did that, they instead told me that they all were going to come one by one and put a candle one at a time and tell me a wish that they have for me. And my voice is breaking up because I’m going to cry again thinking about it. I think about how before this one of the greatest gifts that I have kept for my birthday was the happy birthday sign. My ex’s family had put in the cake for me. And now I have more candles that I could’ve dreamed of. Everyone took turns coming up to me, lighting a candle, and telling me something sweet and a wish for me. And I couldn’t stop crying.

So many people told me how grateful they are for the community that I have built and how thankful they are to get to be a part of it. They told me how many people they have gotten to meet through me and how many fun things they’ve gotten to do. And I couldn’t help but think about all these years that I have spent my birthday and the holidays alone. And I think about how many nights I fell asleep before college dreaming about how I would have friends that I could hang out with people that would give me hugs. I could cry and I am crying because I struggled so much and I have blindly put in so much faith along the way working at this. I always dreamed about being able to have a life like this, and I have made it in mine. I grew up without a community, because my parents kept us isolated at home. And I never felt like I fit in anywhere, with the exception of online. And I’m grateful for that in several ways, and I also think that I have become a deep and unique person because of that lack of conformity that comes with community. But I always wished that I would find my people and I have spent so many nights thinking about it and I’ve written about it so many times I’ve talked with my therapist so many times and I now have that. And I have it in such a loud way that so many of the other people in the community that I have built remind me of this fact.

I also had several people tell me about how unapologetically myself I am, and how it inspires them to feel comfortable being themselves. I had several people tell me how I am always having fun in whatever situation, and I couldn’t stop but cry because it reminded me of how fucking hard I have worked and pushed myself to learn how to be happy. I have people tell me how much energy I have and I feel so grateful to myself for trying so fucking hard through pure willpower. I think about how many days I have woken up at 4 PM because I just don’t have any will to get up.

I had so many people tell me how thoughtful I am towards my friends and how much I care about others, and how much I think about them. And I want to cry so fucking bad because I tried to be the person I needed at so many different points in my life and it feels like I have been doing pretty good in that sense. I think it is such a beautiful thing for your friends to think about you and the word that comes to their mind is thoughtful and considerate. It feels like all of the quiet little times I have accommodated someone without telling them, or made an effort to include someone slipping behind or checking in on someone has been seen.

And most of all I had a lot of people wish that I truly knew how many people around me care about me and love me. And that devastated me in the best way, because I cannot even begin to count how many times I have thought that I should kill myself. And how many times I have thought and truly believed that people would not miss me. And I know that so much of that is depression trying to trick me, but at the same time, it’s such a uphill battle to convince yourself of this so blindly when the only thing you hear is the opposite. But today I heard so many voices just telling me that I underestimate how loved I am.

And I vividly remember sitting here in the bottom of the shower writing about how it felt cosmically unfair that I have tried so hard and putting so much effort into being a good friend, and every year I would dread my birthday. And I would see other people being celebrated and even all of these sweet things like surprise parties, or people all giving wishes. And I feel that bitterness and envy, because what did I do to be doomed to not get that. And I know that it is a lot more complicated than that, and it is in no way shape or form a reflection of how much the people around me care if they did not do this. But also, I did get more than I could’ve dreamed of. And I still get to the day before my birthday as a sleepover with friends. And this is way more than I could’ve wished for, honestly, it’s more than I even feel comfortable receiving. And I guess I want to say that I want to thank the universe. And I’m also really thankful to myself for all of the things and work that I have been putting in so consistently, because things like this don’t just accidentally happen.

It’s more than everything I ever wanted.

 
Read more...

from librasun.scorpiomoon

Kurama to Kibune trail today.

I could have stayed all day. The trees, the autumn leaves; I can’t even begin to explain how beautiful it was. But it was the smell, that exact feeling of being right where I love to be. Far from the city noise. Nature calls, and it just gives me my energy back.

Hiked it with Simon, my new Swiss friend. He is a sensitive soul with so much good insight to share. The way he pays attention when you speak, not everyone knows how to do that. Most people don’t really care about people. When you find someone who actually listens, who takes a real interest in your story, they rapidly become part of it.

What a great day.

No time for the Kurama Onsen today, but the mountain gave me everything I needed anyway.

 
Read more...

from AnOublietteofThought

I awoke from nightmares with your lips upon my shoulder, and your hand seeking the warmth of a wanton response. There was power slinking through the quietly rumbled syllables of my name as you bid it coax chilled flesh to ripple from the kindling of your creation. I felt eternity beckon in a longing scratch of deeply buried hunger until... until... until there was naught — mere aftershocks of a vacancy pledged eternal.

© 2026 AnOublietteofThought. All rights reserved.

https://youtube.com/watch?v=GrYnK1LkEp8&is=xZVNE4JV5BNi6tw2

 
Read more...

from Notes To The Internet

There is a twenty-four-year-old on my screen right now, filmed in crisp, golden-hour 4K, solemnly unpacking a canvas tote bag as if she were defusing an unexploded ordnance from the Cold War.

She pulls out a paperback novel with a cracked spine. She pulls out a disposable Kodak camera, a tin of peppermint lip balm, a half-finished crochet square, and a folded newspaper crossword. She looks into the lens with the grave, missionary zeal of someone who has just discovered fire, and announces to four hundred thousand strangers that she has finally conquered her screen addiction by inventing what TikTok now calls an analog bag.

My grandmother carried the exact same collection of items in a leather purse from 1954 until the day she died, and she never once felt compelled to film an unboxing video about it.

Yet before we roll our eyes too hard at a generation rebranding carrying a book in a tote as a radical lifestyle movement, look closer at what is actually happening here. Cambridge Dictionary has already flagged friction-maxxing and analogue bag for the lexicon of 2026. Millions of people who grew up inside the warm, frictionless womb of the algorithm are suddenly, desperately trying to make their own lives harder on purpose.

They are paying with crumpled paper bills instead of tapping a watch. They are shooting thirty-six exposures on 35mm film and waiting a week to see if the light was any good. They are boarding morning commuter trains with a heavy tote slung over one shoulder and their phones buried at the bottom like contraband—all to engineer a few inches of resistance between an idle thumb and an infinite feed.

For twenty years, Silicon Valley preached a single, relentless gospel: the elimination of friction. Every startup pitch, every interface update, every generative model promised the same salvation—no waiting, no effort, no awkwardness, no snag between desire and fulfilment.

One click to buy. One swipe to date. One prompt to draft the condolence email you couldn't bring yourself to write. Convenience was crowned the supreme moral good, and any task that required patience, callouses, or mild discomfort was treated as a design flaw to be engineered out of existence.

We got everything we asked for, and it hollowed us out.

When every surface of daily life is sanded glass-smooth, nothing pushes back against the hand—and when nothing pushes back, the hand forgets it is holding anything at all. Convenience didn't liberate our time; it liquefied it. It turned afternoons into mist, conversations into transactions, and attention into a twitchy, half-starved animal pacing behind a pane of glass.

Even our rebellion has been trained to perform for the feed: we film our screen-free Sunday mornings and upload them to the very casino we are trying to escape, hoping the algorithm rewards our abstinence with engagement.

Still, you cannot fake the hunger underneath the performance.

Watch someone sit on a crowded subway with an analog bag in their lap. At first, their right thumb twitches against their thigh—the phantom limb of a decade spent scrolling through six-second dopamine hits. Five minutes pass. Ten. Slowly, the shoulders drop. The eyes settle onto ink pressed into rag paper.

A knit stitch is dropped, cursed at, and pulled back by hand.

That tiny, exasperating snag—the dropped stitch, the seven-letter crossword clue that refuses to yield, the ink smudging the side of a palm—is the whole point.

A machine can spit out three thousand fluent words before your coffee cools, and an algorithm can serve an endless parade of effortless entertainment until the day you die. Ease is cheap now; automation has flooded the market with it.

What remains scarce, stubbornly expensive, and unmistakably human is friction—the deliberate choice to wrestle with something physical, slow, and uncooperative until it answers back.

Call it friction-maxxing if you need a hashtag to smuggle it past the gatekeepers of the feed. Call it an analog bag if a canvas tote feels more heroic with a modern name.

Underneath the internet slang is an ancient, unglamorous truth we nearly engineered out of our bones.

A life without resistance leaves no trace, and the things that actually tether us to the world are always a little too heavy to carry in a pocket.

Notes To The Internet by Dev Das

 
Read more...

from SmarterArticles

The email looked like a revenue opportunity. In early June 2026, some developers whose Android apps had been downloaded millions of times received an invitation from Google to “join a confidential content offer pilot”. The pitch was simple: “Get paid for sharing the code powering your apps, as well as your archived projects.” The reassurance came straight after: “This is non-exclusive. You keep 100% of your IP.”

The message, first reported by Jason Koebler at 404 Media and then widely picked up, never used the words artificial intelligence. It said the code would help “improve Google's developer tools and products”. A linked page was more candid, describing “partnerships to improve our AI products”. Nobody outside the pilot knows what Google was offering to pay.

Earlier in the year, a founder named Keelan Miskell had been closing down his crypto startup. According to MIT Technology Review, he netted roughly $25,000 for his codebase, with a further payment, probably around $15,000, pending for the company's workspace data from Google, Notion, Figma and Slack. “At least all that stuff we were doing for two and a half years is worth something to someone somewhere,” he told the magazine.

Then, in August, came the deal that made everyone look up. In the bankruptcy of Spirit Airlines, which stopped flying in May, Google won an auction for the carrier's corporate data with a $10 million bid. TIME's Billy Perrigo reported that the cache held 100 million emails, 500 million Microsoft Teams messages and about 30 million lines of code. A court filing released in November put the volume far higher: about 1.9 billion internal emails, 664 million Teams items, 91 million SharePoint and OneDrive files and roughly 30 million lines of code.

Taken together, these episodes describe something new: a market in which the private working record of software (the code, but also the commit history, the pull requests, the arguments in review threads, the tickets and the design documents) is being bought and sold as AI training material. What ethical, legal and security problems arise when that record changes hands? How can a buyer prove a seller had the right to sell it, when dozens of people wrote it? And does the money now flowing into this trade create risks that existing safeguards were never designed to catch?

Why the Messy Middle of Software Became Valuable

For a decade, AI companies trained on the public internet, and code was one of its richest seams. Public repositories on GitHub and elsewhere supplied billions of lines for the first generation of coding assistants. That seam is thinning. Epoch AI, a research group that tracks the inputs to machine learning, estimated in 2024 that the effective stock of human-generated public text was around 300 trillion tokens, and gave an 80 per cent confidence interval that it would be fully used at some point between 2026 and 2032.

Private code is the obvious next reservoir. It is not one that platforms can simply tap: when GitHub updated its terms in March 2026 to let it train on Copilot interaction data from individual users who do not opt out, it stated plainly, “We do not use private repository content at rest to train AI models.” Private repositories have to be acquired from whoever controls them, and they are valuable for reasons beyond volume. A finished public library shows what working software looks like. A private repository, with its full history, shows how software actually gets made: the false starts, the reverted commits, the reviewer who points out a race condition, the ticket that explains why a strange workaround exists. That is precisely the material that the newest training methods crave.

Turing, the AI training and talent company, made the case explicitly in its AGI Advance newsletter of 24 December 2025, announcing a programme it called Project Lazarus. “We're acquiring full private repositories, design docs, testing logs, infrastructure manifests, and internal wikis from defunct startups,” it wrote, naming fintech, pharmaceuticals, manufacturing and software as target sectors. Existing datasets, the newsletter argued, “fail to capture the texture of real work”. The stated aim was to “preserve the complete operational history of defunct companies”.

The appetite is driven by reinforcement learning. Rather than simply predicting the next token of text, AI agents are increasingly trained in simulated environments where they take sequences of actions and are rewarded for good outcomes. TIME reported that gains from this approach have been largest in coding, where results are easy to verify. Surge AI builds such environments, which it calls reinforcement-learning gyms, and Nick Heiner, who leads that work, told MIT Technology Review he wants archives that capture varied situations, disagreements and judgement calls. Speaking to TIME about the Spirit acquisition, he said the purchase makes sense “if you believe that your agent is going to generalize into the rest of the economy.”

There is also a quality argument. In a widely cited 2024 paper in Nature, Ilia Shumailov and colleagues showed that models trained recursively on the output of other models suffer “model collapse”, progressively losing the rarer parts of the original data distribution. They concluded that data about genuine human interactions will become increasingly valuable as AI-generated content floods the web. A repository written by humans, before coding assistants were commonplace, is that kind of data.

A Market Assembled in Under a Year

The supply side organised itself quickly. Startups fail constantly; MIT Technology Review cited estimates from Carta and AngelList showing shutdowns rising by between 26 and 56 per cent a year recently. An “end-of-life” industry has grown up around them, and part of that industry has discovered that the corpse has value.

SimpleClosure, a service that handles the legal and operational wind-down of startups, added data sales in April 2026 through a platform called Asset Hub, where closing companies can list code repositories, Slack archives, emails and internal documents. In April, Forbes reported that the company had handled nearly 100 such deals, with sellers typically receiving between $10,000 and $100,000; heise online, summarising that report, quoted chief executive Dori Yona describing “a feeling of a gold rush from these companies trying to get their hands on real-world data”. By October, MIT Technology Review reported more than 150 deals, an expectation of returning more than $10 million to startups by the end of 2026, and Yona's estimate that 47 per cent of SimpleClosure's deals now include code or data sales, once rare and “somewhat taboo”.

Competitors followed. Brendan Mahony, chief executive of Sunset, another wind-down firm, told MIT Technology Review that his company values assets by headcount, years in operation, data volume and how the team used its tools. “This operational exhaust data is like the wood shavings that everyone thought had no value, but it actually has a ton,” he said. Brokers now publish buying guides. One, run by Human Union Data, lists Project Lazarus as paying between $10,000 and $100,000 for legacy code; that figure is the broker's own claim, and Turing does not publish its prices. Dan Novaes, chief executive of the data broker Mode.Inc, told Business Insider, as reported by IBTimes UK in October, that “the demand is just astronomical.”

The buyers are foundation labs, vendors that build simulated workplaces for training, and established technology companies building their own models. What they want is completeness. The Human Union Data guide tells sellers that buyers are after “real production code, internal documentation, and development history”, listing “pull requests, design docs, incident notes” as the material that makes a package whole. The completeness that makes the data valuable is exactly what makes it legally and ethically fraught.

A Repository Is a Crowd, Not a Possession

Start with the most basic question: who owns a git history?

The instinctive answer is the company. In many cases that instinct is broadly right, but only broadly. Under section 11 of the UK's Copyright, Designs and Patents Act 1988, “The author of a work is the first owner of any copyright in it,” with an exception: where a work is made by an employee in the course of employment, “his employer is the first owner of any copyright in the work subject to any agreement to the contrary.” The United States reaches a similar destination through the “work made for hire” doctrine, which covers “a work prepared by an employee within the scope of his or her employment.”

Now look at who actually appears in the commit log of a typical startup. There are employees, certainly. There are also freelancers and agencies, whose work is not automatically owned by the client in either jurisdiction; in the United States, commissioned software does not fall within the nine statutory categories that can be made works for hire by written agreement, so ownership passes only through an explicit assignment. There are co-founders who wrote early code before the company was incorporated. There are interns, advisers and contributors from partner firms. A repository that has run for five years may contain the work of dozens of people under a dozen different contractual arrangements, some of which were never written down.

Then there is everyone else's code. Private repositories are full of open-source components, vendored libraries and snippets copied from elsewhere, each carrying its own licence. Black Duck's 2026 Open Source Security and Risk Analysis report, which audited 947 commercial codebases across 17 industries, found licence conflicts in 68 per cent of them, up from 56 per cent the year before; one codebase contained 2,675 distinct conflicts. The report links part of that rise to AI coding assistants reproducing material derived from copyleft code without the original licence information, a phenomenon it calls licence laundering. A seller who cannot say which open-source licences govern the files in a repository is in no position to warrant that those files can be licensed onwards for training.

Open-source projects have built some machinery for this problem. Many use contributor licence agreements or the Developer Certificate of Origin, a short statement in which a contributor certifies that “The contribution was created in whole or in part by me and I have the right to submit it under the open source license”. Private companies rarely have anything comparable. The rights in their repositories are inferred from employment contracts, many of which predate the idea that internal engineering discussion could become a product.

Nor is copyright the only right at stake. Review threads and commit messages are written conversation: explanation, critique, sometimes humour or irritation. An employer may own the text, but that does not settle whether selling it is fair to the people who wrote it, or lawful under data protection law.

Possession Is Not the Same as Ownership

The Spirit Airlines auction has become the first public test of these questions. Mercor, an AI data company, was named backup bidder at $7.5 million, and another firm, micro1, later filed notice of a $12.5 million offer. The approval hearing was adjourned repeatedly through the autumn before being set for 17 November, and the objections filed in the bankruptcy court in White Plains read like a checklist of what can go wrong.

Springshot, a software company that ran operational tooling for Spirit, objected that the dataset could include its own intellectual property. Its filing cites a contract clause giving it rights to “any data or information generated by the Service or Software.” Chief executive Doug Kreuzkamp put the distinction plainly, according to an account published by The Next Web: “The distinction is between the information Spirit supplied and the proprietary outputs our platform generated.” Explaining why the company had not objected earlier, he told the Miami Herald, as quoted in the same account, “we had no reason to believe that Spirit would sell property that wasn't theirs.”

International Aero Engines, the engine manufacturer, filed its own objection arguing that its proprietary commercial, technical and financial information may have been copied into Spirit's internal communications, and that, in the words of its filing reported by ComplexDiscovery, “deidentification is insufficient to ensure that the IAE Proprietary Information has been removed.” Navitaire, Spirit's long-standing reservations platform provider, joined with Amadeus in a limited objection.

These objections expose the central weakness of the market: a company's systems hold far more than the company owns. Repositories routinely contain material supplied under non-disclosure agreements, vendor documentation pasted into tickets, customer configurations and code written under licence. In a working company, contractual confidentiality keeps that material in place. In a sale, it travels with everything else unless someone takes it out.

That matters to buyers, not just sellers. The EU's Trade Secrets Directive of 2016 makes the acquisition or use of a trade secret unlawful when the person “knew or ought, under the circumstances, to have known that the trade secret had been obtained directly or indirectly” from someone using or disclosing it unlawfully. A buyer who acquires a repository full of third-party confidential material without asking reasonable questions may not be able to claim innocence later.

There is now a striking precedent on the cost of careless acquisition. In Bartz v Anthropic, Judge William Alsup held in 2025 that training on lawfully acquired books could be fair use, but sent the claims over pirated library copies towards trial. Anthropic settled for $1.5 billion, covering roughly 480,000 works, and the settlement received final approval in July 2026, according to Jurist. The lesson for the code market is not that training is unlawful. It is that how training data was obtained can matter enormously, and that a court may look past the model to the provenance of the inputs.

The People Who Live Inside the Diff

Every commit in git carries an author name, an email address and a timestamp. Under Article 4(1) of the EU's General Data Protection Regulation, personal data means “any information relating to an identified or identifiable natural person”, and an identifiable person is one who can be identified “directly or indirectly”, including by a name or an online identifier. A git history is therefore, among other things, a structured personal data set: a record of when named individuals worked, what they worked on and, in review threads, what their colleagues thought of their work.

That last part deserves attention. Code review is one of the most socially charged activities in software engineering. A 2020 study by Carolyn Egelman, Emerson Murphy-Hill and colleagues at Google, presented at the International Conference on Software Engineering, surveyed 1,317 developers about negative experiences in review, which the authors called “pushback”. They found such experiences relatively rare but harmful when they occurred. A sold repository carries all of that: the blunt rejection, the apologetic reply, the thread in which someone was told they were wrong. These people wrote for colleagues, not for a model.

European regulators have started to address the training side. In Opinion 28/2024, adopted in December 2024, the European Data Protection Board said that whether an AI model can be considered anonymous must be assessed case by case, set out a three-step test for relying on legitimate interests, and indicated that unlawful processing at the development stage may affect the lawfulness of later deployment, with remedies that could in serious cases include deletion of the data or the model. The opinion did not contemplate a secondary market in staff conversations, but its logic applies.

American law offers less. Ifeoma Ajunwa, a law professor at Emory University and author of The Quantified Worker, told MIT Technology Review that “Employers should have express consent before selling workers' data,” noting that no federal law bans such sales. She described the proceeds, which typically flow to creditors and investors rather than to the workers whose words are sold, as “captured capital”. Greg Ewing, an attorney who advises AI startups, called such data “legally radioactive” and described “a Wild West of AI training”.

Sellers and brokers insist that personal information is scrubbed. SimpleClosure says it removes personal data before sale. The Spirit deal shows what a serious attempt at scrubbing looks like: according to chapter11cases.com, the parties adopted the California Consumer Privacy Act's de-identification standard, appointed Tonic.ai as an independent de-identification agent for unstructured data such as email, made certified de-identification a condition of closing, required re-identification testing before each transfer, and obliged the buyer to commit publicly not to attempt re-identification. Those protections originally covered customers rather than staff. After unions led by the Association of Flight Attendants objected, Skift reported in November that revised terms require Google, still paying $10 million, to cover the cost of de-identification as well and to commit publicly not to knowingly re-identify the data, while employee medical examinations, payroll records, drug testing, crew pairings, biometrics and union grievance filings are excluded from the sale altogether. “Without our union, there would have been no one to speak for workers in this fire sale of their private information,” said Sara Nelson, the union's president.

Even that may not be enough. In a letter dated 8 October 2026, more than a hundred members of Congress led by Senator Elizabeth Warren and Representative Steven Horsford warned that “Removing names, email addresses, or other direct identifiers does not necessarily make a dataset anonymous.” The point applies with special force to code. Writing style, working hours, the modules a person owned and the distinctive way they phrase a review comment can identify them as surely as a name. And a git history without its authorship is a much less useful training asset, which creates a quiet commercial pressure against thorough scrubbing.

Secrets That Travel With the Code

The security problem is more concrete still. Developers routinely commit things they should not: API keys, database passwords, cloud credentials, private certificates. GitGuardian's State of Secrets Sprawl 2026 report, published in March, counted about 28.65 million new hardcoded secrets added to public GitHub commits in 2025, a 34 per cent increase on the year before. Internal repositories, the kind now being sold, were roughly six times more likely than public ones to contain hardcoded secrets. More than 64 per cent of secrets that GitGuardian confirmed as valid in 2022 were still valid when retested in January 2026. And about 28 per cent of incidents originated entirely outside repositories, in collaboration tools such as Slack, Jira and Confluence, precisely the systems now sold alongside code.

Deleting a secret from the current version of a file does not remove it from git. It persists in history unless that history is rewritten. A buyer who values complete history is therefore buying, by design, every credential anyone ever committed and later regretted. Some will have been rotated. Many, on GitGuardian's evidence, will not.

The risk does not end at transfer. Language models can memorise and regurgitate their training data. In a 2021 paper presented at the USENIX Security Symposium, Nicholas Carlini and colleagues extracted hundreds of verbatim sequences from GPT-2's training data, including personally identifiable information and code, and found that larger models were more vulnerable. A credential that survives into a training corpus could, in principle, resurface in a model's output. A dead startup's cloud account may be closed; its partners' shared keys may not be.

Provenance Tools Built for a Different Problem

If the market is to function legitimately, buyers need something like a chain of title for code: evidence of who wrote what, under which agreement, and with whose permission it is being sold. Some of the tools exist. None was designed for this job.

The most rigorous work on dataset provenance comes from the Data Provenance Initiative, a collaboration led by researchers including Shayne Longpre at MIT. Its audit of more than 1,800 text datasets, published in Nature Machine Intelligence in 2024, found licence omission rates above 70 per cent and error rates above 50 per cent on popular dataset hosting sites. If carefully curated public datasets are that poorly documented, the documentation that comes with a hastily sold startup repository is unlikely to be better. Industry groups have tried to standardise the metadata: the Data & Trust Alliance, a consortium of large companies, published data provenance standards covering source, legal rights, lineage and intended use. Such standards help only if someone fills them in truthfully.

Git itself offers little assurance. Its documentation is candid: the author name “has no effect on authentication”, and options such as —author and —date allow anyone to set the claimed author and timestamp of a commit to whatever they like. A git history is a record of what someone typed into a configuration file, not a verified log of who did what and when.

Cryptographic signing can change that. Sigstore's gitsign tool lets developers sign commits using an OpenID Connect identity rather than long-lived keys, recording the signing event in Rekor, a public transparency log, so that the signature can later be checked with git verify-commit. The Supply-chain Levels for Software Artifacts framework, known as SLSA and part of the Open Source Security Foundation, describes how to generate verifiable provenance for build artefacts. Software bills of materials, which the US Cybersecurity and Infrastructure Security Agency describes as “a nested inventory, a list of ingredients that make up software components”, can document which third-party components a codebase contains.

The trouble is timing. These tools establish provenance going forward. They work when commits are signed at the moment of creation and builds are attested as they run. Almost none of the repositories now being sold were built that way. A five-year-old startup history consists overwhelmingly of unsigned commits, and no amount of tooling applied at the point of sale can retroactively prove that a commit dated 2021 was really written in 2021 by the person named on it. SBOMs describe components, not the employment status of the people who wrote the glue code. Even the media world's answer, the content credentials standardised by the Coalition for Content Provenance and Authenticity, attaches provenance to finished objects rather than to an evolving, many-authored record.

What Brussels Now Asks to See

Regulation is starting to demand some of this documentation. Article 53(1)(d) of the EU AI Act requires providers of general-purpose AI models to publish a summary of the content used to train them. In July 2025, the European Commission's AI Office published a mandatory template for that summary. According to the Commission's own guidance, it requires providers to list their data sources, including private datasets licensed from third parties, and to describe relevant processing aspects such as respect for copyright. The obligation has applied since 2 August 2025 for new models; models already on the market before that date have until 2 August 2027. The AI Office's enforcement powers began on 2 August 2026, with fines of up to 3 per cent of worldwide annual turnover or 15 million euros, whichever is higher.

That is real pressure: a lab that buys a startup's codebase must at least acknowledge publicly that it trained on licensed private data. But the template has limits. The Commission has said it will not audit content at the level of individual datasets, acting instead on complaints or qualified alerts from its scientific panel. And a summary of sources is not a chain of title. A provider can accurately state that it used “private datasets licensed from third parties” while knowing nothing about whether the third party had the right to license them.

Incentives That Reward Forgery

The most troubling feature of this market is not any single legal gap but the way money changes behaviour around them.

Begin with what buyers prize. Sunset values assets partly by headcount and years in operation; broker guidance stresses development history and pull requests; Turing wants the “complete operational history” of a company. Buyers want long, busy, human histories because those are what make a codebase useful for training agents. Those are exactly the properties that git makes trivially easy to fake. Dates can be backdated with an environment variable. Author names can be set at will. Language models can generate plausible commit messages, review comments and tickets in volume. A fabricated five-year history, populated with synthetic engineers who argue convincingly in pull requests, is now a technically modest undertaking.

There is evidence that metadata on code platforms is already gamed when it has value. A study by Hao He, Bogdan Vasilescu, Christian Kästner and colleagues at Carnegie Mellon University, North Carolina State University and the security firm Socket identified around 4.5 million suspected fake stars on GitHub, with fake-star campaigns increasing by two orders of magnitude in 2024, largely to promote short-lived malicious repositories. Stars are a crude signal. Commit histories are a far richer one, and they now carry a price tag. If buyers pay more for histories that look human and long, some sellers will manufacture them, producing exactly the synthetic contamination that real-world data was supposed to avoid. MIT Technology Review noted that no company has published tests comparing training on real archives with the alternatives, so buyers may struggle to tell the difference.

The second incentive is laundering. A repository containing third-party code, an ex-employer's proprietary modules or material taken under NDA becomes harder to trace once it passes through a broker, is scrubbed of identifying metadata, and is merged into a training corpus with thousands of others. De-identification, presented as a privacy safeguard, also strips away the authorship information that might reveal where code came from. No such case has yet been documented, but the structure of the market rewards anyone who can present tainted material as clean.

The third incentive is insider exfiltration. Developers routinely have access to code they do not own. Until recently, the main buyers for a stolen codebase were competitors and foreign rivals, and the cases that reached court were dramatic. In January 2026, a federal jury in San Francisco convicted Linwei Ding, a former Google software engineer, of seven counts of economic espionage and seven counts of theft of trade secrets, in a case in which prosecutors said he had stolen more than 2,000 pages of confidential material about Google's AI infrastructure. That was a case about geopolitics. The new market creates a far more mundane temptation: a departing engineer, a disgruntled contractor or a founder in a dispute with co-founders may now find a ready, apparently respectable buyer for a private repository.

That is not hypothetical. According to IBTimes UK, citing Business Insider, Surge AI's Nick Heiner said someone had approached him offering a large company's codebase for millions of dollars, and he concluded that the seller did not have the rights to sell it. A less careful buyer, or one under competitive pressure to acquire data faster than its rivals, might not have asked.

The final incentive concerns who gets paid. In the startup wind-downs described by MIT Technology Review, proceeds typically go to senior creditors and investors. The engineers whose judgement, arguments and late-night fixes make the data valuable receive nothing and are usually not asked. Ryan Lock, co-founder of Polyshares, compared the offers to those of early oil prospectors buying land from unaware farmers. People with no stake in a transaction also have no channel through which to object, so the safeguard most likely to catch a bad sale, the knowledge of those who were actually there, is switched off.

Building a Chain of Title for Code

None of this means the trade must stop. A failing company has legitimate reasons to recover value from its work, and AI developers have genuine reasons to want realistic engineering data. The question is what a legitimate transaction would look like. The Spirit proceedings, existing law and the tools described above suggest a working standard.

Sellers should map every author in the history to an employment contract, a contractor agreement with an assignment clause or a documented licence, and remove whatever cannot be matched. The labour of that mapping is the provenance. Former employees and contributors should be notified and given time to object; the Spirit case surfaced vendors, unions and lawmakers only because a bankruptcy court made the sale public, and private startup deals have no equivalent forum. Vendored code, NDA material and partner data should be found through software composition analysis and contract review, then stripped out or separately licensed.

De-identification should follow the Spirit model of an independent agent, certification and re-identification testing before transfer, and should address the stylistic signals that identify developers even without their names. Every commit and every attached collaboration archive should be scanned for credentials, with live secrets revoked rather than merely redacted. Buyers should demand warranties of title backed by indemnities and escrow, so that the cost of a bad sale falls on whoever was best placed to prevent it. And companies that want their engineering record to be worth something later should sign commits and attest builds now, which would also make fabricated histories easier to detect.

The Record Belongs to More Than One Person

Return to that email from Google: “You keep 100% of your IP.” For a solo developer who wrote every line of an app, that may be close to true. For almost everyone else, it is a simplification that the new market quietly depends on. A codebase with a real history is a crowd of authors, a web of contracts, a store of other companies' secrets and a diary of working lives. It can be sold as a single asset only by ignoring most of what makes it valuable.

The AI industry has discovered that the most useful training data is not polished output but the visible process of people working things out together. That process was never created with a buyer in mind. If the market is allowed to treat possession as ownership, and a git log as proof of anything, it will reward forgers, launderers and insiders. At least one buyer has already recognised an offer that looked too good to be legitimate. A market cannot rely on its buyers happening to be careful.


References and Sources

  1. Koebler, Jason. “Google Is Quietly Buying Code From Play Store Developers to Train AI.” 404 Media, 2 June 2026. https://404media.co/google-is-quietly-buying-code-from-play-store-developers-to-train-ai/
  2. King, Matthew. “AI labs are buying data from dead startups to train their models.” MIT Technology Review, 13 October 2026. https://www.technologyreview.com/2026/10/13/1145755/ai-labs-buying-data-from-dead-startups-to-train-models/
  3. Perrigo, Billy. “Google's $10 Million Bid for Spirit Airlines' Data Reveals AI's Next Frontier.” TIME, 25 August 2026. https://time.com/article/2026/08/25/google-spirit-airlines-ai-data-RL/
  4. Chapter11Cases. “Spirit Airlines Case Update: The Data Sale Slips to November as Spirit Moves to Unwind the HFS Aircraft Deal.” 14 October 2026. https://chapter11cases.com/blogs/news/spirit-airlines-case-update-the-data-sale-slips-to-november-as-spirit-moves-to-unwind-the-hfs-aircraft-deal
  5. ComplexDiscovery. “Lawmakers press Google and Spirit on employee data before a hearing on a $10 million AI training data sale.” 9 October 2026. https://complexdiscovery.com/lawmakers-press-google-and-spirit-on-employee-data-before-a-hearing-on-a-10-million-ai-training-data-sale/
  6. Adebayo, Kolawole Samuel. “Springshot says Google's $10m Spirit deal could include its trade secrets.” The Next Web, 18 September 2026. https://thenextweb.com/news/springshot-objection-spirit-airlines-data-google
  7. Jaen, Regyl. “Companies Are Selling Employees' Private Slack Messages and Emails to Train AI, Often Without Workers' Knowledge.” IBTimes UK, 20 October 2026 (reporting remarks given to Business Insider). https://www.ibtimes.co.uk/companies-sell-workplace-data-ai-firms-1826648
  8. Holland, Martin. “Lucrative internal data: AI firms buy internal data from liquidated companies.” heise online, 17 April 2026 (summarising Forbes reporting of 16 April 2026). https://heise.de/-11262202
  9. Turing. “Can an AI Learn From a Company That No Longer Exists?” AGI Advance newsletter, 24 December 2025. https://www.turing.com/blog/agi-advance-newsletter-44
  10. Human Union Data, Inc. “Best Platforms for Selling Your Codebase in 2026.” HUD, 24 June 2026 (broker marketing material). https://www.hud.ai/guides/best-platforms-selling-codebase
  11. Villalobos, Pablo; Ho, Anson; Sevilla, Jaime; Besiroglu, Tamay; Heim, Lennart; Hobbhahn, Marius. “Will we run out of data? Limits of LLM scaling based on human-generated data.” Epoch AI, 2024. https://epoch.ai/blog/will-we-run-out-of-data-limits-of-llm-scaling-based-on-human-generated-data
  12. Shumailov, Ilia; Shumaylov, Zakhar; Zhao, Yiren; Papernot, Nicolas; Anderson, Ross; Gal, Yarin. “AI models collapse when trained on recursively generated data.” Nature, 631, 755-759, 24 July 2024. DOI: 10.1038/s41586-024-07566-y.
  13. UK Parliament. Copyright, Designs and Patents Act 1988, section 11. https://www.legislation.gov.uk/ukpga/1988/48/section/11
  14. United States Code. 17 U.S.C. section 101, definition of “work made for hire.” Legal Information Institute, Cornell Law School. https://www.law.cornell.edu/uscode/text/17/101
  15. Hamilton, Corey. “Software governance in the AI era: Key findings from the 2026 OSSRA report.” Black Duck, 25 February 2026. https://www.blackduck.com/blog/open-source-trends-ossra-report.html
  16. Linux Foundation. Developer Certificate of Origin, Version 1.1. https://developercertificate.org/
  17. European Parliament and Council. Directive (EU) 2016/943 on the protection of undisclosed know-how and business information (trade secrets), Article 4. https://www.legislation.gov.uk/eudr/2016/943/article/4
  18. Jurist. “Judge approves record $1.5 billion AI copyright settlement involving Anthropic.” July 2026. https://www.jurist.org/news/2026/07/judge-approves-record-1-5-billion-settlement-involving-anthropic/
  19. European Parliament and Council. Regulation (EU) 2016/679 (General Data Protection Regulation), Article 4. https://gdpr-info.eu/art-4-gdpr/
  20. Egelman, Carolyn D.; Murphy-Hill, Emerson; Kammer, Elizabeth; Hodges, Margaret Morrow; Green, Collin; Jaspan, Ciera; Lin, James. “Predicting Developers' Negative Feelings about Code Review.” Proceedings of the 42nd International Conference on Software Engineering (ICSE 2020), 174-185. DOI: 10.1145/3377811.3380414. https://research.google/pubs/predicting-developers-negative-feelings-about-code-review/
  21. European Data Protection Board. Opinion 28/2024 on certain data protection aspects related to the processing of personal data in the context of AI models, adopted December 2024. Summary: CMS. https://cms.law/en/int/legal-updates/edpb-opinion-28-2024-key-takeaways-on-processing-personal-data-in-the-context-of-ai-models
  22. GitGuardian. “The State of Secrets Sprawl 2026.” 17 March 2026. https://blog.gitguardian.com/the-state-of-secrets-sprawl-2026/
  23. Carlini, Nicholas; Tramèr, Florian; Wallace, Eric; Jagielski, Matthew; Herbert-Voss, Ariel; Lee, Katherine; Roberts, Adam; Brown, Tom; Song, Dawn; Erlingsson, Úlfar; Oprea, Alina; Raffel, Colin. “Extracting Training Data from Large Language Models.” 30th USENIX Security Symposium, 2021, 2633-2650. https://www.usenix.org/conference/usenixsecurity21/presentation/carlini-extracting
  24. Longpre, Shayne, et al. “A large-scale audit of dataset licensing and attribution in AI.” Nature Machine Intelligence, 6, 975-987, 2024. MIT News coverage: https://www.media.mit.edu/articles/study-transparency-is-often-lacking-in-datasets-used-to-train-large-language-models/
  25. Help Net Security. “Cross-industry standards for data provenance in AI” (interview with the Data & Trust Alliance). 22 July 2024. https://www.helpnetsecurity.com/2024/07/22/saira-jesani-data-trust-alliance-data-provenance-standards/
  26. Git project. “git-commit Documentation.” https://git-scm.com/docs/git-commit
  27. Sigstore. “Gitsign” documentation. https://docs.sigstore.dev/cosign/signing/gitsign
  28. SLSA (Supply-chain Levels for Software Artifacts), Open Source Security Foundation. https://slsa.dev/
  29. Cybersecurity and Infrastructure Security Agency. “Software Bill of Materials (SBOM).” https://www.cisa.gov/sbom
  30. Coalition for Content Provenance and Authenticity. “About C2PA.” https://c2pa.org/about/
  31. European Commission. “Template for General-Purpose AI model providers to summarise their training content” (FAQ). https://digital-strategy.ec.europa.eu/en/faqs/template-general-purpose-ai-model-providers-summarise-their-training-content
  32. He, Hao; Yang, Haoqin; Burckhardt, Philipp; Kapravelos, Alexandros; Vasilescu, Bogdan; Kästner, Christian. “4.5 Million (Suspected) Fake Stars in GitHub: A Growing Spiral of Popularity Contests, Scams, and Malware.” arXiv preprint 2412.13459, December 2024. https://arxiv.org/abs/2412.13459
  33. CBS News Bay Area. “Former Google engineer Linwei Ding found guilty of stealing AI secrets for Chinese firms.” 30 January 2026. https://www.cbsnews.com/sanfrancisco/news/former-google-engineer-linwei-ding-found-guilty-stealing-ai-secrets-chinese-firms/
  34. GitHub. “Updates to our Privacy Statement and Terms of Service: How we use your data.” GitHub Changelog, 25 March 2026. https://github.blog/changelog/2026-03-25-updates-to-our-privacy-statement-and-terms-of-service-how-we-use-your-data/
  35. Maharishi, Meghna. “Spirit's $10 Million Data Sale to Google Clears Hurdle as Unions Win Privacy Protections.” Skift, 10 November 2026. https://skift.com/2026/11/10/spirits-10-million-dollar-data-sale-clears-hurdle-as-unions-win-privacy-protections

Tim Green

Tim Green UK-based Systems Theorist & Independent Technology Writer

Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.

His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.

ORCID: 0009-0002-0156-9795 Email: tim@smarterarticles.co.uk

Listen to the free weekly SmarterArticles Podcast

Support What We Do

 
Read more... Discuss...

from The disconnect blog

I’ve been accused twice this year of being too “black and white” with my thinking. The last time was while discussing my stance on being a non-voter. I was attempting to convince some people of the idea that it is better to not consent to the political system by voting especially if voting for the “lesser of two evils” or even voting third party. You can read my last post here if you want more details on some of my viewpoints on all of that.

Well since then I’ve been thinking a little bit more on the idea of black and white thinking. In my view I have a wide spectrum of ideas in my thinking. I don’t express them all because I enjoy talking about the extremes which I believe is where many solid truths are found. I used to dwell on the gray thinking for about two decades of my life. In hindsight that is fairly boring to me now. It seems to be avoiding convictions and beliefs sitting around in the gray zone. Now I feel like I’m full of a wide range of color, not just black and white. Black and white, red and yellow, and more.

Perhaps it’s not a problem at all to have some black and white thinking. I think we all do and it is likely unavoidable. Where are your convictions? Many of those things are somewhat binary. The people I was discussing the political voting system were fairly black and white with their convictions that it is an overall benefit for all of us to go out and vote. My arguments against it looked like black and their positive beliefs for voting looked like white to them. In my view it was the opposite, they are upholding corrupt systems that subjugate us all with violence and coercion – which would be black in my view. I support disengaging from that and laboring on alternative voluntary systems and if you believe in the Messiah, have Him as your King. If not at least promote good and non-violent things in place of violent extremists, aka governments.

As I’ve been lightly thinking of this idea, I think anyone with strong beliefs and convictions would have some black and white thinking in their mind, for example those who believe climate change is the biggest threat to mankind versus those who believe climate change is a hoax agenda created by the round table groups to manipulate and control mankind. There are many in the gray zone with climate change, but many have solid convictions on it. Those who believed that the COVID-19 thing was a legitimate pandemic and that those who didn’t “believe in the science” were threatening us all versus those who did not is another example. There are countless examples of this. Belief in the government (and political parties) and belief in some sect of religion are some of the most intense black and white thinking areas but most people have some black and white thinking. Playstation vs Xbox, Apple vs Microsoft or Google, Ford vs Chevy, Israel vs Gaza. Lots of it is just opinions that don’t matter much, but some are life and death type of situations.

I took a long break from politics and religion and it was very helpful. I had to deprogram my mind and clear it up from the constructs that were programmed into me from birth. I’m sure some of that remains but as I’ve come back at reconstructing my reality with a somewhat blank slate it has been pretty amazing. Reading scriptures without holding onto what I was told to think about it has given me a very different perspective on it all. Now it looks like a bunch of people showing what not to do with God patiently giving advice on a better way while watching everyone reject that. Politics are just comedy to me now, I don’t see how people can keep being pulled into whatever party they latch onto. All these systems of control are corrupt; organized government and organized religion are pretty repulsive overall – full of error. And the good, honest, sincere people trying to live according to truth are scattered and divided. Divide and conquer, the elitists are well practiced at this and seem to be winning.

Don’t really have a major point here. Just expressing some thoughts. I’d suggest we all try our best to stay open minded. Yet as you come to find amazing information that you feel and understand through your entire being – stand up for those principles and convictions. But please don’t force them on others with coercion and violence. Realize that is what governments do. So if you press your views through the government system it will more likely than not become a matter forced on everyone.

 
Read more...

Join the writers on Write.as.

Start writing or create a blog