Did my first stream on zap.stream! Super cool and easy to set up.

zap.stream

Dustin is streaming

Playing Go

On Nostur I can’t seem to connect to Damus relay, and I’d really like to - is there a requirement of some kind? When I go to settings > relays > wss://relay.damus.io > connect, it flashes green for a hot second and immediately goes back to disconnected state.

Enums make me happy

GM Nostr!

Verifying my Nostr Nests identity: 0bISV0yC1ctZ45U-k67DqYFzUZX_dmFM9Ciwe5jT2-A

Nests

Nests - Live Audio Rooms on Nostr

Host and join live audio conversations on the decentralized Nostr network. No algorithms, no gatekeepers, just real conversations.

Stuck like this on Nostrudel, tried re logging in and clearing my cache. Should I do anything else? Been probably 1-2 weeks since I used it.

Client DVM feature idea: generate a photo for your profile pic Could use the user’s bio or let them say what they want the pic to look like. They pay the request and then the client automatically swaps our their profile pic with the one created from the AI

Some interesting DVMs are popping up. Found on

Nostr decentralized search and other stuff

Are there any LLM projects for entire code bases? Feels like I should be able to train an LLM on Damus source code to get suggestions on how to add translations into Nostur…

@PABLOF7z @StarBuilder I updated NIP 90.md PR so that customer feedback is a kind:7, FYI

GitHub

Update 89.md and 90.md with Customer Feedback Data by dtdannen · Pull Request #985 · nostr-protocol/nips

This adds an additional protocol flow step to Nip-90 where a Customer can provide feedback back to the service provider.

Could we make NIP-25 Reactions include arbitrary strings like “this worked but took too long” or numbers like “96” ? Terrible idea? Currently the spec says it’s for emoji or ‘+’ or ‘-‘ I want to expand it so we can give DVMs the reactions they deserve (with flexibility on the amount of detail)

GitHub

nips/25.md at 8331354947f2d577e13eb5da4a56133071cb1019 · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

Oh boy I could really use an LLM fine-tuned on the NIPS docs right now.

DVMs will help clients and relays be lighter, by offloading computation. Algorithms for sorting your feed could be done via DVMs.

If you’re interested in AI, Rao is one of the best perspectives to have. Cuts directly through the hype and his lab has lots of papers to back up his claims. Not on Nostr yet, for now Twitter and LinkedIn seem to be where he posts

LinkedIn

Doesn't the fact that LLMs can "write code" prove that they can also reason and plan? (Hint: Nope..) (Part 2/2) Continued from Part 1 https://lnkd.in/gz5Wr7da In contrast, though, the code data for… | Subbarao Kambhampati | 13 comments

Doesn

I have proposed an update to NIP-90 for a customer feedback event:

GitHub

Update 89.md and 90.md with Customer Feedback Data by dtdannen · Pull Request #985 · nostr-protocol/nips

This adds an additional protocol flow step to Nip-90 where a Customer can provide feedback back to the service provider.

and created an issue on vendata.io to add a user interface element so a user can send a `customer-feedback` after the DVM has finished.

GitHub

Add human feedback response to output · Issue #5 · pablof7z/vendata.io

When the result comes back from the DVM, allow the user to like or dislike, use a reaction emoji, and/or add text describing their feedback. This f...

@PABLOF7z @StarBuilder thoughts?

If a client chooses to make a new feature via DVM, then other clients could adopt the feature quickly. Consider recommending new people to follow on Nostr. Each client could implement their own version, or instead one person could make a DVM that other clients hit to get the data. DVMs may cost money but paying per each request to the DVM probably doesn’t always make sense. “Salaried” DVMs might be a solution. Client subscription fees could cover DVM fees. Free clients wouldn’t have the paid DVM features. Network effects would be insane here!