The site's going to run into a problem where content is going to become lost soon. The page count only shows up to page 2,615 (making it look like the oldest posts are 5 years old) when in reality we have posts running back 13 years.

These pages are only accessible if you know they exist and manually enter them in the search bar; and the website doesn't let you go beyond page 4762. The site currently has 4576 pages of posts, meaning we only have 186 pages left before the old content becomes inaccessible.

Right now, at the pace stuff is being posted, that's about four months away.

This feels like an engine glitch to me (I mean, obviously, but) - and it's odd that Hub experiences this when I don't believe Gelbooru does.

This is like that Y2K thing.

And if you search * or a space character, it breaks by going too far

It seems like the limit is 200000

You can also search for the oldest posts by using sort:id:asc so it's not like it's lost forever

My coder brain be like "So this is effectively some weird variable issue that could be solved with changing the type of variable to something bigger?"

This doesn't seem to work for me, it still won't let me go beyond page 4762

> You can also search for the oldest posts by using sort:id:asc so it's not like it's lost forever

That's a good point. Looking into it more, it looks like you can also use id:>*ID* and/or id:<*ID* to filter for pages that are inaccessible other ways.

A few years in the future, once the hub passes ~9,500 pages, stuff in the middle won't be accessible with sort:id:asc or sort:id:dsc; so searching for a specific range like "id:>123456 id:<200000" will be the only way to see them

Don't they also show up if you search for a tag or other feature of the post? I may be misunderstanding?

If I get you right, then the issue is pretty specific. Most people don't just browse content, they are looking for stuff they are into.

It's important for a subset of people who go onto imageboards window shopping. And I'm not saying that doesn't matter, it does. This site is held together by glue, and a lot of things on it need a tune up.

But saying images are going to be lost is a tad dramatic. They are just, like, gonna be mildly inconvenient to find for a percentage of users.

Even if one tag has enough images to ever go over the limit, one or two additional tags in your search will eliminate the issue entirely.
Unless the site continues to exist until the Sun goes red.

You need to be pretty optimistic to worry about That, if you think about it! :D

This doesn't affect our favorites, does it?

In theory, yes, but many of the older posts [and plenty of the newer posts] on this site have incomplete or extremely minimal tagging. And once a tag has too many pages it'll also be affected by the site's page limit.

> But saying images are going to be lost is a tad dramatic.

It's not too dramatic. Fortunately the trick of ID Sorting does work, otherwise without it you'd likely miss lots of older posts that are quite good.

Just as an example:

hypnohub.net/index.php?page=post&s=view&id=640

"Strawberry Marshmallow" only has two images on the entire site and the rest of the tags are used tens of thousands of times, the odds that you'd run into this image without being able to browse older posts is kinda unlikely.

hypnohub.net/index.php?page=post&s=view&id=34

And this one doesn't have any copyright tags at all to help locate it.

..hm, you know what? You've swayed me.

I Am only speaking for myself when I say I diligently tag old posts, and that's only when I feel like it.- .

Fortunately, I may have a partial solution for you. Give me a day.

As I believe kids of this era might say:

Let him cook.

I am pretty certain Gelbooru uses a much newer version of whatever booru codebase the Hub uses. There are a lot of differences and improvements there that just aren't here.

Bro's got the kitchen, let's see what he cooks

the cooking occured. I present Hypnohub...is Old.

mega.nz/file/AxgymK5K#IIN...0msdimhaid48-C87flfhanCkI

It's a static version of hypnohub's post browser. I cut out the javascript and some other chaff, then made the CSS internal.

It includes no images, all the previews you see when you open it are referenced from the original site. Every link that remains leads back to the original site as well.

This version is just a proof of concept to show the less tech-literate that it can be done, and pretty easily. I did this in a few hours between my day job and a major outage, and that was before I knew where everything was. That should give you the feel it isn't difficult.

It only shows the first page for now, but it should be trivial to automate a process that adds as many pages to it as we like, and browse them exactly as you would on the site.

It's more a question what form people would like the final version to take.

It can be local, like this example, which is probably the easiest and will take me a couple of days of mucking around in powershell. Plus you would need to download a new version now and again. (I can make an updater for it if that is an issue.)

It could be its own website. Each page would take up around 80 kilobytes, + 20 for the CSS, and it's static, so it could be hosted on pretty much any free service.
Much as I am mad at SlayerDuck, I do not want to steal his money, so we would have to be careful to only include pages the hub no longer can display, if we go with this option.

It could be integrated into the userscript, though only regular visitors use that thing, and it's Detour's baby, so I'd only do that if everyone including him agrees to the idea.

Finally, it could be its own standalone script, or running off Tampermonkey. This would be the hardest since I'd have to learn something I do not already know how to do, but it's just scripting, not coding. Shouldn't take 3 months, in any case.

---Well, I guess it's also okay to say none of these are appealing to you guys, and tell me to go somewhere the sun don't shine. I didn't spend much time on it yet, I'd take it on the chin\ <w > /


What do you think? Would it help?