Flotilla 1.6.5 is out on web and on zapstore! This release is NOT the big one. That's coming hopefully this week. However, this release is substantial: * Attempt to fix permission grant for notifications * Make sync logic more robust * Add unban/unallow support * Improve support for downloading/opening protected images * Add manual send/receive to wallet * Show wallet status when wallet is unreachable * Update nostr signer capacitor plugin * Fix some safe area insets * Update NIP 55 signer plugin (fixes Primal login) * Refine space join dialogs and discover page * Reopen the last DM that was open when navigating back to chat * Get rid of ChatEnable interstitial * Enable auth for relays we're publishing to * Drag and drop space icons * Add better muting support * Add back button to settings menu * Add page titles * Improve scroll to event behavior * Add in-memory search to rooms * Fix editing messages with html tags * Fix DM media detection * Clean up reporting dialogs * Improve room detail If you experienced bugs, please try the new release and tell me about any new bugs. Voice rooms and email/password login coming very soon.

I made a spoon

Not saying your mom jokes in front of my kids is one way in which I die to self daily

@utxo the webmaster 🧑‍💻 I gotta ask, how is wisp so fast

switching to @npub130mz...l29s makes spending on tokens hit different, I've spent 300k sats this week 😅

@utxo the webmaster 🧑‍💻 I love the custom colors, and the post delay interface, great work on wisp

Getting close to being able to release pomade to Flotilla users. Here's a boring video which showcases the UX:

My spirit animal is this website

RFC 406i - The Rejection of Artificially Generated Slop (RAGS)

I've heard people talk about the technique for agentic coding where you have a bunch of agents build the same thing in parallel 100x then pick the best implementation. I'm sort of doing the same thing with pomade right now — instead of building one implementation of the protocol, I'm building three (one in typescript, one in rust, and one in go). But what's neat is I don't have to choose one, because the whole idea is to have multiple separate unrelated custodians, each person can run an entirely separate codebase.

> It’s been six years since GPT-3, and there has been no “move 37” moment for writing (as there was for AlphaGo’s creative play of Go). Not even close.

Bits In, Bits Out

Six years of AI and the world got stupider

This article says a lot of what I wanted to say about LLMs, but couldn't find the words:

The L in "LLM" Stands for Lying — Acko.net

Questioning the frame of inevitability in use of AI

I don't agree with his conclusion that leaning in to intellectual property rights and source citation is the solution, though that's an interesting though. But there are some great sections, particularly in the first half. Here are some highlights: > LLMs do something very specific: they allow individuals to make forgeries of their own potential output, or that of someone else, faster than they could make it themselves. > Experienced veterans who turn to AI are said to supposedly fare better, producing 10x or even 100x the lines of code from before. When I hear this, I wonder what sort of senior software engineer still doesn't understand that every line of code they run and depend on is a liability. > > One of the most remarkable things I've heard someone say was that AI coding is a great application of the technology because everything an agent needs to know is explained in the codebase. This is catastrophically wrong and absurd, because if it were true, there would be no actual coding work to do. > > It's also a huge tell. The salient difference here is whether an engineer has mostly spent their career solving problems created by other software, or solving problems people already had before there was any software at all. Only the latter will teach you to think about the constraints a problem actually has, and the needs of the users who solve it, which are always far messier than a novice would think.