One of the things I just realized that may be an issue for long form publishing platforms is migration from other platforms.
Say a user wants to migrate from Medium. How do they port their content? It’s easy to say, just leave it alone and start fresh, but I suspect people will not like that.
I have my own writing tool app and customers requested to have their content ported over.
I haven't looked into them, but I would presume you could write a decent scraper for most of the content.
But user is not going to manually publish it? And if they did, then what - it gets published at once and floods the network?
I suppose you could create a tool for users to run a script and import their notes.
We’d need a way to not flood the protocol though.
I think that tool exists already, if I'm not mistaken. On highlighter.com, there's the possibility to import any blog post as a nip-23 long-form note.
Oh!
A wordpress/etc plugins make sense to me - create 'blog' profile, store keys in the plugin, export all content to long-form (existing & new as published), notify in admin area about kind-1 comments etc.
Flood isn't a problem, at least for now - the load will be trivial, and you could set created_at timestamp as old as you like (to match the dates on old posts). The issue is that most relays won't accept old events atm, so this would require some (paid?) arrangements with relays.
An idea I had was to make an import service that imports into your own archival node. I was thinking of the Twitter GDPR archives as source but it might work with other platform data as well. That way you can recreate content with original time stamps, and serve it back to the network. Combined with a reverse proxy relay service would work well.
Interesting 🤔
