Gnome Console seems to be intended for people who don't use terminals. I quickly install GNOME terminal for real use.

I was using GNOME Console in a postmarketOS install in my Chromebook. The fact that it is lightweight compared to say Ghostty (my main terminal everywhere else) made a difference in performance for such a constraint device.

And I didn't really miss any features to be honest, it has the basic that you expect (things like tabs). It is less customizable than other options, but the defaults were good enough for me.

No, there is no reason to believe it can be enforced.

In the US, training is considered fair use at this time, and thus DOES NOT require a license at all. That might change, but I doubt it.

I would say "limited and unreliable access". What it says is the cause might be the cause, but it's not on any way certain.

I think Inform 7 is pretty cool. I suggest checking in to that as well.

Inform 7 source code, at first glance, looks like plain English. It makes you start to wonder whether Inform 7 is actually an LLM and not a compiler. Then as you look at more code, you quickly start to see the structure of the language, and realize that it is indeed a programming language merely structured to look like English at first glance. But it's very cool that you can do things like this (example from the Inform 7 documentation):

    Definition: a room is neighboring if the number of moves from it to the location is 1.
    Every turn:
        if a random chance of 1 in 2 succeeds:
                    let current location be the location of the lurking critter;
                    let next location be a random room which is adjacent to the current location;
                    if the lurking critter is visible:
                        say "The critter [one of]slouches[or]slithers[or]shambles[or]lurches[at random] away.";
                    move the lurking critter to next location;
                    if the lurking critter is visible:
                            say "A critter [one of]oozes[or]staggers[or]ambles[or]creeps[at random] into the room.";
        [Whether or not the critter has moved, we need to adjust the sword-glow, because the player may have moved.]
        if the lurking critter is in the location:
                  adjust sword-glow to glowing brightly;
        otherwise if the lurking critter is in a neighboring room:
                  adjust sword-glow to glowing faintly;
        otherwise:
                  adjust sword-glow to glowless.

This snippet omits the definition of "the lurking critter" (a standard NPC) and the sword (a standard object with a custom defined method called "adjust sword-glow to"), but it should give you a good idea of what Inform 7 source code looks like. (Inform 6 looked much more like a traditional programming language).

> [Whether or not the critter has moved, we need to adjust the sword-glow, because the player may have moved.]

That must be a comment, right?

In that case: "The critter [one of]slouches[or]slithers[or]shambles[or]lurches[at random] away.";

[one of] [or] [at random] are also comments?

In code, square brackets indicate comments. But inside a string literal they indicate variable interpolation or other commands.

No.

And training is currently considered fair use in the US (some court cases pending).

I am not a lawyer, tho.

I suspect this is really a surveillance bill, but we won't know until the text is revealed.

Agreed. The whole topic is a Trojan horse for surveillance companies to siphon off data. We need to start asking which politicians are pushing this and who’s pushing them to do it. They’re either doing it for money or being blackmailed into it by the existing surveillance apparatus.

I suggest this vocal performance: https://youtube.com/watch?v=GggK9SjJpuQ

I prefer the term "assistant". It can do some tasks, but today's AI often needs human guidance for good results.

I also made a list of tips on writing code with AI, with a special focus on security. Others may find the tips useful. Here they are: https://openssf.org/blog/2026/01/05/ai-software-development-...

This has many similarities to the Heartbleed vulnerability: it involves trusting lengths from an attacker, leading to unauthorized revelation of data.