People love to bitch and moan about nostr websockets but frankly I think websockets are way better than HTTP and make a lot of sense for most applications.

SwiftNIO is such a fantastic library

I used to think that burning alive was the worst way to go out. Now I realize, the worst way to go out is paying $250,000 to die in this tube over 96 hours with 4 other people at the bottom of the ocean.

As a kid that grew up entirely in Colorado…having visited Casa Bonita multiple times in my childhood (and also a massive South Park fan), I absolutely love this story.

This is ridiculous. The client is NOT a platform for moderation. Ever. Period. Data should always be reliably, faithfully and transparently shown to the user. WITHOUT servers or assistive backends in ANY capacity. Direct client to relay only. The user can make informed decisions about what they see and how they possibly moderate and manage their intake. And the client should enable the user to control that for themselves. Regex patterns, block + mute, maybe even something like OpenAI prompt filters (if the user is willing to provide their own API token ofc) “The code” doesn’t tell you shit about complex problems like this 🧊 View quoted note →

And with this in mind… I’m proud to announce the soft release of nostr-kit! nostr-kit is cross platform, open source "heart” of topaz (which itself is open source). It has been an intense effort to take the best (and learning lessons) of my early topaz builds, and formalizing/repackaging them into a mature library for industrial uses. nostr-kit is designed for both clients and server (relay) applications that span across any platform or architecture that can run Swift. It’s an extremely tight and efficient packaging of the cryptography, concurrency, and networking tools needed for any given nostr implementation. Now, I approach the topaz project with this new library, in hopes that it can add the final layer of polish and performance I was looking to achieve before we open to users.

GitHub

GitHub - tannerdsilva/nostr-kit: the fastest way to do nostr stuff in swift. period.

the fastest way to do nostr stuff in swift. period. - tannerdsilva/nostr-kit

View quoted note →

SwiftUI on the Linux desktop looks EXTREMELY promising. Native gnome with accessible and familiar syntax. It’s possible right now (not speculative), if you’re brave enough to be the first to deploy it (I certainly might be…before end of year). topaz is swift only, but that absolutely does not mean it is Apple only. A thoroughly native Linux desktop client would be huge. It’s very very attainable from a technical perspective. 🤷🏻‍♂️🤔 Still waiting for Swift on Android to catch up….Windows is also hopelessly behind (shocking I know). View quoted note →

I’ve been silent on topaz platform support. The repo exists…I know people view it…and I’m sure people recognize it’s an iOS app. Have no fear, this app is NOT staying in the walled garden. This is simply the start. My bead & butter trade is in writing very high performance C & Swift code for Linux…I’m NEVER reaching for the “Apple Platform” libraries. I’m just here for the language as an open source initiative. On top of iOS being an obvious entry point for a swift project, CakeWallet started as a Swift app so beginning here also gives a nice nod to the brand and the guy supporting my developments here (Vik)

No zaps for topaz! https://t.co/DkXEeQG2mz

Framework laptop preparing to ship 🔥

Building a ton of tooling for nostr. First, I lay the foundation for my work… Introducing QuickJSON, the fastest and easiest way to handle JSON in Swift. It abstracts the excellent C lib yyson into two simple functions (encode and decode), without abstracting away performance. Type-strict languages ftw

GitHub

GitHub - tannerdsilva/QuickJSON: Native Swift Encoding and Decoding from ANSI C library yyjson.

Native Swift Encoding and Decoding from ANSI C library yyjson. - tannerdsilva/QuickJSON

Just discovered clib yyjson. Impressed - will be deeply integrating this into my nostr lib.

As nostr survives and grows, I think NIP-42 will become a requirement. At least, it will be for DM access. Of course, DM’s came before AUTH, but now that both are solidified, it’s kinda crazy that the default configuration for relays is to share all DM metadata openly for all to see.

So apparently Amethyst claims to support NIP-42 but in reality, doesn’t actually support NIP-42 🤣

Charlotte de Whitte. It’ll Do Club - Dallas Texas. Lfg!

Face the fire.

💡nostr based system management and monitoring

the client is straight 🔥

Follows needs to be a dedicated nostr kind. It’s way too easy to nuke a carefully curated follow list with a single accidental event write.

Perez looks pretty screwed lol #f1