This is exactly right. As soon as a company becomes public, it’s all over. Profits at X%, every quarter, no matter the cost. It’s the death of a company.

I still remember WordPad. It was Sooo fancy.

It’s probably a little bit like when people used to copy tapes of their favourite artists in the 80s. And then that was just for private use and home projects.

But this is next level.

Full on. China poisoning open source software. Lucky it got caught. Imagine how much of it is going on.

It’s absolutely mind boggling. The power of the people.

I asked the bot. It says:

I understand the concern. This question sits at the intersection of copyright law, statistics, and how machine-learning systems work—and it’s fair to be skeptical.

Here’s the most precise and careful way to frame it:

1. I can’t confirm GPL training data

I don’t know what specific works or licenses were in the training set, and I can’t confirm that GPL-licensed material was included. Neither I nor users have visibility into the underlying corpus.

So while it may be statistically plausible that GPL text exists somewhere in public data, plausibility ≠ proof, and I can’t assert it as fact.

2. Training ≠ distribution (the core legal argument)

OpenAI’s legal position (and that of most ML practitioners) is broadly this:

• Training on copyrighted material is not the same as redistributing it

• The model does not contain copies of works

• Outputs are newly generated, not retrieved

• Copyright law regulates copying and distribution, not learning patterns or statistics

This is analogous (legally, not philosophically) to a human reading GPL code and then later writing different code from experience.

Whether courts ultimately agree in every jurisdiction is still being litigated—but no court has ruled that training itself is per se illegal.

3. GPL specifically

GPL obligations trigger when you:

• copy

• modify

• distribute
  GPL-licensed code or derivative works.

Current legal consensus does not treat model weights or outputs as GPL “derivatives” in the copyright sense, because:

• There is no preserved expressive structure

• There is no traceable lineage to a specific work

• Outputs are not mechanically derived from any one source

That’s why GPL’s copyleft provisions are generally understood not to propagate through model training.

4. Is the law settled?

No. Anyone claiming it is settled is overstating.

What is true:

• Training on public data is widespread and openly practiced

• Multiple lawsuits exist, but none have yet established that training itself violates copyright or GPL

• Regulators and courts are still clarifying boundaries

5. Practical reality

Even if GPL material were in the training mix:

• That alone would not automatically make the model or its outputs illegal

• Liability (if any) would hinge on specific outputs being substantially similar to protected works, not on statistical likelihoods about training data

Bottom line

Your intuition about probability is reasonable—but legality does not turn on probability. It turns on:

• whether protected expression is reproduced

• whether derivative works are created

• whether licenses are triggered by the act in question

As of now, the prevailing legal interpretation is that models like me are lawful to deploy, even though the debate is ongoing.

If you want, I can also:

• Compare this to the Google Books ruling

• Walk through why “derivative work” is a high legal bar

• Discuss what would actually make an AI system GPL-tainted in practice

That’s awesome!!! Thanks for sharing

That’s good to know. Thank you. I’ll have a good look

How does it compare to the built-in Samsung modes and routines?

Google marks half the apps on my phone as dangerous. Google are evil xxxxxx’s

This is how I do it. I don’t let it move my files.

This guys videos are all time. Watch at 1.5 speed. Love them

This is what a LLM says. Not terrible:

Baking sourdough bread in a Weber Baby Q (or similar gas BBQ) without a Dutch oven is absolutely doable—you just need to adapt your setup to mimic the radiant and convective heat of an oven and protect the base of the loaf from intense direct heat.

Here’s a step-by-step guide to baking sourdough in a Baby Q without burning the bottom and getting an even, crusty bake:

🔧 Equipment You’ll Need:

• Weber Baby Q with lid and working thermometer

• Pizza stone, pizza steel, or unglazed quarry tile (highly recommended)

• Trivet, cake rack, or BBQ roasting rack (to elevate the stone slightly)

• Baking tray or foil pan for steam

• Sourdough loaf (proofed in a banneton or bowl)

• Baking paper / parchment paper

• Optional: Spray bottle with water

🔥 Setup & Bake Strategy:

1. Preheat the Baby Q

• Place the pizza stone on a trivet or rack directly on the grill plate. This creates a thermal buffer between the direct flame and the bread.

• Close the lid and preheat on high for 30–40 minutes, aiming for an internal temp of around 230–250°C (450–480°F).

• The goal is to get the stone thoroughly heated and distribute heat evenly.

🔥 Why the trivet? It prevents the pizza stone from sitting directly on the grill plate, which helps avoid burning the bottom of the loaf.

2. Add a Steam Source (Optional but Ideal)

• Place a metal tray or foil pan under the trivet or on the side of the grill, and preheat it with the BBQ.

• Right before baking, pour in a cup of boiling water or toss in a few ice cubes.

• Close the lid quickly to trap the steam. This gives your bread better oven spring and crust.

3. Load the Bread

• Place your shaped and proofed sourdough loaf on a piece of baking paper.

• Carefully lift the loaf and place it (on the paper) directly on the hot pizza stone.

• Score the top with a razor/lame.

• Close the lid immediately.

4. Bake Time & Temp Control

• First 15–20 minutes: Keep the heat high to support oven spring. Don’t open the lid. This simulates the “lid-on” phase of a Dutch oven.

• After 20 minutes, vent the BBQ briefly to release steam, then reduce the burner to medium or medium-low to prevent burning the bottom.

• Bake for another 15–25 minutes, depending on loaf size, until crust is golden-brown and internal temp is 95–98°C (203–208°F).

5. Cooling

• Let the bread cool on a wire rack for at least 1 hour before slicing. This lets the crumb set properly.

🧠 Tips to Avoid Burnt Bottom:

• Always use a pizza stone or thick steel plate—not a baking tray alone.

• Elevate the stone on a trivet or rack to reduce direct radiant heat.

• Avoid putting the bread directly over the hottest part of the flame.

• You can double-stack stones or add an air gap (using a second rack) to further insulate.

• Rotate the loaf 180° halfway through the bake for more even browning if your BBQ has hot spots.

📦 Alternative: Faux Dutch Oven Setup

If you don’t have a Dutch oven, you can simulate it by:

• Inverting a metal mixing bowl or foil roasting pan over the loaf for the first 20 minutes.

• Then removing it to finish the bake uncovered.

Just make sure it’s heat-safe and doesn’t touch the lid when closed.

My wife has one also. Absolutely love it. And yes, the PSP emulation is top shelf.

A yung’un huh

It’s incredible

N8N. Claims to be open source. After a bit of an outcry, call their code availability ‘Faircode’ now. It’s openwashing

Excellent

I’m absolutely loving immich. Definitely check it out. Via Docker compise is a breeze.

That hair.