Or we could make all links outside links ...
The problem that was discovered with caching would be less of one with threadsucked pages, because it's unlikely that one is going to threadsuck from the same post twice at different ages of the thread. But it should be noted in the cases where one does, we weren't able to find a caching mechanism that didn't require you to force a refresh the second time to see new content.
If we can find this caching that doesn't need forcing, I think we should implement it on all content.
The complaints we had when we did try caching pages were about the home page and message center not updating.
Which I think is a bigger detriment to usability than not caching, in my estimation.
Probably. However, if we could apply it to individual pages, that would be ideal. If we can't, is there a way to force the home page and message center to refresh every time they're entered?
is there a way to force the home page and message center to refresh every time they're entered?
Last time's jiggling didn't reveal one, other than leaving them as is.
Do we need any more domains? Domaindiscover is offering us registration at $8 a pop.
I'm going to be prettying up the html on some new pages ita's been working on. Question: Should I still care about Netscape 4.x? It requires significant additional work. Does anyone still use it here?
Scroll down for the browser usage stats. NS 4 doesn't appear on it, but I don't have those precise numbers here -- they're at home.
I don't have those precise numbers here -- they're at home.
Could you check later? ta.
I've tried threadsucking the last 600 posts or so in Natter four times now, and I keep getting the header without any actual posts. I was able to threadsuck a smaller amount--is this likely my browser?
