I maintain keys for my email addresses.. but like most in this thread i almost never receive encrypted emails.. other than the BTC exchange i use that sends automated mail encrypted.

@movq@www.uninformativ.de keys.openpgp.org is a descent key server. They only publish a key the at has a valid email.

@lyse@lyse.isobeef.org
Bottomline, twtxt is a poor’s man email system. 🤣

Is it me, or Gmail’s web interface is going down the drain? Using Safari—my default browser—often takes two, or three clicks to open an email. If it weren’t because its search is amazing, I would never visit its web interface.

The features that macOS Monterey will bring, albeit minor, will made for a better “quality of living”. I am looking forward to Notes, and the iCloud+ integration (Private Relay, Hide My Email). It also bring macOS cohesively close to iOS. My work 2015 iMac and M1 Mini will get it, so looking forward to it!

@prologic@twtxt.net I know, because fork makes it 100% sure to know who is replying to whom. Just like email’s in-reply-to does (plus the message-id).

@prologic@twtxt.net What if the reply does what fork does, for any replies to the top post, but not the top post itself? You know, like email does. Other than to reply to the top post (for which I use reply), I don’t use reply but fork, to reply to posts underneath because it is the logical thing to do.

@movq@www.uninformativ.de But it makes sense, right? I spend way too much time trying to figure out who replied to whom. I treat twts replies as emails, pretty much.

I wonder how can I set, on Mutt, a shorter subject (elipsed) on the status bar, while reading a email (or a twt).

Based on spam logs, I am (again) considering banning a bunch of TLDs at the server level. Has anyone ever gotten legitimate email from a .work, .casa, or .today domain, for example?

Ah, no; and there we have a good example of finger’s poor discoverability! It matches my email address, though: echo a.9srv.net | sed ’s/./@/’

@prologic@twtxt.net Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own.

it takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>

@prologic@twtxt.net huh.. true.. the email is md5/sha256 before storing.. if twtxt acted as provider you would store that hash and point the SRV record to the pod. .. to act as a client it would need to store the hash and the server that hosts the image.