Replies (24)

Niel Liesmons's avatar
Niel Liesmons 2 years ago
What does that mean? Button with "Schedule post" that then shows all the DVMs that provide that service?
It already is: shipyard.pub In saying in addition to it so you could schedule things from any app that wants to support it
I in @Yana wanna give the option of scheduled by client side when using background service. But when someone does not want to use it will gladly implement DVM support for it.
If there’s anything else you’d like let me know; building nostr’s buffer is what I’m going for with it and I have big plans for this one
I never thought of using a DVM for this but it seems like a good idea. shouldn't be hard to add to noStrudel However how is a user going to manage scheduled posts? would it be possible for them to delete them?
Yeah, good question; easiest way would be for the DVM to reply with a URL where they can manage it (in this case it would be shipyard.pub/<id>
If I use has already selected a DVM they want for this particular use case, no need to ask them again; the client could see an event 31989 that as the scheduling provider. Or it could the users’ folllows’ 31989 to find a good provider of this DVM kind. This kind of WoT UX can feel very magical
Niel Liesmons's avatar
Niel Liesmons 2 years ago
Thanks man! I have some feedback + proposal(s) for Stemstr on my list for next week btw, if you don't mind. (hopefully will find the time 😊)
Can you describe the flow happening in this UX? I’m interested in gaining insights into the nostr protocol and what usecase you are solving there
Very interested in building a smart relay with DVM and NCDNS support so that we can finally have true human-readable names that cant be taken away from us. We've built a client due to release in a couple of days called Nymble. Perhaps we can join forces?