Adding "outbox builder" to my to do list for applesauce. I've built a very flexible relay pool that doesn't have any "default relays" but I still have a long way to go before it can support the outbox model out of the box although once I get there it might be easier to make micro apps. since I won't always need to build a settings view to allow the user to configure the default relays

I have this saying I like to repeat to myself a lot when it comes to software development. "don't lie to your users" It sounds obvious but so many developers don't get it, or at least don't see the whole picture and there is a moment in this podcast that illustrates my point perfectly. At 42:00 Chris looks down at the recording software and it says "connection unstable". he gets upset, and starts asking why and how the connection could be unstable but because the software cant talk back it never answers his question... Obviously we don't want software to talk (yet) but my point is that it notified him that it detected an issue but refused (lied) to tell him the reason why, or how it detected the issue. Was the connection unstable because it lost 50% of packets? is the latency over 5 seconds? is the recording software lagging due to CPU? The software *knows* the issue, otherwise it couldn't have detected it. but the developer decided to lie to the user. probably because they thought the user wouldn't understand. but this just leaves the user in the dark and easily frustrated which leads to them quickly loosing confidence in your software. Don't lie to your users, if there is an issue tell them about it and what it is. even if they don't understand at least you will still have a user. Video link with time: https://blossom.primal.net/979bf277264f6c42a99be43a33ade167e2711f103247ee243653f1ebd3dcec8d.mp4#t=2520 P.S. might be better to use OBS to record long podcast (vlogs) then some internet connected thing. but idk, I don't vlog :)

NWC is the way

I thought Satscomm was just comments and not highlights

I don't use iphone and probably never will :( But I'm looking for this on android

Looking for something that works with generic sites. most of the stuff I read isn't on nostr :(

Zapping in the first place isn't economically viable for me, I loose so many sats... But it would only be an additional 4 sats per transaction so its not too bad if you do larger zaps

Can't wait to see what you build with it

Ever wanted to create a temporary NIP-46 bunker using your NIP-07 extension?... well in case you did I added an applesauce example that lets you create NIP-46 bunkers (remote signers) for testing. also applesauce V3 will have a class for easily creating and handling the server (bunker) side of remote signers 😁 Example: https://hzrd149.github.io/applesauce/examples/#signers/bunker-provider Documentation: https://hzrd149.github.io/applesauce/signers/bunker-provider.html

It seems like it would be super easy for browsers to support. Since you can already run it in wasm

I haven't see the "scope" type yet, still need to do a deep dive on it. just been thinking about what it would take and wanted to provide feedback, not sure if I will go through with building an implementation (maybe more pressing bugs to work on)

Blossom is a simple http protocol for basho addressable content. And will hopefully allow Nostr clients and users to share censorship resistant media and files. Blossom doesn't have "chunking" (splitting a single file up so its more easily transfered and stored) since the protocol was design to be as simple as possible. Maybe in the future it will but for the time being torrents are still the best way to distribute "large" files. Applesauce is my nostr SDK I've been building to support noStrudel and other small Nostr apps I've worked on. Effectively, it's a competitor to NDK.

#asknostr does anyone know of a good NIP-84 highlights app or browser extension that works on mobile? I read a lot of articles on my phone and I'd like to post those to nostr

Fees are at 1sat/vB, I doubt it's the fees preventing people from using bitcoin

I can only read this as F*** your customer...

Done 😁 https://hzrd149.github.io/applesauce/examples/#nwc/auth-uri Docs: https://hzrd149.github.io/applesauce/wallet-connect/wallet-connect.html#using-a-nostr-walletauth-uri

Never mind found it, just had to do some digging in the github repo https://github.com/nostr-protocol/nips/pull/1818 https://github.com/rolznz/nips/blob/feat/nip47-client-created-secret/47.md

where is the documentation for the "nostr+walletauth+alby://" URIs your using in the bitcoin-connect package to make it so user can scan a QR with alby go and connect the wallet? Id like to support it in my applesauce library and I want to make sure I'm going off the documentation and not guessing

Awesome, followed

no, my POC only had paid uploads. never got to the point of trying downloads