Working my way through “Build a Large Language Model from Scratch" and the publisher (Manning.com) has a feature that is basically @npub1w0rt...cu4x , called ‘livebook’ although the interface for showing highlights isn’t quite as nice as highlighter.com. First time I’m seeing something like highlighter not on Nostr. Highlighter UX for textbooks or other dense reading material where people can have side discussions will be amazing.

Relay devs and runners - do you limit massive filter subscriptions? Is it terrible to subscribe on a filter for kind 3 events for say 100,000 npubs? Has anyone written a guide on relay filter etiquette? Or should I ask for what I need and if relays stop responding / block me, I submit smaller filters? tagging a few folks that I know develop and run relays #asknostr @utxo the webmaster 🧑‍💻 @PABLOF7z @Mazin

If an npub has no follower from within my ‘n’ degrees of followers, why am I ever seeing it in my Nostr client? Is this just a compute problem? If so, let’s start running DVMs to solve this. Does such a simple solution not work? Let’s say you are brand new to Nostr. For you to get connected, you’d need to: 1. post a few high quality notes (anything that’s not spam) 2. follow people you like 3. wait for one npub who has followers to follow you. As soon as 3 happens, you’re good to go. If a spam account gets past this part, you just need a few people to report them and then your client shows you that should be skeptical of this person. The question then becomes, how do you find new people to follow when there is a flood of potential fake profiles waiting to be discovered alongside new real people? Best case solution, you meet anyone in real life who has a Nostr account and they follow you. Worse alternative is bootstrapping from legacy social media. There will probably be markets in the future selling you access to Nostr networks (pay me to follow you and add you into my WoT). You could be anonymous this way. Maybe AI search tools will be able to pick out some authentic profiles just by the content they post. Moral of the story is - the incorrect solution here is to KYC or scan eyeballs for “proof of human”.

GM

GM.

GM. Life hack: if you’re feeling down, go pick up litter in your local park.

My expectations of other social media platforms is increasing because I’m used to Nostr as my main driver. Saw a high value post on LinkedIn this morning and I went to zap it before realizing there’s no zap button on LinkedIn. Like why not!?! Walled gardens are decaying as Nostr blooms.

Turning users prompts into database queries is all the rage in LLM land and I can’t help but wonder about the potential exploits like little Bobby droptables

xkcd

Exploits of a Mom

Data vending machines provide extra functionality outside clients and relays. View quoted note →

Today's daily puzzle was a bit tricky, try it yourself. I was not sure I had it right when I submitted the solution:

ARC Prize

ARC Prize - Play the Game

Easy for humans, hard for AI. Try ARC-AGI.

I just went back and forth with an OpenAgents AI that created a PR for an outstanding issue on DVMDash. The solution is now live on the website (the task was to add the current github commit hash to the DVMDash webpage so users could easily verify which version of the code is running, either in the cloud or locally). Overall, it was a smoother experience than I expected. Props to the team behind OpenAgents; looking forward to using this project more. You can view the PR conversation here:

GitHub

Add git commit hash to webpage by dtdannen · Pull Request #30 · dtdannen/dvmdash

This pull request implements the feature to show the git commit hash on the webpage, as requested in issue #25. Changes made: Created dvmdash/dvmd...

Every comment that ends in "(Comment from OpenAgents)" was the OpenAgents AI, everywhere else was me. You can see that I kicked back two different errors, and then I had a few requested changes to how it visually appeared on the webpage. In the end it took 6 iterations. The flow was: 1. I connected OpenAgents to my github repos 2. I started a chat, selected the dvmdash repo, and checked the permissions I wanted to give the agent 3. The first thing I asked was: "Can you try working on one of the github issues that is marked as "good first issue"?" 4. It then picked the git commit issue after looking at a few of them and submitted the first attempt. 5. I did a git checkout of the PR, tested it locally, and then posted the failure back to the PR thread via Github, like I would with any contributor. 6. Then, in the chat with the agent I said: "please respond to the new comment on the PR" 7. It then went off, got the latest comment from Github, modified the code, submitted a new commit, and pushed it along with a new comment. I repeated steps 5-7 another 5 times, before it fully worked in a way I was happy with! Check out the git commit link on the top right of https://dvmdash.live/metrics ! View quoted note →