Shipping Shipyard DVM

I'm happy to announce that Shipyard is now roaming the nostr relays as a DVM.

Ok, what the hell does that even mean?

Ok, so DVMs, or Data Vending Machines, are just programs that take requests over nostr to deliver... well, data.

And what is Shipyard?

Shipyard, as it's slogan "A Quiet Place for Loud Ideas" implies, is a write-only Nostr client. One of the instrumental features that Shipyard.pub implemented was the ability to SCHEDULE posts and reposts. No more fighting to publish your notes to defeat the evil Timezone Cabal; you can write your note when you see fit, and then schedule so it's published whenever it makes most sense to you.

Groundbreaking stuff, I know.

Ok, so now, Shipyard's scheduling superpowers can be accessed as a DVM:

meaning that any Nostr client can now easily add scheduling capabilities without much fuss!

For example, this long-form post was actually written a day before it was published, and the publishing was handled by the Shipyard DVM.

How does it work?

Client developers can use NIP-89 to find kind:5905 DVMs, right now only Shipyard, and when a person wants to schedule a post they simply send the post via an encrypted DVM request to Shipyard. That's it, at the time the event's created_at timestamp reaches the event will be published to the specified relays!

What can it look like? Up to clients developers to decide; here's my take: