qyckudnefDi5

Do you have a dedicated git repo for your dnscontrol config and use github actions to run dnscontrol when you push?

I've been thinking about doing this for my personal domains, but not sure if it's a good idea

I'm curious for everyone who upgraded from a previous generation, what did you do with your old pair? AFAIK Apple doesn't do AirPods trade-in.

The noteworthy thing about this wallet is that it uses the TROPIC01 secure element[1]. The first open verifiable secure element.

It will be interesting to see how it compares to the Keycard Shell[2] a fully open-source wallet with swappable smart cards using the same secure element as found in credit cards etc.

[1]: https://tropicsquare.com/tropic01

[2]: https://keycard.tech/

Agreed! No one asked for liquid ass!

Anyone wanna share their email strategy? I'm thinking of going for the following but I'm still undecided:

1. 1 custom domain (<simple-word-or-two>.com): this will be used for friends, family and any online accounts that know me IRL.

Use Fastmail masked addresses with my custom domain where it makes sense like an online account for amazon.

2. 1 custom domain (<online-nickname>.xyz): this will be used for a blog, professional IRL interviews, correspondence, github.

Use Fastmail masked addresses with my custom domain where it makes sense.

3. Masked emails using fastmail.com: for online accounts that are ephemeral, random newsletter signups etc. Don't want to associate any of my custom domains or IRL identity. Don't care if these are portable.

My main goals are:

- Separate my online identity/alias used for my blog (2) from gov entities, banks etc (1).

- for more anonymity/privacy use the fastmail.com domain with masked addresses to blend in with others on this domain.

I'd love feedback and to read what you do if you want to share :)

Have you tried any of the splitkb keyboards? If so, how do they compare to the kinesis adv 2?

Top tier comment!

I'm curious if you make your home directory immutable, where do you store your files like pdfs etc?

For point 1 I recall the creator of Age, Filippo Valsorda suggesting something similar:

>The .age-recipients files also include the public key for an offline disaster recovery key. I generated the key with age-keygen, encrypted it with age -p, printed the ciphertext as a QR code, and wrote the random passphrase in pen. This is a bit convoluted, but I don’t trust printers. All this was done in a tmpfs, so nothing reached storage. Only had to do this once, and have been using that key as the anchor for all my disaster recovery data. https://words.filippo.io/dispatches/passage/

You don't need security keys to enable ADP. You need to setup a Recovery Contact or create a Recovery Key.

This guy grids!

Looks like FiloSottile may have switched from passage to 1Password:

https://bsky.app/profile/filippo.abyssdomain.expert/post/3l5...

Would be interesting to get more context why move from storing passwords locally to an online service.

I like Wipr. Simpler design IMHO.

Have you considered writing passage in Go to integrate age and age-plugin-yubikey as a single binary to make it more convenient to setup and use?

"Better backup" aside, as I understand that I'd miss out on deduplication and all the other things backup software can do like keeping track of what it has backed up etc.

"Better encryption": Can you explain why age's encryption isn't sufficient if it's recommended for encrypting files? Really want to understand how it's recommended for encrypting and sharing a file over an untrusted channel like email, but not recommended to encrypt a file and upload it to an untrusted server.

No deduplication is a tradeoff I'm willing to make for simplicity and less things that can go wrong :)

I know there are specialized backup tools like restic or borg, but I like to keep things simple.

Is using age like this to encrypt my files before uploading them to untrusted cloud storage not ok?

tar > age > cloud

Some comments mention signing with minisign. Should I be doing that like this:

tar > age > minisign > cloud