Illiterate Domine

There are many ways to setups full disk encryption on Linux, but the most common all involve LUKS. Providing a password at mount (during boot, for a root partition or perhaps later for a “data” volume) is a but more secure and more frequently done, but you can also use things like smart cards (like a Yubikey) or a keyfile (basically a file as the password rather than typed in) to decrypt.

So, to actually answer your question, if you dont want to type passwords and are okay with the security implementations of storing the key with/near the system, putting a keyfile on removable storage that normally stays plugged in but can be removed to secure your disks is a common compromise. Here’s an approachable article about it.

Search terms: “luks”, " keyfile", “evil maid”

The difference, as I understand it, is Beeper hasn’t claimed to not be doing that. Sunbird/Nothing touted E2EE and that was a lie.

Here’s a link to the anchor

I’d be interested in utilization data before and after that change. Anecdotally, I use Signal much less after SMS was removed. With one app, I could opportunistically use Signal, when the other person had it, and send an SMS otherwise. Now I have to decide what kind of message to send before opening an app and learning my options. Most of those quick messages have moved back to SMS for me.

Most self-hosters are probably using dns services through their registrar, but you don’t have to. A registrar with poor api support might still be a good choice, if that was the only negative.

Significant Figures: am I a joke to you?

Well, I’m back and can confirm the sneaky DNS resolver. I have two roku devices and they both were making requests to 8.8.8.8.

Thanks for this post! TIL.

Interesting. I set an adblocking dns via DHCP and, as far as I know, the Roku respects it. Ads are blocked and I can see it failing to delivery telemetry in my dns logs (most persistent thing on the network).

I set a rule to catch outside dns to see if anything, the roku included, has been misbehaving.

I do and it works great! I mostly did this to limit the blast radius of breaches, but aliases also provide an easy way to send those kinds of things to both me and my spouse.

Not extensively, the keyboard is at work right now, but I’ve fired up a few things to try it out. It’s a well-built mechanical keyboard and performs like you’d expect in that regard. Ortholinear key placement takes a bit of getting used to, but it doesn’t take long to build that new muscle memory. By the time you’re typing comfortably on it, gaming would likely be fine.

I have an Ergodox EZ from ZSA and have been really impressed with both the keyboard and the company. I got mine with Silent Reds but later swapped out for some clickier Zilent switches. Switches are easy to swap, so you have a lot of options there.

When I got mine, there was an issue with it losing connection (I think the USB port solders had broken) and ZSA support was really easy to work with.

If you have a phone number on the account, you can do an SMS reset. If not, I guess it’s “open a ticket with a throwaway” time.

Lemmy, itself, more or less has no rules, but individual instances do and links may violate some of them. More importantly though, publicly linking directories like that can be a good way for them to catch the attention of someone that would want to shut them down.

Edit: I accidentally a word

Little clusters of nucs has become a really common way to run small Kubernetes clusters at home. I recently rebuilt mine (still using a bulky, power hungry box like you’re tossing) and have been very happy with it. Everything is really stable, containers that misbehave are automatically destroyed and replaced, and updates are breeze because everything lives in code/git.

“Know your customer”. Financial institutions, in the US at least, have to verify their customers’ identities before providing services.

Had me in the first… third.