Based off of a suggestion @lou made about special tags, I wonder if would we could make a tag that is automatically applied when a lot of comments are added all at once and then removed when it reaches a more normal level of behavior?
Additionally, is there a roadmap? Interesting if site is open to everyone
In honor of starving artists everywhere, the topic for this thread is "scant".
@userexec won the last round of the Visual Weekly Activity. I don't want to steal the glory, but I also got ants in my pants. So this is an unofficial thread and hopefully userexec will chime in with a new official thread when they have time.
Edit: moved the user tag down so the main topic is more visible.
I'M ALIVE!!!!!
Sorry about that; my get up and go got up and went without me. I wandered out of funkland today just in time to be a week and a day late.
<_<
For this week, you may use any media you like - photos, sketches, paints, collage, et. al. to portray BLUE. In any sense of the word. Posting and up voting will cease when the 16th is over and done with.
If you end up with the most votes appreciating your piece(s), you will have the honour to decide the theme to the next week's thread! If that's not enough I'm sure I can find a gif of people grovelling in your magnificent wake. \o/
I'm currently using 24 hour sort, and it's great, minus one thing - threads older than 24 hours just disappear. Perhaps a better implementation would be to keep the threads showing up underneath the <24 hour ones, but prevent them from being bumped up by new posts.
Example - if I go to ~comp right now, there are only 5 posts. Older ones, imo, should still be visible, just no longer bumping.
I've been browsing Tildes a bit today and, overall, am enthusiastic about what I've seen. However, while reading a thread, a thought popped into my head that was evocative of an issues Reddit and other tree-based systems suffer from — thread freshness and activity over time both decay quickly.
While reading the thread, I thought "I would comment, but there already seem to be a lot of comments here. If I reply to a specific tree, then that limits people who might see it and respond. Even a top-level comment probably won't be likely to get much of a response."
On Reddit, this leads to repost after repost of the same content in brand new threads, as the activity level of a thread decays and the thread is lost. It looks like one way you intend to combat this is with different sorting methods (Newest, Activity) over various time periods (all time, last 3 days, etc.). Do users feel that this will be effective enough itself, or do they have other ideas to combat this issue?
The way I generally see it, linear threads often beat out tree threads when it comes to keeping threads alive without users having to read through a lot of crap to figure out what the current topic of discussion is, and where it's taking place. (Linear threading models to think of are phpBB, vBulletin, IP.Board, and their ilk. Tree threading models are sites like Reddit, Slashdot, or Shacknews. There are also hybrids, like Metafilter. Please share other examples and their pros/cons.)
In a tree system, I've often experienced the following sequence:
While in a linear threading system:
Alternatively, the linear threading sequence can also be:
An added benefit that is usually concomitant to a linear threading system is that threads are easy to "reactivate" (AKA gravedig) — simply add a new reply and the thread gets bumped up the stack for all users. This is not an exclusive benefit of a linear system. It could likely be made to work with a tree system too. The Activity sorting method may be related, though it's unclear how this functions.