This is why I don't care for apps that ask for 100+ signing requests while they are running, no clue what its doing in the background. also cant verify what your signing if you have auto approve View quoted note →

What if we did reverse outbox model? Instead of trying to connect to at least two relay per contact you would show the relays that your contacts post to and browse those relays individually. It would only be a subset of your contacts but it would be much easier to implement and would give you multiple different feeds

Jumble has really good UX and there are some parts of it that look like they were copied from noStrudel. So I think it's only fair if I copy them back to improve noStrudels bad UX @Cody I assume there was a lot of intention behind jumbles UX flow and layout. It would be great if you could write about it, even just pointers on what libraries you used or some of the complicated problems you had to solve. I'm not a good example for this but I'd like for us devs to talk more about the technical stuff and bugs we are working on. At least that's the type of content I want to read on Nostr.

#asknostr does this make sense to you?

#asknostr what are some good open source AI chat apps for android. Something I can use to easily query an OpenAI compatible provider like @PayPerQ or @routstr

Turns out there are more implementations of RxJS in other languages

ReactiveX

I had no idea... I'm not saying someone should... But it would be cool to have applesauce avaliable for other languages

I will collect all the nostr events into my nostr-relay-tray and there is nothing you can do to stop me @Cody why is there a whitelist for searchable kinds?

GitHub

nostr-relay/packages/event-repository-sqlite/src/search.ts at master · CodyTseng/nostr-relay

A framework for developing a Nostr relay. (WIP) . Contribute to CodyTseng/nostr-relay development by creating an account on GitHub.

Why not make every kind searchable, id like to search highlights and everything else

Next version of #noStrudel is going to finally use users outboxes for the main feed. and I know its working pretty well because its finding @emperor's new groove notes Its using the relay selection logic from applesauce

Applesauce Examples

Why don't we have a simple way for relays to self describe what they are? like ["read-only", "indexer"] or ["personal", "index", "read-only"] Maybe its getting to semantic but it feels like it would be so much better then checking for supported nips (don't really tell you anything) or the (always wrong) nip11 document Id like to recommend some indexer relays inside the app and I don't want to hard code them. so if they could just advertiser themselves that would be great

Well I was going to make a big post about all the changes I've been thinking about for noStrudel V1, but then the page reloaded and I lost the draft... so I guess that's something ill try to fix with the next release In the meantime just pretend this post is a detailed description of how awesome V1 release is going to be. (hint I want to default to outbox model)

cool app for managing your follow list

Plebs vs. Zombies

Plebs vs. Zombies | Nostr Follow Manager

Clean up your Nostr follow list by identifying and removing dormant zombie accounts. Hunt zombies, manage follows, and keep your network alive!

New applesauce package with random stuff. like a @Vertex API and @primal caching API https://www.npmjs.com/package/applesauce-extra Mostly vibe coded, so I have not verified if everything works. but the user search methods for vertex and primal work 😁

Applesauce Examples

#SovEng

NIP-77 negentropy should be supported by default in a lot more relays. I added support for it in applesauce last week and since then I keep thinking if ways it could be used.

Could all the devs who are using applesauce for an app paste the links in this thread, I'd like to add an "apps using applesauce" section to the docs site