The context in which I use threadsuck make whitefont/no whitefont irrelevant. In other words, as far as I'm concerned to it either way.
'Out Of Gas'
Buffistas Building a Better Board ++
Do you have problems, concerns, or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Yeah, my feeling is kinda, if it's a huge pain to do, it's low on my list of "things to prioritize doing". It's a "that'd be nice, I've noticed it once or twice, but it hasn't killed me, just made me momentarily befuddled or spoiled and mostly for something I don't watch or since I was catching up, had already seen"
Fixed.
I'm curious about something-- why are Film and TV discussions "filed" differently when it comes to closed threads?
Every other thread is Closed Threads/Bureaucracy 2: Like Sartre, Only Longer, but closed tv threads are filed Film and TV Discussions/Closed Film and TV Threads/Buffy 4: Grr. Arrgh.
I notice it because I will unsub to a thread sometimes when I haven't had a chance to watch a show, and it makes it harder to find the thread when I want to resubscribe.
Fixed.
Yay! Thanks.
why are Film and TV discussions "filed" differently when it comes to closed threads?
Film and TV Discussion closed threads are a subfolder of the Film and TV Folder. Main folder closed threads are put into a subfolder of the main folder.
I'm not sure how it makes the thread harder to find--shouldn't it make it easier?
Film and TV Discussion closed threads are a subfolder of the Film and TV Folder. Main folder closed threads are put into a subfolder of the main folder.
I get that, I was just wondering why the Film and TV folders were set up differently
I'm not sure how it makes the thread harder to find--shouldn't it make it easier?
no, because I can skim immediately past any line that starts with "closed", whereas, I have to read into the line for Film and TV. Not a huge deal, just vaguely annoying.
Is it possible that there is something wonky with the Threadsuck option around post 15,000?
I was trying to threadsuck Natter (in order to pretend to at least skim, and not downright skip). I was behind (um, *way* behind) post 15,000, and it threadsucked only until post # 15,000.
I manually (clicking "Next") went past post 15,000, and when I tried to threadsuck then, it sucked from post 15,000 *until* the post that the threadsuck was supposed to begin with.
I repeated it several times, each at a different post # (larger than 15,000), and it happened each time. The first post sucked was 15,000, and the last post sucked was the one which was supposed to be the first.
I have no idea if this is my browser, Natter sticking out its tongue to me for skipping so much, or matzah crumbs creating bugs, though. So I turn to you for help.
15000 was hard coded into the program as a default ending post number if the user left that field blank. I just changed it to 99999 so it should work now. Thanks for discovering that!
I feel like I'm seeing the random quotes be not so random. It's possible that I just spend too much time on the site and am imagining it, but didn't we have a randomizing problem before?