In my previous thread (on infosec wishlist items, here https://social.coop/@dynamic/115004207618295294) I took the plunge and intentionally violated conventional Mastodon thread structure.
It's a bit of an experiment, and I'll see whether I regret it.
I wanted each topical toot to be structurally at the same level. Conceptually this feels right for a wish list with replies, especially if other people add wish list items.
It also means that the #thread structure will look right on Facebook-like platforms like #Friendica and #Hubzilla.
I think the main disadvantage of structuring a thread with toots all at the same level is that on #Mastodon, when any subtoot is activated, the rest of the thread (except for the top post) becomes invisible.
I seemed to recall having written a thread about thread structure before, but a quick search reveals that it's actually a thing I keep coming back to. Links to related threads follow.
I think my first Mastodon thread about threading structure was this July, 2023 thread:
https://social.coop/@dynamic/110656011613352543
There was also this April, 2024 poll on how people prefer to consume longform content on Fedi:
https://social.coop/@dynamic/112257962194554804
And on May 2024 when social.coop was discussing whether to increase character limits I posted this thread gesturing toward the idea that maybe keeping character limits is a good idea for Mastodon instances:
https://social.coop/@dynamic/112428200242353565
For anyone who's curious about why the structure I used for the infosec wishlist structure works well on non-microblog platforms, here's a couple screenshots of what it looks like on #Hubzilla
And here's what InfoSec the thread looks like on #Friendica. I think indentation of subthreads is a bit clearer on Friendica than Hubzilla.
