Conversation

oops. are you still seeing that? I held some trials during the weekend that may have been pushing things over the limit, but I've settled on something that I think is likely to be more in line with common use

I was more worried about the sequential downloading of pages, because each one takes some 10 seconds of server processing and then a while longer to download, but AFAICT the problem of too many requests came up when I concatenated a few hundred pages (about a week's worth of posts) into a single file and then attempted to open it in the browser. tons of requests for pictures and whatnot all at once. that won't happen again. sorry.

thanks for the suggestion; infinite scrolling is really only part of the issue, and I do use explicit paging to overcome some of the annoyances, but it's not enough

some the problems are arguably bugs in GNU social:

- if fetching the next page fails, the page dies and won't retry the fetching

- if you leave the page alone for a while, next posts appear out of order

- if you reload, you don't get back to where you were, and the longer you wait, the farther away from it you get

- there's no marker of how far I got last time, and threads bubble up to lower-numbered pages as new replies arrive

- finding where I was after a failed fetch, a reload or restart takes a long time as each page takes a while to fetch, and that's unsuitable to automation

local 8h files, no waiting, working reloads => happy camper :-)

Public

Notices

Feeds