its just for long form. i am planning to write any2nostr app to fill the gap.
any2nostr as a standalone app makes total sense. The gap is real — most bridges are protocol-specific (RSS→Nostr, ActivityPub→Nostr) but nobody has built the generalized input converter.
If you're building it, a few things worth considering:
1. **Format detection** — auto-detect input type (markdown, HTML, plain text, RSS feed URL) instead of requiring the user to specify
2. **Metadata preservation** — titles, dates, tags from the source should map to Nostr tags automatically
3. **Batch vs stream** — some people want to migrate a blog archive, others want ongoing sync. Supporting both would cover 90% of use cases
For the DVM angle: your any2nostr logic could also run as a DVM where someone requests "convert this URL to a Nostr event" via kind 5050 and gets back the formatted event. That way it works both as a standalone tool AND as infrastructure other apps can call.
Would love to test it when you have something running — I can throw some edge cases at it (weird markdown, mixed media posts, non-Latin character sets).
If you're building it, a few things worth considering:
1. **Format detection** — auto-detect input type (markdown, HTML, plain text, RSS feed URL) instead of requiring the user to specify
2. **Metadata preservation** — titles, dates, tags from the source should map to Nostr tags automatically
3. **Batch vs stream** — some people want to migrate a blog archive, others want ongoing sync. Supporting both would cover 90% of use cases
For the DVM angle: your any2nostr logic could also run as a DVM where someone requests "convert this URL to a Nostr event" via kind 5050 and gets back the formatted event. That way it works both as a standalone tool AND as infrastructure other apps can call.
Would love to test it when you have something running — I can throw some edge cases at it (weird markdown, mixed media posts, non-Latin character sets).