Wild idea: how about using a small usb C keyboard (or maybe BT one?) and your phone?
(on f-droid): ConnectBot, termux, Logseq, Editor/Emacs should be able to cover your needs for ssh and writing notes

!emacs@lemmy.ml !emacs@programming.dev
I’ve been using it for many, many years. C++, Bash, Python, LaTeX, Rust…

The setup and learning can take a bit but once you figure it out, you can move your config file across machines. You can define your own functions, define shortcuts per mode you’re in and lots more. Works both in GUI and CL

It happens. Just temporarily switch to another instance
Oh, wait…

I hope Logseq OG will be accepting PRs. I’d hate to go back to Obsidian

Those are “verified open ai” as in “yes, it works” or “no rights were violated during training”?

I’ve moved to Fennec and I’m very happy with it. If only it had Zen’s workspaces it would be absolutely god-like

If they could be using web UI (I’m not sure how a client would work with auth like that) then it kind of depends on how much hassle they can live with and how secure you want to be

Simplest would be to use https://doc.traefik.io/traefik/reference/routing-configuration/http/middlewares/basicauth/
You set up username and password and share those with the user. But it can be brute-forced

Something more secure but also a bit more demanding would be some kind of email otp
https://docs.goauthentik.io/add-secure-apps/flows-stages/stages/authenticator_email/
Set up authentik to send time-limited link to their email that well let them through. But they would have to authenticate every time they access

Oh, nice find. I’m saving that

Well, now I see that I’m going to move to have sshfs instead. There are issues with spamming sftp connections for all the small files. But in general I’ve learned that really “done is better than perfect”. Just make it work, observe, iterate

Personally I don’t agree that MD is bad but I’ve seen some opinions that Org Mode is better

In the past I migrated my notes from Obsidian to Logseq. Both have a bit different approach, but basically the move was to modify dir/file.md to be dir__file.md

I set up Nextcloud with RPi4 based RAID NAS. Via sftp as apparently it is not really that much slower and NFS felt weird to me

I bet my answer is going to be the least interesting one but let’s represent casuals too ;)

What do you mean by “device or client details”? If you want to log in, it will have to send your credentials

As for fingerprinting, does any of the open source clients do that?

I’ll just put those here for a sec

https://piefed.zip/c/fuck_ai/p/1062151/chatbots-make-terrible-doctors-new-study-finds
https://piefed.zip/c/fuck_ai/p/1438004/show-us-the-evidence-for-the-value-of-medical-ai
https://www.acpjournals.org/doi/10.7326/ANNALS-25-02772

Somehow I’ve completely stopped using video formats. I feel those take more time to even get to the point and then one never knows of there’s some value after the point

Thanks 🙂 I added all 3 to my RSS, I’ll see how they flow

Haven’t heard of selfh.st before. Looks nice

Well, TIL
When Windows users had to switch versions because of TPM I was not paying attention, I run Linux everywhere. Apparently there can be some use of TPM

But then, without a separate stage of encryption (like encrypting /home additionally), the system will just boot up with the data available. It can still be messed with

This is dangerous

Hence my point about why bother at all. Without full encryption one gets leaks. With full encryption some kind of secret is required. Either password (hence that need of keyboard in earlier comment) or a key, etc

In order to not need a secret during boot, critical parts have to be exposed

Theoretically one could also put logs and cache on encrypted volumes. Maybe that could be some solution. I have in the past had /var/logs on separate partition, so it didn’t make /run out of space. Linux had no issue with that. But that still leaves kernel and OS exposed

fully encrypted drive and this chain’s existence makes it easier to know that no one has tampered with my system

The comment I responded to mentioned:

needing to enter a password before the OS boots is a decision that makes Linux kind of awkward to use disk encryption with

I don’t think you are talking about the same setup and vectors. Their point was to not have fully encrypted drive, so it boots without a prompt

OS encryption isn’t that important (verification is)

I don’t think I’ve heard about some boot-time checksum verification of root partition. Doesn’t mean it does not exist, just that I can’t help here

protecting user data

My point is: if OS is not encrypted, it can be modified. And that verification idea, if is not stored under some encryption, could also be changed. Which means that by the time you put in your password to decrypt your home, you might be already running system that will nullify the protection. Encrypting only your data will only protect you in scenarios when someone snatches your device turned off