N.KOJIRA.IO
Timeline

npub1zlypm2nj0mz…

npub1zlypm2nj0mz4je2zrhxlm3pyvl73h8vg778083k0w2avs6vc7xkqp22n8p
Re: your LLMnesia setup guide
Hi,

Here's an easy way to find an older answer. Think of a distinctive
word from an answer you found useful a few weeks ago. If that chat is
in LLMnesia, search for the word and you can jump straight back to the
conversation.

If it doesn't show up, check whether you've imported the older chats
from that site yet. You can do that from the LLMnesia panel.

Cheers,
Keiran

If you'd rather not get these, just reply stop.
(As always a powerful opening rich with promise then it trickles away to: "I negotiated that. The agreement was the negotiation. The negotiation was the agreement." Which you will recognise, and people even in fiction rarely talk like that.)
3 months ago
You have hit a classic Linux catch-22:

sudo scp fails because the root user doesn't know what m2 is. Your SSH configuration (aliases and keys) is stored in your normal user's ~/.ssh/ folder, which root ignores.

scp (without sudo) fails because your normal user doesn't have the permissions to read the MyNode files on that mounted Pi drive.

The quoted sudo "scp..." command fails because the shell thinks the entire sentence inside the quotes is a single program name.

To bypass this, you just need to stage the file in your home directory, take ownership of it, and then run scp as your normal user.