I’m fairly convinced we need highly opinionated AI agents for good UX

Have any journalists checked their signal invites for the alpha?

With the humans

Classic shirt

Are you running Sovereign Engineering next year? Wife heard me talking about it as a bucket list thing to do on a podcast and now i need to make a case for it 😉

The real 58k gang

If it’s “critical market infrastructure” it’s not “market infrastructure”

This is more of the care of data that just doesn’t need to be public.

Mongo By Relays! It's cool that Nostr apps can be thin clients using Nostr as a free backend 😉 Sometimes though I just want a db to store some data that doesn't live forever on public relays where a boring offline DB would be sweet. Quick example project to implement NostrMQ as a simple access layer for MongoDB requests. -> No hosting, no api layer ephemeral keys for misdirection and encrypted responses. - https://github.com/humansinstitute/nostrMQ/blob/main/docs/mongobyrelay.md - https://github.com/humansinstitute/nostrMQ/blob/main/examples/mongo-pilot-client.js

Learn to build. Don’t learn to syntax

Talk about it every week here :) https://fountain.fm/show/5c1jIyQLUHKkpS1r0ssb

Thank you 🙏

👀 https://fountain.fm/show/5c1jIyQLUHKkpS1r0ssb

NostrMQ - Composable Applications via Nostr Remote RPC Most applications force you into all-or-nothing trust relationships. You either trust a provider with everything, or you self-host. This limits our design space and options we have to deliver NostrMQ uses Nostr like a public message queue to decompose apps into separate components, each run by one or more groups, and links them together through remote RPC. Each building block can have the trust model that best fits the use case. e.g. let someone else run the client, LLMs etc but keep the signing logic on an isolated device in your house :) https://github.com/humansinstitute/nostrMQ Why Use It? Don't worry, you don't have to :) The philosophy and ideas behind it are: 1. User composable apps - Users can choose and swap out components of apps as required. No more "take it or leave it" software with tightly coupled trust models. 2. Sharing the load - Complex systems can be hard to self-host. This lets us share the complexity across both self-hosting and service providers - why not both! 3. Risk sharing - Running Freedom Tech often comes with risk for both server runners and users. The idea is to open up the design space for how we design and share these risks and responsibilities. and introduce more opportunity for.... 4. Regulatory arbitrage - Regulation is heavily jurisdiction dependent and risk differs depending on who runs what. This allows you to only run the aspects that are fine in your jurisdiction, then allow users or other service providers to fill in the gaps. Freedom Technology Principles For dissidents in authoritarian societies or those dealing with corruption: - Operational Security: Keep identity management local while outsourcing heavy computation - Plausible Deniability: "I just run an encrypted database, i dont process anything", "I'm only a filesystem" , "I only sign messages in a secure enclave"... - Resilience: If one component gets compromised, the others keep running and we can hotswap providers - Distributed Risk: No single person carries the full legal/physical risk of the entire system "NostrMQ lets you build applications like LEGO blocks - choose the best provider for each piece while keeping full control of your identity and data." ---- Shoutout to - who's latest Option Plus podcast convinced me to just push this out today before it's good 😉

First guest on the show this week :) https://fountain.fm/episode/m6msKRJKxnS4b5ba1Gni