The Glowfic Constellation

[Throne3d]

It's possible you'd counted the number of replies you'd read incorrectly (since it is replies, it does not include the main post itself – if you read off the stats from the site you're probably fine) and ended up getting the nearly-10,000 page? I'm not sure.

[DanielH]

I was reading off the number on the site.

Unless I had a typo (and I don’t think I did) or page=unread would go to an edited comment, I think I would have gotten the page I wanted.

[Marri]

Was that maybe the time you used two ?s by accident, and it crashed because unread?per_page isn't an integer? Probably worth another shot? I would expect it to be fine.

[DanielH]

No, this was less than a week ago. I’ll try again and get more details if something goes wrong.

[MaggieoftheOwls]

so if it's with rendered replies does that mean it's safe to do page=all as long as the thread is shorter than 1000 replies, or that page=1000 is also unsafe

[Marri]

I am tentatively unworried about things <= 1000.

Maggie, I know you used to use page=flat to review the thread; has the search feature been helping with that at all?

[MaggieoftheOwls]

It's still less convenient that loading the whole thread but if that is Problematic I can make do.

[DanielH]

I would like to second the reformatting the reply-search page. The big heading at the top of each result does not take me to the result in question. It would be better if it said “<thread name> #<index of reply in thread>” and went to the reply in question.

Edit: it can also check the per-page setting and say “page 5”, but still go to that reply.

[Moriwen]

The protections against double-posting interact frustratingly with my unreliable internet. 

I often type up a reply, hit "post," and have my internet go out before it can go through, so I get a "unable to connect" message from my browser. 

Previously, I could reconnect my internet and hit "try again," and my post would go through. This now takes me to "The page you were looking for does not exist."

I can also backbutton and get the textbox with all my text still in it, but the "post" button is now disabled, because I've already hit it once. It remains disabled if I refresh the page. Hard-refresh undisables it, but that of course gets rid of the text too.

This means that every time a post fails to go through, I have to backbutton, copy the text, hard refresh, paste in the text, sometimes restore formatting, reselect the icon, and try again. This isn't the end of the world, but it's kind of annoying to do on a regular basis.

I don't know that there's any easy fix that doesn't sacrifice other people's functionality (double-post protection seems like a good feature to have), but if there is one I shall be pleased about it.

[Unbitwise]

Technical kibitzing: Double-post protection should be done on the server ("I see you already submitted a posting form with this particular ID I generated, so I will ignore/replace it”), or not at all, not by disabling buttons in the page, for exactly the above reason.