I don’t think so… we do allow necrobumping for the sort called
New Comments, which is essentially a forum sort. And that’d be extremely useful for question and answer type communities.The default 2-day bump limited
ActiveandHotsorts keeps things fresh, and makes it feel like a news page, but the other sorts can turn lemmy into a forum, or who knows what else.Slightly off topic but…
Is a sort like “active since i last logged in” possible, of planned?
… Ignore if too off topic.
No, but we have a hide read posts option in your settings.
I like that idea a lot 👍
Hmm, on the one hand Lemmy doesn’t move old posts to the top again unless there is a lot of new activity (so no “necrobumping”) and still being able to answer a specific question of a user after some time seems good to have.
On the other hand, community moderators might easily overlook spam and other bad content posted later in threads (as they are not bumped up to the top as in regular forums) but that bad content would still show up on searches. So from a moderation perspective it is probably helpful if threads get closed automatically after a while…
We do have a sort that allows necro-bumping, called
New Comments, which is basically a forum sort. It would be ideal for use in 101 / question / answer type communities.
I think letting the communiry moderators decide that would be good, since some communities like support ones would benefit, while there’s no reason not to archive posts on some others.
Some topics may evolve really slowly over time. it’s more compact to have a single post for a long lived topic than to create many posts with just 1 or 2 comments in each. Thought i am new to “lemmy.ml” i didn’t see any huge posts here (yet).
Automatic close after 6 months + possibility of longer as need may be.
I completely agree with your first point. I can’t count how many times I have visited a forum and found a thread that is answering a question almost identical to mine, but is missing one key piece of info that I need.
I hate to make a new, almost identical thread for a simple bit of added info. I honestly can’t think of a good reason in favor of time locking a thread.
If we had to however, I think your 6 month + longer as needed approach seems the most reasonable.
i stole the 6-month idea from :
Travis Skaalgard https://lemmy.ml/u/tskaalgard in present tread. He says Reddit does it. As a rule of thumb, when a big player does something, there is a good reason. Maybe this reason does not fit in here but i wouldn’t know that.
deleted by creator
Maybe in the future if the service becomes very popular a la reddit with more traffic.
Agreed. As far as I’m aware gravedigging old posts hasn’t been an issue, yet. Maybe once a thread has been inactive for a 3-6 months a confirmation screen could be displayed explaining that the thread is inactive and users should only post if they are contributing something of value to the discussion.
Reddit archives stuff after 6 months but I never understood why they did this
I remember them saying something about not wanting to have massive threads with hundreds of thousands or millions of comments, like how some long-term BB forum threads are. I wonder if it’s due to the possibility for server strain since Reddit (and Lemmy) uses a nested commenting system that needs to be loaded recursively, or if it’s just a decision about the “style” of forum they want Reddit to be.
Not a lot of people are fans of “necroposting” (if memory serves right, it means to post on a thread after being inactive for a long while). Worst yet, it’s probably less likely you’ll gain any responses from the same people that have posted in a thread long ago or from anyone really. I think if the time limit is not too long and not too short (so as to cover both bases) like say… 3 to 7 months till the post becomes archived, then it’d be acceptable. However, it’d be cool if instance maintainers get to control that feature since I’m sure they won’t be all agreeing on the same limit.
Is there a time limit the lemmy devs/admins have agreed on so far?
I am not sure:
Imagine a problem with kernel Linux 5.10 right now.
I am using the oldest LTS version always and, in 2 years, I finish in version 5.10.
I didn’t read the post of that version in that time because I didn’t need it, but now I need it and happens that anyone replied a workaround that works for me and want to ask again.
Why should I open another thread and expect people to unread that one (even if I reference it in the new thread most people will ignore) and post likely the same unsuccessful replies now?
Could happen the same with a discussion around a topic, people recycling arguments already discussed again and the situation goes to a no point.
Edited:
Could this be set depending on the community?
Worst yet, it’s probably less likely you’ll gain any responses from the same people that have posted in a thread long ago or from anyone really.
The person commenting an old thread should be aware of that, so I don’t see what forbidding them to comment helps with.
It also depends how a newly commented post is highlighted in usrrs’ feed.
The person commenting an old thread should be aware of that, so I don’t see what forbidding them to comment helps with.
See, the thing is, not everyone keeps that in mind before posting in an old thread. I’ve also made the assumption that the user expects a response from the og posters and/or OP, which might not necessarily be true.
I do understand that, but forbidding everyone to answer the thread seems like a radical solution for this mild problem. Maybe a more appropriate solution would be highlighting the age of the post and of the last comment.
So far there is nothing like this implemented, thats why i’m asking. And yes the (default) time to close threads automatically is also an important question.
Why should they?
Yes. I think at least a month with zero activity should be closed to keep the communities that are on lemmy current
And it also stops people from owning a community to just own the name.
This one isn’t too much of an issue, because now we sort the communities by active users within the last month, on the communities page.
