Danbooru

Page numbering

Posted under Bugs & Features

Pointman said:

is it just me or now it's just next and previous without page number anymore?

It's one of the changes albert introduced with most recent update. It only affects regular members and anonymous. Perhaps it will be reverted, perhaps not.

Type-kun said:

It's one of the changes albert introduced with most recent update. It only affects regular members and anonymous. Perhaps it will be reverted, perhaps not.

I hope that canceled, because it is very uncomfortable. Dear administrator, please cancel it.

For me page numbers also disappeared.
Bug or not, may be related: I see everyone (including me) has "x in 1000000 posts" both for "Note changes" and "Comments", while x is true number. Occurred at same time with page number vanishing.

I want to also see this reverted. I can understand adding features for paying members, but to remove a long standing, useful feature from all non-premium members with no explanation is bad practice in my eyes.

DeadW@nderer said:

For me page numbers also disappeared.

Type-kun said:

It's one of the changes albert introduced with most recent update. It only affects regular members and anonymous.

You are a regular member.

DeadW@nderer said:

Bug or not, may be related: I see everyone (including me) has "x in 1000000 posts" both for "Note changes" and "Comments", while x is true number. Occurred at same time with page number vanishing.

That's the database having an error, generally when it times out on the query.

Click on the version number at the bottom of the page (v2.86.0) to see the change log:

For non-gold accounts, the following searches will use the sequential paginator versus the numbered paginator: multitag searches, any search with a metatag, any search on Safebooru, any search if you have hide deleted posts enabled

Sequential paginators are less taxing on the server, I believe.

I guess a workaround is to just keep opening the next page in a new browser tab so I can more easily keep track.
Though it's a shame the page numbers have gone from that page.

Also I'm not sure whats going on with "order:" that seems to be behaving rather strangely.

OOZ662 said:

That's the database having an error, generally when it times out on the query.

Normally you'd be right, but in v2.86 basic members will see 1000000 even if it doesn't time out. It's a result of the paginator change.

DarkDragoon said:

I guess a workaround is to just keep opening the next page in a new browser tab so I can more easily keep track.
Though it's a shame the page numbers have gone from that page.

Also I'm not sure whats going on with "order:" that seems to be behaving rather strangely.

Order is bugged with the sequential paginator.

I read that dozen of seconds after posting, OOZ662. Silly me...
Too bad, URL bar not shows pages either, but shows absolute number of first post of page instead.
Well, if this change have it's pros heavier than cons, so be it.

E: not actual number of page, but "N ± 1" depends if previously clicked "Next" or "Prev." (=aNNNNNN or =bNNNNNN). Some interesting simple formula implemented...

E2: If clicked "Next" URL shows number of last post in previous page with prefix b (bXXXXXX).
"Prev." button is inverted - shows number of first post of next image with prefix a (aXXXXXX).
Interesting feature: While browsing via "next" and "prev" pages will remain at same layout. If new post added upon reaching "first" page - there will be shown newly uploaded posts since hitting "index" page. Also loading "index" page will rearrange layouts to leave no space. Can't confirm with "deleted" post (numbering paginator was leaving hollow if there was deleted post on that particular page on search).

As I can understand - sequental paginator disables page calculation on server side and it don't need to reallocate posts every time when any page loaded, given ratio of numbers of "members and -" and "goldens and +". "Members-" can see hard 20 posts/page while "golds+" can be wary, so it may cause more calculating pages for members on server side.

But I think there is a hope: custom scripts and/or browser plugins theoretically can do page calculation on user's side, but it will be rather relative paging (eg. +1, +5 page of index at hh:mm:ss). There is also can be made custom buttons like "prev ± 5 pages", "first with or without reallocating posts". Only requirements: knowing exact formula (approximation of it's work made here) and knowing exact number of first "index" post.

Updated

DeadW@nderer said:

E: not actual number of page, but "N ± 1" depends if previously clicked "Next" or "Prev." (=aNNNNNN or =bNNNNNN). Some interesting simple formula implemented...

aNNNNNN means "the page After the post with id #NNNNNN", bNNNNNN means "the page Before the post with id #NNNNNN".

Pointman said:

is it just me or now it's just next and previous without page number anymore?

It's the newest gimmick to get people to buy gold accounts. At the rate things are going now it may be hard caps on max numbers of images viewed a day unless you're a gold member. This is setting a bad precedent.

Hurting base functionality for a what feels like nothing more than a cashgrab.

Although it makes me wonder if Gold Membership in the future might get features removed to increase the incentive for Platinum Memberships in a bit of a "Increased Chocolate Rations" kind of vibe if this keeps up.

Updated

Yeah, this isn't good in my opinion. To remove a very common feature just to put less load on the servers and keep that feature for more privileged users is just bad practice. Why not just apply it to everyone, including the admins, instead? What's worse is that this is on an independently run website.

Numbers still show up for searches with one tag, but not zero or two. For some reason.
There's no excusing this. If there's stress on the servers, then find another way to lighten the load. Preferably one that doesn't make the site look this bad, because god damn, this cash-grabbing could not be more blatant.

Updated

1 2