I have already commented on a couple 2-4 year old posts by accident
Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
Doesn't help that posts that old are popping up under some sorts they shouldn't be showing up in. Hopefully that glitch gets resolved soon.
I looked into it a couple days ago, seems the fix has already been done. I’d predict it comes next update.
Depends on your instance. Some cache needs to be cleared or something.
ahh the Hot feed
Not today and hopefully never for general forum purposes. Worse case, you get somebody that necros an old post akin to responding to an old email chain, or replying to an old forum thread. Usually not a big deal but sometimes it also sparks new discussions if that post/thread had some meaningful content.
Edit: Actually I think @[email protected] had the best idea. Would be a great option depending on the forum / poster's need. There are some good reasons when you want to "mark a thread as closed"... like bug reports, project tasks, etc. But I feel the default behavior should be to keep post / threads open.
The code currently doesn't have any timed locking feature. Perhaps one day, but not any time soon I would guess.
Personally, I'd like it if it could be set by community or poster: They could allow it to expire after X time or just leave it open indefinitely with a setting.
Long term, that's a decent idea - Mastodon and related platforms generally have a function similar to that, and it saves me scripting "Retrieve post, edit post, replace with '.'"
I never really understood the purpose of it.
Like, I don't know whether the aim was to address some sort of abuse, or whether it was to reduce Reddit's storage costs in some way or what.
A few guesses:
- it stopped the OP being forever notified of comments on everything they've ever posted
- force conversation into the "fresh" post (reposting on Reddit was allowed even encouraged, I suppose it's clear their purpose was to drive engagement at the expense of being spammy and repetitive)
- reddit's search was shit so I guess you would get a dozen results for a news headline some unrelated and old and it was to stop people commenting on old threads by accident? I dunno