I have been posting comments on sites for almost 2 decades now.
Why on earth should i have to read a manual just to post comments on this site?
Does it belong to the riddler?
Step 1: Make the text on the control (or next to it) say what the control does.
Step 2 There is no step 2
It’s impossible for you to say I’m wrong. You asked where Hawks quote was from. I answered. You appear to just want to rant. I’ll let you flail around now; I don’t feel like babysitting.
PS - noone is making you read a manual. Noone is holding a gun to your head. If you’ve used Discourse in the past, then cool; you don’t have anything to learn. I’m guessing you never visit new sites or use new software; there is a learning curve.
I have to step in here. I understand your frustration at having to learn a new system, but I’m not cool with you jumping in here and putting us down. We’re not ‘some little site-community’. We work really hard here to provide tools for you to use for free. If you don’t like it here, that’s cool, you don’t have to be here. If you do choose to be here then please treat us with the respect that we deserve.
Then I understand better why the comment system looks like it does.
And by “learning” your system, you actually mean accepting that it cant do the things the system it replaced could do?
Or perhaps you could take the opportunity to learn something about what your system looks like to a user who hasn’t used it before and learned to work around any possible flaws in the design, and who is willing to take the time to tell you about what doesn’t work?
Do you really only want feedback from users who like your system regardless of any flaws?
And remember, the clock is ticking…
For everything i “learn” about how to do things here, every secret handshake I figure out, every mysterious icon whos function I memorize,
…the more useless I get as a source of feedback for anything that might be wrong.
Respect and positive feedback only are two separate things that have zero relation. We simply look for constructive feedback (which you provided well early on and the rest of this topic is anything but constructive).
We’ve heard you. We don’t have an immediate solution. I can’t even tell you if we have a plan for threaded comments (but I can also say, I can’t tell you we don’t have a plan for threaded comments).
Yep, comes with the process of implementing new systems. We are bound to eventually come across a person who felt feature X was spectacular and the rest of us didn’t use it. It doesn’t mean we ignored you, we simply didn’t see it as “that big of a deal” from a feature list standpoint (read: content is king).
Warning: This may sting a little
Cool, point me to this person? As all I have experience with so far is the threaded issue in this topic, brief mention of “Reply as linked Topic”, and adding text next to controls (but which ones?) and several more posts about the same threaded issue in this topic. Again, we are looking for constructive criticism. Give us concrete examples, screenshots, etc. No need to go on a personal vendetta for 5-6 posts. We are reading your remarks, but once it gets repetitive, it doesn’t help us anymore (seriously).
Nope, and if you take the time to read a few other topics, you’ll quickly find we actually handled several key issues that a lot of our users came across. But they all provided good solid constructive criticism and worked with us to create a solution.
TL;DR
Seriously, if you can provide screenshots, mark them up with the design elements you’d change and how you’d change it, that is something we can work with. But right now, we are left to our own imagination which may or may not help you.
This type of feedback is what we consider constructive feedback and what we expect here.
One thing to note is that the forums have always been a much bigger part of Sitepoint than comments on the articles. The use of Disqus for commenting on the articles was a relatively recent and short-lived scene. Most of the people who are involved in the discussions here are those who have been involved in the forums for a long time, but there has been a disconnect between the forums and the articles that, at long last, these have been reconnected (as they were many years ago).
So whereas you see the move from Disqus to Discourse as “it doesn’t do threaded comments any more”, most people are seeing the move from vBulletin to Discourse as “it doesn’t do threaded comments but it never did anyway”.
That’s not meant as a criticism of either side, but as a bit of an explanation as to why people are coming at things from different points of view.
Yes, Sitepoint Forums is more of a community than a drive-by comment thread (which is why we’ve got the URL community.sitepoint.com); that doesn’t mean that we don’t want to welcome people who have come by way of the articles and to draw them in, and we need to make sure the comment system is easy and rewarding enough for people to get stuck in, but at the same time we want it to do a lot more than just allow people to drop comments.