It is time for the mainland to come back into the fold.

I agree the mainland should be allowed to maintain some amount of self rule during the transition.

I vote for xX-[X]-Xx

Alas, this being the darkest timeline, we'll probably end up with X Social.

You can list every man page installed on your system with man -k . , or just apropos .
But that's a lot of random junk. If you only want "executable programs or shell commands", only grab man pages in section 1 with a apropos -s 1 .

You can get the path of a man page by using whereis -m pwd (replace pwd with your page name.)

You can convert a man page to html with man2html (may require apt get man2html or whatever equivalent applies to your distro.)
That tool adds a couple of useless lines at the beginning of each file, so we'll want to pipe its output into a | tail +3 to get rid of them.

Combine all of these together in a questionable incantation, and you might end up with something like this:

mkdir -p tmp ; cd tmp
apropos -s 1 . | cut -d' ' -f1 | while read page; do whereis -m "$page" ; done | while read id path rest; do man2html "$path" | tail +3 > "${id::-1}.html"; done

List every command in section 1, extract the id only. For each one, get a file path. For each id and file path (ignore the rest), convert to html and save it as a file named $id.html.

It might take a little while to run, but then you could run firefox . or whatever and browse the resulting mess.

Or keep tweaking all of this until it's just right for you.

Instead of simply blurring them, it'd be technically possible to feed their images through a stable diffusion prompt, like "humanoid lizards" or "frantic lemmings"..
Also, I understand that a large language model could be made to rewrite articles about them with a matching prompt.

That would be very silly, of course.

Honestly, it depends on your job.
Some jobs will fire you for taking too long in the restroom.
Those are not good jobs.

At other jobs, nobody will flinch if you send a quick note saying you gotta leave now for personal reasons and just take off.

There are stories after stories of students getting shafted by gullible teachers who took one of those AI detectors at face value and decided their students were cheating based solely on their output.

And somehow those teachers are not getting the message that they're relying on snake oil to harm their students. They certainly won't see this post, and there just isn't enough mainstream pushback explaining that AI detectors are entirely inappropriate tools to decide whether to punish a student.

Running strange software grabbed from unknown sources will never not be a risky proposition.

Uploading the .exe you just grabbed to virustotal and getting the all clear can indicate two very different things: It's either actually safe, or it hasn't yet been detected as malware.

You should expect that malware writers had already uploaded some variant of their work to virustotal before seeding it to ensure maximum impact.
Getting happy results from virustotal could simply mean the malware author simply tweaked their work until they saw those same results.

Notice I said "yet" above. Malware tends to eventually get flagged as such, even when it has a headstart of not being recognized correctly.
You can use that to somewhat lower the odds of getting infected, by waiting. Don't grab the latest crack that just dropped for the hottest game or whatever.
Wait a few weeks. Let other people get infected first and have antiviruses DBs recognize a new malware. Then maybe give it a shot.

And of course, the notion that keygens will often be flagged as "bad" software by unhelpful antivirus just further muddies the waters since it teaches you to ignore or altogether disable your antivirus in one of the most risky situation you'll put yourself into.

Let's be clear: There's nothing safe about any of this, and if you do this on a computer that has access to anything you wouldn't want to lose, you are living dangerously indeed.

Several times now, I've sent people I knew links to articles that looked perfectly fine to me, but turned out to be unusable ad-ridden garbage to them.

Since then, I try to remember to disable uBlock Origin to check what they'll actually see before I share any links.

That's odd. Their own sidebar points to a Want to reform work? Start or join a union where you work. post, so your ban was perhaps not tied to your use of the U-word.

On that note, maybe it would have been more constructive to post your actual question here rather than a "I got banned" post.

That sounds like an improbable attempt to leverage the notion that minors can't enter into a legally binding contract into a loophole to get anything for free by simply having your kid order it.

I'll note that there are plenty of models out there that aren't LLMs and that are also being trained on large datasets gathered from public sources.

Image generation models, music generation models, etc.
Heck, it doesn't even need to be about generation. Music recognition and image recognition models can also be trained on the same sort of datasets, and arguably come with similar IP right questions.

It's definitely a broader topic than just LLMs, and attempting to enumerate exhaustively the flavors of AIs/models/whatever that should be part of this discussion is fairly futile given the fast evolving nature of the field.

One of my guilty pleasures is to rewrite trivial functions to be statements free.

Since I'd be too self-conscious to put those in a PR, I keep those mostly to myself.

For example, here's an XPath wrapper:

const $$$ = (q,d=document,x=d.evaluate(q,d),a=[],n=x.iterateNext()) => n ? (a.push(n), $$$(q,d,x,a)) : a;

Which you can use as $$$("//*[contains(@class, 'post-')]//*[text()[contains(.,'fedilink')]]/../../..") to get an array of matching nodes.

If I was paid to write this, it'd probably look like this instead:

function queryAllXPath(query, doc = document) {
    const array = [];
    const result = doc.evaluate(query, doc);
    let node= result.iterateNext();
    while (node) {
        array.push(node);
        n = result.iterateNext();
    }
    return array;
}

Seriously boring stuff.

Anyway, since var/let/const are statements, I have no choice but to use optional parameters instead, and since loops are statements as well, recursion saves the day.

Would my quality of life improve if the lambda body could be written as => if n then a.push(n), $$$(q,d,x,a) else a ? Obviously, yes.