Boyd Stephen Smith Jr.

Fsck. Using this laptop with netbsd is painful. Multiple keyboard smashes and screams of frustration this morning.

Anyway, has anyone got #nvm working on #netbsd ? It seems to be installed. But, when I attempt to pull down the latest stable node.js with nvm install stable, it fails:

WARNING: C++ compiler (CXX=g++, 12.5.0) too old, need g++ 13.2.0 or clang++ 19.1.0 WARNING: cargo not found! Support for Temporal will be disabled. WARNING: rustc not found! Support for Temporal will be disabled. INFO: Using floating patch "tools/icu/patches/78/source/i18n/dtfmysym.cpp" from "tools/icu" WARNING: warnings were emitted in the configure phase INFO: configure completed successfully make: /home/bss/.nvm/.cache/src/node-v26.8.2/files/Makefile:15: Unknown modifier ":upper" while evaluating variable "shell uname -s | tr '[" with value "" make: /home/bss/.nvm/.cache/src/node-v26.8.2/files/Makefile:16: warning: Invalid character " " in variable name "findstring os/390,STYPE" ... and then pages and pages of follow-on errors.

(Excuse any typos, due to the lack of extra mouse buttons I'm finding it impossible to get text from xterm into this textbox of firefox140.)

@jornane@mastodon.bsd.cafe Have any tips? I'm new to NetBSD, so even basic stuff would be appreciated. So far I've just been installing binary packages using pkgin, and user-level installs of a few things from source.

When using the wip package from pkg_src should just directly make install ( https://www.netbsd.org/docs/pkgsrc/using.html#how-to-build-and-install ) or build a binary package and use pkg_add ( https://www.netbsd.org/docs/pkgsrc/binary.html#building-a-single-binary-package ) or something else (stow?).

5km in 47:09 #running

I think something is wrong with my gait/stride/pace. Calves hurting at lot more than they should.

@Dio9sys@haunted.computer I was running some shadow IT at one of my previous jobs, and I would tease people that got their sudo password wrong (or tried but didn't have access) by mentioning to them that "I am the person to which sudo incidents are reported."

I was using logcheck, so I would often get an email immediately.

Some people would sudo on the server because they thought they were sudoing on their laptop -- that was the normal reason someone without access would "try".

Look How They Massacred My Boy

https://media3.giphy.com/media/v1.Y2lkPTc5MGI3NjExdmNpbW9nYmEwMHplcXYxYmtpdXpvZGtwcHplbG9meDdncGI0aWJwbyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/l4FGGafcOHmrlQxG0/giphy.gif

@franklinlopez@kolektiva.social

So what’s the plan if Signal gets blocked, banned, or bullied out? Delta Chat?

I've heard good things about Delta Chat, but my second E2E messenger is Wire.

The only non-Signal messenger EFF endorses is WhatsApp: https://ssd.eff.org/module-categories/tool-guides

Best of luck putting together a plan.

@yoasif@mastodon.social @neriman@wikis.world

The problem with assigning copyrights to LLMs

I never said the LLMs should hold the copyright. I think the human operator can hold the copyright to the output, though the work would still be a derivative of any and all of the training data, so their terms would significantly affect what the human (or at least sentient) copyright holder can do.

@yoasif@mastodon.social @neriman@wikis.world

the idea that works - freely contributed, would be reshaped into new works that violated or were not protected by the license by which the contributions were made is anathema

I agree, which is why the output of LLMs (or any future generative "AI" technologies) not only must be suitable for copyright protection, but must also be held to be derivative works of any and all of the training materials.

This would mean those outputs are only distributable if you can satisfy terms for each and every training work.

If all your training inputs have terms that are compatible with CC-SA (or AGPLv3 or whatever), then you can ethically release the output as CC-SA (or AGPLv3 or whatever).

I believe the USCO currently incorrectly classifies LLM outputs. There's also some contradictory federal adjudications, some of which I disagree with.

https://en.wikipedia.org/wiki/Apertus_(LLM) is one attempt at an LLM that is Free Software, all the source code, including but not limited to all the training data, is available under freedom-preserving terms.

I know people that are working on a Free Software code assistant as well.

If LLM outputs are uncopyrightable (as you say the current stance of the USCO), that breaks the derivative-works-chain of copyright. Copylefts depend on that just as much, so they are similarly broken.