GM.
If it is open source, than someone could run it behind a DVM!
Once something is accessible via the DVM protocol, it can be used just like any other DVM, so other DVMs could call it, etc. reduces a lot of friction
Right so I think the difference is that instead of that company hosting it (or any company), someone runs a DVM that does that work for you and you can pay a subscriptions, etc.
Also, it would be easier for AI to use it if it’s a DVM (just pay an invoice, no need to sign up, no cc info required, etc)
If you want privacy though, it might always be better to go through a company like that.
Where would the ci/cd action run if not in a DVM? Or is this just a private ci/cd action?
Have you considered putting whatever logic you’d like to run to solve this inside a DVM?
Just posted my first quick update of CI/CD on Nostr. It's my first video like this so it's not amazing quality, but i gotta start somewhere... 🤷♂️
📜TLDR:
Basically I added a little front-end to trigger a DVM that watches the specified repository and publishes a note on each commit, mentioning the author and commit hash.
🐾 Next Steps:
- Split publishing of note into seperate DVM's (aka: introduce chaining)
- Improve handling of DVM request (adding responses)
- Add other chained steps (like pulling/building repository)
- ...
🚀 To try it out yourself:
- https://stens.dev and enter a repository naddr
- nostr:npub1hflnseyhn7tkngmkfmr4qrjygjppw3dgg3t3xpeza7r4skwy3u9samkmwh will put out notes on new commits.
CC: nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 nostr:npub1mgvwnpsqgrem7jfcwm7pdvdfz2h95mm04r23t8pau2uzxwsdnpgs0gpdjc
#grownostr
Love it. Chaining will be so cool. I need to make a few updates to the debug page on DVMDash to show infinite chains
GM.
Life hack: if you’re feeling down, go pick up litter in your local park.
Found it, was surprisingly easy, figure 1 is where it’s at:
https://www.fiscal.treasury.gov/files/reports-statements/mts/mts0824.pdf
This came up during my dinner conversation but I didn’t have these numbers, any chance you have links to sources or know where to look this up?
Same issue in peer review for scientific literature, rejections aren’t public either for similar reasons
Full dump of nostr events collected by nostr.band crawler for you to play with (550Gb): https://media.nostr.band/events.jsonl.gz
If you wanted to do research, data analytics, calculate stats, etc - that's your chance.
Contents:
- 550Gb of nostr events in jsonl format, gzipped
- no data about source relay
- some event kinds are absent (DMs, other encrypted stuff, ephemeral)
- some duplicates are possible
Will publish regular updates on this data set if someone makes anything useful out of it.
Thanks nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p for the push.
You could consider getting a DOI for this if you want to get cited for it. It’s a thing, and any academic papers can cite you easily if you get a DOI. For example, you can use zenodo (https://zenodo.org/), they also will host it for a long time. Might have to check size limits. There’s other services too.
It’s a way to get credit for putting this all together.
I’m sure they’ll announce it any day now
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
Same. A game I recently found and enjoy: isle of arrows
Tower defense with some board game elements
Data vending machines provide extra functionality outside clients and relays.
nostr:note10ss3jncag4uzzyvrdayqkf3sjnr727mjkzz29egzrykan32fne7qz2fl7w
You might need to run (yourself, or someone else) a DVM to accomplish exactly what you want, if one doesn’t already exist.
To browse existing Kind 5300 DVMs (the ones that generate feeds), check out: https://dvmdash.live/kind/5300/
You may also find these slides helpful from a Nostriga Tutorial on DVMs: https://dustinnostrfiles.nyc3.digitaloceanspaces.com/Final_Data_Vending_Machines_Tutorial.pdf
Today's daily puzzle was a bit tricky, try it yourself. I was not sure I had it right when I submitted the solution:
Next up is François Chollet
If you want some real signal on AI, check out this live stream. Day 2 will happen tomorrow as well:
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: https://github.com/dtdannen/dvmdash/pull/30
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 !
No, that’s just one type of DVM.
They are micro-services that have Nostr accounts.
Data vending machine!
checkout these links to learn more:
Get you a #nostr client with translations to welcome nostriches speaking another language! nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955
nostr:note1uu8vr3wvh4j6sdxp967ndkpghny4kygyezavq7j2nyefzk0wjhfsqfkg9j
Cool, I actually did want to try it with the DVMDash repo I’m working on. Made a bunch of issues and thought I might try to see if it could make any reasonable progress on some of them