>>5798
damn, nothing on this incarnation of the site is more than 3 years old, that's some pretty fast becoming-embarrassed-by-your-younger-self right there.

>>5799
Hopefully that's some proper kind of markup, not that "markdown" bullshit that never works right even when you try to use the actual code, and visits all kinds of generalised destruction on any copied-in text or everyday ASCII-assuming typing which may have asterisk/underscore/etc emphasis included amongst other things...

As for the links, I'd suggest a bit of lightening and desaturation (so it doesn't actually go full brightness on the red channel), so it's actually more a sort of greyish pink but still looks fairly red in comparison to everything else? I'm using the light theme right now but I assume "light blue" isn't full primary blue (itself difficult to red against a dark background) or cyan (a bit glaring) but a more pastel sky colour anyway, so its reddish counterpart might work just as well.

With the editing thing, the fairest might be something like the IP which submitted a thread can delete it afterwards (in order to repost it with corrected title/text/etc) for an unlimited time if no one else has posted (even if they have themselves submitted multiple posts and then realised the OP had a glaring mistake), and maybe for 10 minutes after the first post by another user/IP, after which it's fixed except for Mod intervention. I've never known an imageboard of this type to offer any kind of editing beyond simple post/thread deletion followed by reposting, and I'm not sure how you'd implement it without adding in whole extra modules (instead of just adjusting the permissions setup).

>>5806
Is there a way to get the aforementioned autosageing thread restored to normal life in that case, or does the post limit remain, with it simply saved from being deleted by falling off the bottom of the threadlist quite as early?

>>5807
^this

>>5828
That's a handy way of catching up on what threads may have changed, though usually they still have at least some of the text title and last post date. I think the most useful one I saw however was a rather simpler, yet more comprehensive type which just showed a reverse-date-order (ie newest to oldest) listing of each uploaded image for the entire sub-board (/g/, /f/, etc) as fairly small, fast loading thumbs with a timestamp and short version of the parent thread title underneath, 100 or so to a page. Good overview of what the freshest stuff from the whole section is, especially if your last visit was only a day or two earlier and you can therefore maybe reach what was newest last time you were on within the first page. Somewhat like a *booru frontpage, but a little more organised and without it being the default interface.

>>5844
This does annoy me a little, but I think that's a universal interweb problem, unless it could be fixed by e.g. adding (individual thumb appropriate) width= and height= fields to each img_src tag... or even just height, in fact... so the browser can reserve the space in the document framework. Seeing as they can be individually or collectively expanded from thumbnail to full size (or at least as large as will fit horizontally?) without reloading the page (thus dynamically changing both the source of the image as well as the height/width), however, there might be some kind of CSS or Javascript spanner waiting to fall in the works there.

What browser do you use, btw? For me, Chrome, and especially the mobile one doesn't seem to load (or at least bother to render and figure the size of) images until just before they scroll into view, first time round, so if there's a bit of loading delay - here or on any other site - I can hold "End" on the keyboard and wait for it to herky-jerk its way down the page without too much spurious data loading or stretching the overall page length out. And once it gets to the bottom, it "sticks" there with any further loads causing the centre of the view to drift upwards (ie it remembers it's "at the bottom", or maybe "X percent down the page", instead of the rather more troublesome "Y pixels down the page"). However, hitting the "expand all" button does mean it then comes adrift, which I don't quite understand, but as usually I'd only bother doing that in order to hurridly archive the entirety of a thread page (instead of picking and choosing), that doesn't matter so much.

3mbit isn't so great, sure, but having browsed similar sites on 512k and my current connection seeing to vary between 8-20mbit (mostly the lower), it wouldn't say it's terrible either. It's probably about what I get with my phone, both on wifi and 3G, thanks to the low power transceiver... Seeing as the median image size I figured further above was under 300kb, after doing an expand-all, that's better than one image per second on average, though the biggest ones will take a while (some were up to 6mb, so a remarkably dial-up-esque 20 seconds?). Dunno how big the thumbs are, data-wise, but I'd expect it to be maybe around 100kb each, including for the ones that are huge once expanded. And the non-image data itself should only take about 1 second to load. Take heart :)

Though a solution to this could be to have a clickable option to just swap oldest first / newest first. It fouls up the flow of any ongoing discussion, but otherwise should be fairly intuitive, especially as that would fit with the catalogue / booru-like layout if it was restored and you used it.

>>5845
That sounds like a pretty decent way of working things.
Can't remember which particular chan I saw it on, but an option set that has gone before is having, on the thread header list, a trio of "first 100 posts", "last 50 posts", and "show entire thread"... something like that anyway. So you could either read the thread from the start in manageable chunks if it's new to you, see the more recent few dozen if you're familiar with it - being able to jump back and forth in chunks from there, or see everything together if you want that for some reason (also being able to switch to that in-thread after opening it a different way). Given the way the threadlist and previews are arranged on GC this might be a bit trickier to do in an efficient way (it was on some more traditionally set up chan which didn't have the summary list at the top of each sub-board page, I know that much), but still worth investigating.
Even if it just loaded the last 50 by default, if this was made obvious to the casual browser, and the navigation back and forth / expansion to the full thread all at once was reasonably easy, that would work fine itself.


.....phewwww
right, off to the everyday normal world for another few weeks.