pull down to refresh

Peer-to-Peer Delivery/Transport over Nostr
604 sats \ 4 comments \ @trevthom 9h builders
I am of the firm belief that we should be making as many permissionless and decentralized applications as possible to replace companies who take a cut of the labor of hard-working people.
I started this application as a way to replace the likes of Fedex/UPS, USPS, Lyft/Uber, etc.
It is entirely built with Claude so far, because my programming experience is very minimal, but it looks decent. I would love for some more experienced builders to contribute. There is still a lot of work that needs to be done.
You can find the repository here: https://github.com/trevthom/nostr-delivery
write
preview
related posts
100 sats \ 1 reply \ @optimism 6h
Why is there a backend component with GET/PUT/PATCH if it is over nostr? Also there's no license, so no one should contribute to this repo as long as that is so (but realize, also no one really wants to co-code with claude that someone else prompted.)
Gentle nudge: if you share vibed code as open source, be aware that you shared your PoC - you just gave away your moat, your idea, so be careful now, because you've kind of just made yourself obsolete, especially if you cannot code. 1

Footnotes

  1. Note that I'm a bit hostile to the usage of vibe coding in actual products, see #1250807 ↩
reply
0 sats \ 0 replies \ @trevthom OP 5h
To answer your first question: it's because I used Claude and I am not a software engineer.
Ultimately, it's just a WIP and I'm not trying to make money off of it, so I don't care if someone takes the idea. I don't care if people use Claude to code with it. In fact, I would be happy to see real software engineers tackle this. It is a problem that I think needs solved and initially, I was just playing with Claude to see how far I could get with it.
At the very least, I was just kind of hoping it might spark an interest from someone else who might like to make a real, working version of this, whether or not they start with this version.
reply
0 sats \ 0 replies \ @Fenix 1h
Some time ago I had a similar idea based on another project, I only kept it as an idea because I'm not a dev and I have no idea how to do it. It would be to use nostr and PLS for rides and deliveries, just as you proposed. Each order would automatically create a contract on PLS between the provider and the user with a default (or otherwise chosen) arbitrator, the contract is sealed with the service amount in sats by the user and a kind of "insurance" amount by the provider. At the end of the ride the contract remains pending objection and a deadline is set; if it is not contested the contract is closed, the payment and the insurance go to the provider and both reputations are recorded as an agreement closed pending written review. In case of dispute the arbitrator is triggered.
reply
0 sats \ 0 replies \ @VzxPLnHqr 6h
Great initiative! I think it is also important to do it in as privacy-preserving a mannner as possible. To the extent it is helpful, here is some outdated research/notes regarding how to use LN to accomplish parts of this.
reply