So I know a lot of chan-type boards have an autosage feature which occurs once a thread hits a pre-determined post limit, but I'm a bit unsure if Uboachan does as well. It seems autosage likely is implemented though, since there have been various threads not bumping; mostly longer ones in /fg/, I believe.1 post omitted. Click reply to view.
Basically, what I'm wondering is whether it seem like a good idea for autosage be in place on Uboachan. Since Uboachan is much less active than many other imageboards, it may help increase activity if autosage wasn't in place, or if the bump limit was at least increased on certain boards. At the very least, it may make sense to change it on a couple boards, such as /fg/, where it makes less sense to create many new threads, especially considering Uboachan doesn't delete threads past a certain page number. As it is now, when a game which garnered more discussion has an update, it either gets overlooked by many due to the thread not bumping, or a new thread needs to be made, which seems to rarely occur, at least in recent years.
The bump limit on /fg/ is already 10,000, or effectively infinite. There should not be any issues with bumplocking. Please inform me if bumplocking continues to occur.
Thanks for checking. It's good to know there isn't a sage limit on /fg/.
While I haven't noticed any newer threads not bumping since this topic was made, it still seems to be affecting older threads, since I made a non-sage post in one of them just a few minutes ago, without it bumping.
Here are all the threads that seem affected (at least, judging by the date of the last non-sage post):
DebrisPost too long. Click here to view the full text.
It is a timeframe based problem after all. I have manually removed the bumplocks from all of the threads that you linked.
Hmm, that simple, huh? Good to see it was an easy (if slightly time consuming) fix.
I only tested it with one thread (last thing we need is a bunch of bumps due to test posts), though it's probably safe to say all the listed threads should be fixed now. I'll let you know if I notice any threads not bumping, though.