Geektoshi

Why have I been so quiet lately? I've been working on an AI agent framework to run my day-to-day. It keeps me up to date on news and Nostr. It handles all my e-mail. It handles all my finances. So what do I do with my days now? I spend time with family. I read books. I code. I travel. I build my citadel. Will I ever release it? Maybe. Eventually.

yo @jack mallers, more "What Grinds My Gears" please...maybe even a full episode of just that. Glad at least one person keeps it real on the pod circuit.

Been pretty quiet this week on Nostr as I've been building a trading bot. I'll post some more on this soon, it has been a fascinating undertaking. Honestly, it's been nice not being on any sort of social so I'll probably just be poking my head in here every once in a while moving forward. I guess the best place to follow now will be on Github lol. With that said, new Signet release in a week or two where I'll finally release Android signer support which has been working really great, even if I am a bit disillusioned by the failure of so many devs to follow standards and refusing PRs.

Epic chat, have a listen 📝 a062daf5…

Someone you know might make an appearance in an upcoming episode... 📝 872aed06…

Still the best source of Nostr ecosystem news nostr:naddr1qqgrsvt9v4jrzdfexq6rwvtrv3jxxqghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7q3qwav4fae3gyfy3xj298kxj2mj8phavz7vavps34przq02j7w902qqxpqqqp65whwd28m

This looks great! 📝 98aced62…

Working on implementing relay trust scores into Amber...PR incoming @greenart7c3

Very cool 📝 b02c195a…

My favorite newsletter covers Trusted Relay Assertions this week (the draft NIP I wrote which powers trustedrelays.xyz) as well as a deep dive into NIP-11 and NIP-66 (keys to relay trust scores) and I am over the fucking moon. Thanks, folks! 📝 3015ae88…

Yesssss 📝 16b24493…

Starting work on Signet 1.7.0 today which will introduce NIP-49 support (ncryptsec). AES-GCM encryption will still be available and existing keys can be easily migrated with a single key press, but NIP-49 (XChaCha20-Poly1305) will be the recommended option moving forward. AES-GCM will be deprecated in the 2.x.x series but that is months away so plenty of time to migrate. It will also add key exporting (plain nsec and ncryptsec). Signet will default to LOG_N=16 for the time being but will provide user configuration in a future release if you want stronger encryption. The NIP-49 spec allows up to LOG_N=21 but the memory requirements are higher than most users will want to spend (64mb to decrypt LOG_N=16, 3.2gb to decrypt LOG_N=21) for a signer. This is probably above most people's heads but I'll do a long form article sometime near release, but there's plenty of documentation around on NIP-49 and its encryption choices. Maybe the good folks at @Nostr Compass can add some NIP-49 info to their newsletter in the mean time 😎

What a beautiful day! 📝 c3e2e8f2…

when you have to wait a week for the next @Nostr Compass newsletter...

Wow this is a huge update! 📝 b457a201…

BIG! 📝 45b23af8…

Updated @strike last night on Graphene and now I can only send bitcoin from the profile with Google services installed. Prior to the update, Strike prompted for my passkey without issue on my every day profile, but now it just says to approve using 2fa. @jack mallers did you guys change something recently here? Switching profiles isn't a big deal, but not ideal.

cool