Log in
| 1 | ||
| 1 | ||
| 1 | ||
| 1 | ||
| 1 |
https://img.gvid.tv/i/YDdDuNZ8.png
Instead of listing all xposts, make a feature where you can post to a "main" sub, then list some cross posts subs. In the "general" feed, it only shows once, with the main sub listed, but a hover element next to the main sub lists all cross post subs.
When viewing individual subs, the post shows as normal for whatever sub you are in.
To be clear, I'm not complaining about xposts, but with a site this small, why would you not just be browsing new at all times? The cross posts are useful for those with a particular interest, but make new cluttered.
The front page does condense cross posts. /new doesn't. But obviously the cross-post finder page is going to list them all out because that's the job of that page.
I'm trying to think what that would look like graphically.
I think the premise I was operating on when I didn't apply that to /new was to make sure there is a page where someone can see all the posts that come into the site. I'd also have to figure out some kind of way in the database to indicate that the sub is more "main". I could possibly make use of the time field, setting one of them a millisecond newer than the others.
Also the other way to do it is to use the custom sort to set age as the only factor. Then you can have /new on the front page.
Keeping a little bit of bump on might be good to catch conversations that are happening in older posts. Some of our threads like movie stuff will have conversation in them for a while.
I have the age factor set to max, and the others set to zero. It generally shows them like new, but they are out of order. 3 hour posts after 8 hour posts, etc.
It's nice that custom does this, but it's far from a true "new." Not a big deal, I will work around it.
I see what it is. When a new comment is posted to a post, it considers it "new" and breaks the true post age order.
An interesting concept I'm not sure I like. Generally, I don't care about some inane conversation someone is having.
Again, just my thoughts, no big deal.
It should only be impacted by new comments if there is still bump on. But I'll also take a look.
The bump is to make it more 4chan like. I wonder what browsing 4chan would be like if you only saw new threads.
Edit: Just tested age only. It looks pretty in order to me.
https://img.gvid.tv/i/3zxaN7uc.png
Do I have the settings right? It still seems to be bumping via comments
https://img.gvid.tv/i/3NGzECkg.png
The page, with those settings, after my previous comment. If this is expected, then maybe I misunderstood you.
That does seem to be acting as if 'bump' is on. Did you refresh after setting the settings?
There is a slim chance the changes didn't hit the database. This isn't a usual case but some of my stuff on the server is getting very popular and I'm in reaction mode. For a second one of the drives on the server ran out of space just from massive logs being produced, so something may have not gotten written to DB.
Try fiddling with the bump, up and down, just to send some bump attribute updates to the server and then refresh.