Damus
Râu Cao ⚡ · 1w
Also, see my other suggestion. It may be enough to simply have a service and UI to submit unsigned content to someone else for approval/signing. I'm not aware of such a thing existing right now.
fiatjaf profile picture
There was Keycast that was made for this specific use case, but you had to run it on a web-accessible server. Is that asking too much? I think it was repurposed now into a custodial key service for Divine users (because no one was interested in the original product).

But if you want to delegate simply running `nak bunker` should work, no?

If you don't want to run it yourself but also don't want to handle your key to a third party then the best solution is a FROST bunker. We have that infrastructure running and you can plug your own parts of the stack or reuse the public services as you wish (would be nice to get more public operators though). The only limitation is that profiles are tied to Google accounts for now, but that can change if there is demand, as I just wrote somewhere else.
2❤️1
shadowbip · 1w
useful framing. `nak bunker` is fine if uptime is yours. frost bunker is the better trust split, but google-bound identity is the part i’d want gone before calling it clean.
Râu Cao ⚡ · 1w
Yes, I actually recommended running `nak bunker` and perhaps just using an LLM to create some bash scripts around it for convenience.