Hey folks,
1/2 I've been experimenting with methods for keeping a string of posts connected as a #thread and this poll provided some guidance: https://mastodon.cloud/@nontechietalk/110046396755047235
My first thread was standalone posts with sequential numbering, preferred by just 5% of respondents.
My last thread was each post as a reply to the top post, preferred by 19%
Each post as a reply to the previous thread was the overwhelming choice, preferred by 76% of respondents.
Changed my mind. I'll stick with the reply-to-top for this next thread.
I prefer that, if anyone replies to, say, post 3, all that forked conversation will be just to post 3 (and, of course, rolling up to post 1).
If each post is a reply to previous, every reply to every post would create a jumble. Not loving what that is setting up to be.
Perhaps, I'll try that approach with a shorter thread.
@duaneaubin I think for those wanting to write larger pieces, a fediverse app that allows something more akin to a blog post than a microblog post would be better.
Because I see a fair amount of toot chains, and I’ve never seen it work smoothly.
That said don’t stop it you from tooting away. If we have something to say, it’s worth saying. Technology will catch up in some way:)
@breadbin @duaneaubin The 500-character limit is just a default setting. Server admins can choose a much higher limit if they wish. My instance allows 65,536 characters, for example! No threading necessary then.
@duaneaubin @breadbin Very true, and I do tend to run on when posting original thoughts, because there's nothing to stop me or even slow me down!
@pwinn @breadbin I can certainly see advantage to that kind of length. Yet, it also seems... unwieldy to me on a platform like this. I might read an article and have multiple reactions, it'd be harder to speak directly to each point...