|
Sincere thanks for your comment - and of course for the initial attempt.
It seems to me that popular threads eventually fizzle out, usually within a few days really, though sure, some go on for weeks. When they're resurrected they'll hang there for just a few days more, but all discussions like this fade with time. Discussions that go on too long, digressing into unproductivity, should be closed by the manager.
That some discussions become heated and remain at the top of activity isn't a bug or flaw. That's what people want to discuss ... until they don't want to talk about it anymore.
What you're describing is the notion that newer threads will have priority over older ones which people would like to continue discussing. That's like telling someone you're on the phone with that you need to break to answer the other line. The latest call is not always the most important one.
I respectfully request that this concept not be rejected, but re-visited, perhaps allowing article author/managers to determine how they'd like their group to function. Or at least I'm hoping that this topic be kept open for some upvotes and re-evaluation, as people are often discouraged from upvoting an idea that's already rejected. Of course in a short amount of time it will fall off the top and no one will see it again, so it doesn't need to remain open for long.
Thanks again.
|
|
|
|
|
Just my 2c, Chris.
Having been writing ToDoList for 10 years now, I often find that problems that once seemed intractable to me are more easily solved when I revisit them with fresh eyes and more experience.
And I don't doubt that you have developers on your team that are both bright enough and experienced enough to solve this issue, because it really is a big issue IMO
|
|
|
|
|
We've actually solved it, nicely, at the technical level
It's the "how to avoid the inevitable log jam" that's the issue.
|
|
|
|
|
No disrespect intended (sincerely) but if it's a great technical solution that doesn't work in practice perhaps a rethink is in order...
|
|
|
|
|
LOL.
I know what you mean, but I'm sure even you know that a great solution the solves every problem except a user's perception isn't such a great solution.
Did you red my not about thread stagnancy? Any suggestions on how to work around that? I'm all for adding back the mode, but don't want to stifle the discussion.
|
|
|
|
|
Give threads a "death date", which is the latest date by which they can be sorted... For example, if you only want threads to stay on top for a maximum of 3 days, the death date would be the posting date + 3.
Personally the only way I think this would work is that you only see the main thread in the thread list and have to click on it to open a new page that just views that thread. There are a lot of forums that work that way. Adding a "death date" would help from people bumping threads up.
Edit: After more thought, it really doesn't solve the problem, just mitigates it a bit. The only real way I see it is to give people the power to lock a thread when its use has been worn out, or let people sort by last post date or newest thread date.
|
|
|
|
|
I think reddit has a system that allows popular questions to stay on top for a longer time.
I once read something about it, but don't remember when and where that was. (Probably a link to a blog in the daily news )
The "importance" (the order in which they are displayed) is a combination of time + popularity (upvotes and/or comments). So many comments and/or many upvotes on a discussion increase the popularity of it. And now the catch: if the thread gets older an increasing amount of upvotes is needed to keep it on top.
so the popularity generated by a votes/comments decreases over time (preferably exponentially so you'd have a high influence in the beginning that slowly starts to fade away and you'd ultimately have the threads in the order they were added as the influence of votes/comments approaches zero)
I'm not saying that something like that is a solution for codeproject. It's just an idea of how to work around threads staying on the top for too long. I think the difficulty is: how to you prevent new posts from drowning in many popular threads? You'd probably have to experiment a bit with the factors like how fast does the value of new comments/votes decrease and how strong their influence is. And also probably: How do you prevent such a system from having to recalculate everything every few seconds just because someone upvoted a comment )
[Edit]
I think I found the post about reddit's ranking system: http://amix.dk/blog/post/19588[^]
|
|
|
|
|
In the product VAXnotes, there were three options used to navigate.
Next Note (here that would be next Topic)
Next Reply
and Next Unseen
In the case that a reply was posted to a topic from (long ago), Next Unseen would eventually get you there.
I do not really think that would be an option here though.
Reference linkity
Question on NEXT UNSEEN in VAXNotes[^]
!bVagadishnu
|
|
|
|
|
There's a reply button on one[^] of Nagy's posts in the Lounge, but I seem to lack the right to post a reply;
Items that need attention:
You do not have permission to perform this action
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
"The man" is keeping you down... the reply link works for me, at least I get to the page that I can post a reply.
Do you get this after you hit post, or just after hitting reply?
|
|
|
|
|
I received 2 similar emails whenever that user posted in the forum of my Combination in C++[^] article.
Please kindly look into it.
|
|
|
|
|
An Electronics Project, for things like Arduino, Raspberry PI, etc.
What says the hamsters?
Getting information off the Internet is like taking a drink from a fire hydrant.
- Mitchell Kapor
|
|
|
|
|
Interesting. Very interesting actually.
Can I get a hands-up from those who would like to post articles on hardware?
|
|
|
|
|
i'd like to read them, does that count?
|
|
|
|
|
I would post a few articles, I have a lot of .NET MF and Arduino stuff on my desk.
|
|
|
|
|
Are we talking about a new sister site or a dedicated article and forum section?
As it is now, you have to go here[^] and set your filter in order to find relevant articles. There might be other sections where articles are being placed as well (not really sure).
I would like to read (and try out) more articles like this: Raspberry Pi as low-cost HD surveillance camera[^]
DaveAuld has been writing some articles[^] and so has Marco B[^] and several others. I would also be interested in seeing what ledtech3 comes up with[^].
In short, I think there is an audience and sufficient contributors for dedicated article section and discussion forum(s). I like to believe I will be able to contribute as well (time permitting ).
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
I vote against another sister site (see my answer to Chris - source code is source code, and there isn't a sister site for Android programming, either).
I primarly find codeproject articles by using the Google search (My article on Arduino and C# comes up at the 3rd position on Google[^]), so no real need to change anything. Except a dedicated section for Arduino-ish and Pi-ish platform would be nice.
SoMad wrote: so has Marco B[^] and several others.
Veni, vidi, caecus | Everything summarizes to Assembly code
|
|
|
|
|
|
Chris Maunder wrote: we need to split "Hardware" and "System" out into two.
With the current rise of small platforms as Arduino and RPi are, definitely yes.
I think it would be also great if we could "outsource" all Hardware stuff which has nothing to do with programming into a separate category.
Veni, vidi, caecus | Everything summarizes to Assembly code
|
|
|
|
|
I'd stick with CP for this kind of stuff. Even though I have posted only a single article on Arduino, a new section as "Hardware near programming" for Arduino and similar stuff would be great.
A new sister site wouldn't make any sense, since a lot of the CPians are playing with Arduino and similar devices in their free time and in the end, source code is source code - There isn't a sister site for Android stuff, either. Take it as a chance to make CP less MS-focused and get it towards other technologies, too.
Veni, vidi, caecus | Everything summarizes to Assembly code
|
|
|
|
|
Both Hands Raised.
I am sure I asked for a couple of hardware section a few years ago for this very reason. E.g. add a section for Micro's e.g. RasPi/Arduino/Beagle/Parallela/a.n.other
|
|
|
|
|
I find it a good idea.
A bit off-topic:
I suggested some time ago a new section about automation programming (PLC, Robotics, HMI-Scripting and similars). You told it was a good idea, is it still on the queue? or has it been discarded?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
One possibility is that the author decided to remove it. Sometimes they just have to.
|
|
|
|
|
Because this: Teacher on call[^]
was my "featured article" today: implying it's one of the best articles we have if you are new to the site...
Perhaps competition entries shouldn't be eligible for "Featured Article" selection until the comp is over and the true dross has been weeded out?
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|