Post suggestions here!

Threads can get edited and greatly changed at any time, even after a thread has been approved - nothing we can do about that.

It might be a good idea to disable rating of threads that have not been approved, but commenting on such threads should stay. It allows people to point out issues that need fixing instead of leaving it all to the editor. As for unfinished threads: Do people even add such threads to stories that are not their own? The few times I have seen unfinished/in-progress threads they were added by the story's creator as part of setting up things.

Also, not-yet-approved threads do not show in the story map, so most people likely won't even see them until they are approved. But that reminds me:
Currently if I read an unapproved thread before it gets approved it does not show up in the story map as new (at most it can show up as updated). It might be a good idea for unapproved threads to not get marked as 'read' so that when the thread gets approved it will show up in the story map as new (green color) instead of read (white color).

 

Since threads can indeed be changed heavily even after approval, why can't such comments be made after it's been approved and dealt with then? At this point, this specific matter is rather trivial and comes down to personal preference, but I just don't agree with commenting on something that the editor hasn't even gone through yet. Just my own opinion, however.

It's happened a few times with submissions from other writers to my stories, so yes. Sometimes people write on the go and simply leave notes to the editor that they're not finished writing yet. Obviously, this isn't a common occurrence, but it does happen every now again.

Is that so? I've been seeing unapproved threads showing up in the story maps for my stories, but I wasn't sure if that was just because I was the story's creator or if that was how the site simply functioned.

 

Really? I've honestly never seen that happen, but I guess it happens occasionally.

Originally unapproved threads did show in the story map, but it was changed. Now you don't see them in the story map, and if you access the story map from a thread that has not been approved there's no mark showing where you are.

 

Maybe if only the original adder can do so. Right now anyone can, so you can have other people adding threads you want to accept onto a trash 2 sentence thread (as I did) forcing you to essentially rewrite the tread from scratch so you don't have to reject the followups.

 

In my opinion only the story owner and the original author should see non-yet-approved threads and should be able to add to them.

 

Ok, I'll change the behavior in this case. As a side note, unapproved threads can only be seen by users who are logged in, they aren't visible for guests.

 

What behavior? We talked about a bunch of things.

 

You're right. I wasn't precise. Here is a list of changes I'm planning:

• Ratings only possible after thread approval. Comments will still be possible (or we have to figure out another way how conversations between the owner and editors can be made)
• Rejected/Declined threads won't be visible anymore.
• Only the story contributors can add threads to unapproved/pending threads.
• Possibility to change the parent thread.

Another thing: What do you think about replacing the star rating system with a simpler (and probably more informative) like/dislike system, similar to YouTube's thumbs up/thumbs down voting system?

 

Wasn't there an on-site messaging feature on the way? Or did I misunderstand that and was it really just the forum in it's entirety? Not to undermine the forums as this message board is pretty amazing all around, just wondering if I had things mixed up.

Everything else sounds fine to me.

I personally don't see any problems with this. To my knowledge, most people usually vote with a 1-star or a 5-star, anyway, which is practically the same thing, really. I do think low-star ratings/dislikes should enforce some sort of commentary or criticism to be posted alongside it, though, to prevent any sort of harassment or trolling and the like.

 

or just notification about forum messages?



Maybe it would be good to differentiate between content and implementation

 

That's right. There will be a single messaging system. I was referring to thread-specific conversations. But if the messaging system is sufficient, we can deactivate comments while threads are pending as well.

 

That could be very handy, though I'm sure there's some users who still wouldn't bother checking the forums even if they were notified about it.

Maybe an e-mail option? The old Chyoo allowed you to send messages to someone directly through their profile page and it would show up in their e-mail inbox as an e-mail from the site. I'm assuming implementing this into Chyoa wouldn't be too difficult...?

Ah, I gotcha. I'd like to think the on-site messaging system would be sufficient enough to erase the need for comments on pending threads and for the e-mailing thing I just mentioned, so scratch that altogether.

 

Declined threads still show as "not approved yet". Personally, I would like rejected threads to only be visible to the author of the thread until they update it (so my view isn't cluttered by a bunch of threads I turned down and the author dissent want to change, not that this happens that often), but if it is going to stay visible to the editor even after rejection it should definitely say "rejected".

 

what about some kind of pm function

 

All pages on the site have the same title.

It would be helpful for navigating browser history if the different views had different titles -- front page, member page, story cover, (view) story thread title, edit story thread.

 

We are having some odd problems with mobile right now. The reports I am getting are:

1. The middle links (Discover & Explore, All Categories, and Chyoo Forums) do not appear at all on mobile

2. People cannot get the forums to work for the first time if on mobile. Seems to work if they already used it from desktop, though.

3. On small screen devices (phones, but not tablets), when composing a new chapter, the page will stop rendering after a certain scroll distance. Once you reach this point you can keep typing, but your text will be invisible until saved. Correction: occurs on tablets too, just after a much larger amount of text has been entered due to screen width.

All of these reports are from android users (Nexus devices). Can anyone confirm or deny? Apple users, are you having the same thing?

 

The cause for this is probably that only users who have confirmed their email address are able to log in to the forum.

 

That seems to be fixing #2 for most people.

 

Its the same on desktop, if the width of the window is too low.

 

I thought it was a mobile rendering issue (whatever object is being used for dropdowns not being compatible with mobile chrome), but maybe it's that the elements won't render if there is no reserved width for them.