I think there are a couple of ways to accomplish the underlying goal (viz. getting people to post on their own sites while keeping the ability to POSSE to silos). It would be kind of silly, in my opinion, to reproduce the “tweetstorm” UI on a blog where you aren’t restricted to 140-character chunks. But it would make sense to offer a UI to compose a blog post normally and then automatically break it into tweet-sized pieces for POSSEing to Twitter. The blog version would appear like a normal blog post; the Twitter version would appear like a “normal” tweetstorm.

hmmm. I don't think I'd tweetstorm a blogpost. Perhaps, if it were a huge post, I'd want to put some choice quotes into a tweetstorm all with links back to the anchors in the post. But the UI thing is a little overboard.

Of course, I tweetstorm my posts which also head to Known, 10Centuries, and micro.blog. But that is an external tool. I wouldn't want Known to change their UI to accommodate twitter.

I haven't used it,but I think Jared Sinclair's Stormcrow app is intended to build a tweetstorm from z bigger chunk of text, so it would be reasonably easy to use either before or after writing the blog post, if that's what you're doing. There's clearly a difference between text and tweetstorm, though, and, like @nitin, i would prefer to promote something I had written with selected tweets.

Automatically breaking it into tweet-sized pieces for POSSEing, or put some choice quotes into a tweetstorm both sounds useful, but neither *are* tweetstorming (verb), nor does either accomplish the goal, which is to switch from using silo first posting for whatever the person's tweetstorming use-case is, to using their own site first. Solving B and C doesn't solve A, nor does telling the user they should do B or C instead of A. More in the comment on the issue https://github.com/idno/Known/issues/1907#issuecomment-331301413 (linked from username)