Feedback after a year+????

[Chainsmoke]

So not sure how to go about this, but I guess being straight to the point is the best way!

Yeah, as the title says, I'd like some feedback on my threads, specifically the MxF one and the NbxNb/F one (the FxF/Nb is far too popular to need a feedback)

 

[Honey Blossom]

Just a few quick things I noticed.

• I usually find that full NSFW threads are ones I skip over/forget about. Sometimes I'm browsing while out and about and don't want to take the risk of seeing full-on porn embedded in a thread. NSFW links are usually more accessible to me - that way I can choose to view it. In the same vein, the different sized pictures completely take the focus away from the plots for me; I'm not really even able to focus on the content with so many differing image sizes/table sizes.
• I think code words are silly, personally. People who are going to read your thread are going to do so regardless, and people who don't will be obvious from the start. Requiring a code word as another hoop to jump through is a bit of overkill in my opinion.
• The double-first-post thing is a bit confusing — are you looking for the ideas in your first post, or in your second? Combining them might make it easier to read.
• The spoilers in the second post are a bit vague — it's nice to have plot titles, but I like having a bit of a blurb after them so I can see if the spoiler is even one I want to open.

 

[Chainsmoke]

• I usually find that full NSFW threads are ones I skip over/forget about. Sometimes I'm browsing while out and about and don't want to take the risk of seeing full-on porn embedded in a thread. NSFW links are usually more accessible to me - that way I can choose to view it. In the same vein, the different sized pictures completely take the focus away from the plots for me; I'm not really even able to focus on the content with so many differing image sizes/table sizes.

That's a fair one yeah! I just used a template that I found and thought was neat

• I think code words are silly, personally. People who are going to read your thread are going to do so regardless, and people who don't will be obvious from the start. Requiring a code word as another hoop to jump through is a bit of overkill in my opinion.

Hmmm, that's a good idea yeah, though I don't think I've even enforced it in the past few months, should remove it

• The double-first-post thing is a bit confusing — are you looking for the ideas in your first post, or in your second? Combining them might make it easier to read.

Oh that's because one is a mobile friendly post, both are the same

• The spoilers in the second post are a bit vague — it's nice to have plot titles, but I like having a bit of a blurb after them so I can see if the spoiler is even one I want to open.

I put it in a spoiler to make it easier to view on phone, or at least I think it helps do that.

Though overall, I might need to revamp my threads and how they look, though I'm not any good at formatting or making them look pretty

 

[Honey Blossom]

Oh that's because one is a mobile friendly post, both are the same

I meant more that the threads have two "first posts" in the thread — one with the table of images, and the second one with all the spoilered plots. Having to look through two posts on each thread might deter some people.

Though overall, I might need to revamp my threads and how they look, though I'm not any good at formatting or making them look pretty

I'm a firm believer that formatting should come after content and accessibility. It's nice to have a pretty thread, but having one that's easy to read and interesting is much more important.

 

[Chainsmoke]

I meant more that the threads have two "first posts" in the thread — one with the table of images, and the second one with all the spoilered plots. Having to look through two posts on each thread might deter some people.


I'm a firm believer that formatting should come after content and accessibility. It's nice to have a pretty thread, but having one that's easy to read and interesting is much more important.

that's all amazing advice! I'll start reworkin my thread, thanks for your help!