why couldn't we let users sign events / log in by presenting a qr code, and have the user sign from their signing app? wouldn't go thru relays, signer could be offline. would be a bit of a QR dance (scan then be scanned), but otherwise seems ok. #asknostr

is there a nostr website that's just a client to submit reqs to relays, no need for user keys ? Just to read stuff

interesting to watch AI get very confused with moderately large typescript apps, but fine with go/rust/elixir projects. Despite the mountains of training data for it, it seems to still struggle with React's model.

New Deftones coming soon LFGGGG

The czech Techcrunch is called CzechCrunch 💯😆

Today ~500k high school grads sat for philosophy exam in france. 4 hours to write an essay, the prompt choices: "Does our future depend on technics?" "Is truth always convincing?" "Do we need art?" "Are we free in all circumstances?"

man Mistral ships like crazy

has anyone built a kind 10002 directory? So you can find a users relays in the outbox model? #devstr

im getting 'filter item too large'' errors from relays for querying for 4 authors... no comprendo... whats the size limit?

MCP for Nix 1.0

GitHub

GitHub - utensils/mcp-nixos: MCP-NixOS - Model Context Protocol Server for NixOS resources

MCP-NixOS - Model Context Protocol Server for NixOS resources - utensils/mcp-nixos

only beef with this is that it's called "nixOS" when it actually focuses on the Nix part, not the "OS" part. I want an MCP that interacts with my local machine (queries the store, analyzes dependency graphs etc).

imo one possible vector of ecash adoption is the amount of vibe coded apps that devs will make public but dont want to turn into a whole business or subscription play. They're happy to keep it running if it makes a small, positive return by users sending them ecash per usage.

I regret to inform you that france has discovered brisket... and they are fucking good at it 🥹

great writeup, and funny I try not to shill langs or ecosystems--to each their own--but one should note that Erlang (and by proxy Elixir) have the concepts of Agent and Supervisor baked into the language for decades. The framework for these patterns is called OTP. See

Supervisor — Elixir v1.20.3

Every language ecosystem will need frameworks to handle async, coordinated, supervised agents that scale. And they will need to be highly parallel, again concerns that Erlang addressed decades ago. I suspect every language ecosystem will end up rebuilding OTP frameworks in order to build agent fleets. I disagree with the author when he says "we're already very good at parallelizing work". In most languages, parallelism is an afterthought bolted on to the language (Python being a great example of this), and their performance cannot match languages and VMs that took parallelism as a first-class concern (Rust, Go, Erlang). Engineer or not, I recommend you spend some time reading on the history of Erlang and Elixir--highly relevant to the times at hand. View quoted note →