dba_afish said:
I feel like having it as a news announcement would be a bit overkill for moderately sized updates like this. I don't think that absolutely every user (including ones who aren't logged in because news goes to them as well), necessarily, needs to know about every change before it goes live. it's liabile to just end up with a thread like this if we did.

If you don't broadcast it via the announcements the people will still complain about not having a heads up all the same. At best it'll only decimate the number of complaints

snpthecat said:
If you don't broadcast it via the announcements the people will still complain about not having a heads up all the same. At best it'll only decimate the number of complaints

yeah, but at least some of the complaints were things that most of us had and were repeated several times in the noise before being fixed. and also, reasonable statements were sandwiched between easily-ignorable doom and gloom.

having a grace period between reasonable review and annoying bullshit is probably a good idea.

dba_afish said:
yeah, but at least some of the complaints were things that most of us had and were repeated several times in the noise before being fixed. and also, reasonable statements were sandwiched between easily-ignorable doom and gloom.

having a grace period between reasonable review and annoying bullshit is probably a good idea.

Fair

WELL, the site has been updated once again, now about this new way of searching for tags, which, based on the tag I searched for, even informs me about what that tag will show.

But, like, it's not a criticism, in fact, I even liked it. However, in this business of researching about the tags, I wish they had more of all the new posts, like, instead of putting 8k, 11k, 1k, And I believe it should have the whole number like, 8,235, understand? Instead of leaving only 8k, that way we will know if something new was posted, instead of going into the tag to find out.

This is just an idea, if anyone else thinks so, comment here, or if not, comment too so I know if it is viable, or if it is a bad idea, for example... And a number with more digits? It could be confusing, right? Or not.

Is there’s a option to disable the wiki page displaying when searching for something, if not, then it’s useless.

it’s nothing like other booru sites like gelbooru and rule 34, some of the features are unnecessary, the website looks horrible on my iphone 13, the pages and the thumbnails are too small, it’s sucks cuz i use this website as my fap material.

sksjsjsjjs said:
Is there’s a option to disable the wiki page displaying when searching for something, if not, then it’s useless.

.wiki-excerpt { display: none; }

add this to the CSS section in your advanced settings

manitka said:

.wiki-excerpt { display: none; }

add this to the CSS section in your advanced settings

Thank you, I really need this, but I also want to make the thumbnails big.

and now there is tag description when one goes look for posts with said tag, not gonna lie, i disliked it, it feels intrusive layout wise and condescendent,as if the user is too stupid to understand what the tag in question is

eranormus said:
and now there is tag description when one goes look for posts with said tag, not gonna lie, i disliked it, it feels intrusive layout wise and condescendent,as if the user is too stupid to understand what the tag in question is

A good number of tags may not be very clear, especially if the user tries to search for something that's aliased to a disambiguation. Tags like humanoid are routinely misused, and tags like nude are regularly misapplied to ferals, as examples. Having the wiki excerpt and link available will help allow people to more easily look up the definition of what they're searching, to explain why they may be seeing or not seeing what they expect. In either case, the excerpt can be collapsed (click the name or arrow icon) so it's only a single line with the search term, or a line of custom CSS can remove it entirely.

sksjsjsjjs said:
Is there’s a option to disable the wiki page displaying when searching for something, if not, then it’s useless.

it’s nothing like other booru sites like gelbooru and rule 34, some of the features are unnecessary, the website looks horrible on my iphone 13, the pages and the thumbnails are too small, it’s sucks cuz i use this website as my fap material.

Didn't you leave the site like 4 times at this point?

I like tag explanations conceptually but maybe they should only display the first paragraph initially, or be a drop down. If the wiki page is like 1 or 2 lines it looks pretty bad (center justified read more covers too much up too).

Tag explanations should be off by default on mobile though. It just takes too much real estate.

manitka said:

.wiki-excerpt { display: none; }

add this to the CSS section in your advanced settings

Ah thank you as well for this, that woulda been rather annoying to see on every single page when tag searching, as I saw it wasn't only on page 1 but followed you to later pages.

Honestly, really cool!

I want an e6 "classic" setting, the new info bar thing is annoying me and the new home page keeps making me hit the button underneath because I have YEARS of muscle memory built up.

I didn't have a problem with the new stuff until this most recent update. On the 'Posts' tab, your Search History Autocomplete Suggestions don't populate when you click the search window (on mobile, at least). Been using that functionality for years at this point. Your Search Suggestions populate on the homepage when you click the search window; it's just under the Posts tab that it has stopped functioning. Is that intentional?

tamaneko said:
I didn't have a problem with the new stuff until this most recent update. On the 'Posts' tab, your Search History Autocomplete Suggestions don't populate when you click the search window (on mobile, at least). Been using that functionality for years at this point. Your Search Suggestions populate on the homepage when you click the search window; it's just under the Posts tab that it has stopped functioning. Is that intentional?

?

as far as I'm aware, that hasn't functioned like that since 2019... and this is the second person to bring this up. I'm-- I am so confused.

dba_afish said:
?

as far as I'm aware, that hasn't functioned like that since 2019... and this is the second person to bring this up. I'm-- I am so confused.

re6 functionality? Idk that's the first thing i jump to when they complain about something that isn't present in base e6

cinder said:
People keep saying that, but it's just factually not true.
The UI was reworked to make it functional on mobile. And people have complained about it, yes.
No, there will not be an option to revert back to the old version.

I am so fucking sick of websites doing this. Shitting up the desktop experience just so it's better for mobile users.
Especially since I thought you could have both mobile and desktop versions of UI anyways.

On to my own feedback about the changes:
Not very big on the account button being moved. It being all the way to the right isn't obvious. It's arguably out of place considering everything else is bunched up the the left.

watsit said:
A good number of tags may not be very clear, especially if the user tries to search for something that's aliased to a disambiguation. Tags like humanoid are routinely misused, and tags like nude are regularly misapplied to ferals, as examples. Having the wiki excerpt and link available will help allow people to more easily look up the definition of what they're searching, to explain why they may be seeing or not seeing what they expect. In either case, the excerpt can be collapsed (click the name or arrow icon) so it's only a single line with the search term, or a line of custom CSS can remove it entirely.

As valuable as this might be, there has to be a better way. Maybe a quick popup(similar to how mousing an avatar over shows tags & other post info) after you enter or search a tag. It's way too obtrusive to not be a toggle setting as it currently is, frankly. Most people who use the site aren't going to know about the custom CSS box, much less how to use it.

popoto said:

Most people who use the site aren't going to know about the custom CSS box, much less how to use it.

Neither are they to know about themes/gestures but ok

snpthecat said:
Neither are they to know about themes/gestures but ok

No? Custom CSS is hidden at the very bottom of the advanced settings section. Themes/Gestures is shown at the bottom of every page.
You're going to be visiting the former section maybe once or twice to get the website how you like it then never again.

tamaneko said:
I didn't have a problem with the new stuff until this most recent update. On the 'Posts' tab, your Search History Autocomplete Suggestions don't populate when you click the search window (on mobile, at least). Been using that functionality for years at this point. Your Search Suggestions populate on the homepage when you click the search window; it's just under the Posts tab that it has stopped functioning. Is that intentional?

Having the same issue.

I also encountered the problem of not retaining the original search terms when clicking on a new search, which made me very distressed because I have always used this method to filter my favorite character images. Not retaining the search terms means that I have to spend more time copying and pasting the existing ones

thisorthat said:
Having the same issue.

What exactly is the issue though?
The site does not have a "search suggestions" feature. We do have autocomplete, but that does seem to function normally.

cinder said:
What exactly is the issue though?
The site does not have a "search suggestions" feature. We do have autocomplete, but that does seem to function normally.

They're talking about browser behavior and mistaking it for site behavior.

MDN page on <input type="search"> says:
In addition, modern browsers also tend to automatically store search terms previously entered across domains, which then come up as autocomplete options when subsequent searches are performed in search inputs on that domain. This helps users who tend to do searches on the same or similar search queries over time.

potentialgoat said:
They're talking about browser behavior and mistaking it for site behavior.

but that's been overwritten by the quick-complete menu for like 5 years, no?

dba_afish said:
but that's been overwritten by the quick-complete menu for like 5 years, no?

IIRC, it was fixed/brought back when you had the site's autocomplete disabled in your settings.

watsit said:
IIRC, it was fixed/brought back when you had the site's autocomplete disabled in your settings.

Confirmed, just disabled auto-complete and my search query based on keystrokes never shows up. It wasn't like this two days ago and I had a Chrome update before that 4 days ago. So this is a site thing as far as I can tell.

manitka said:

.wiki-excerpt { display: none; }

add this to the CSS section in your advanced settings

Also thanks. I came into this thread hoping to find a way to disable that. I mostly don't mind the UI change, but I really didn't need a pop-up explaining the tag I searched for at the top of every page.

It’s… fine. It will take some getting used to, but it’s not atrocious. I’m just disappointed in how its release was handled. Yes, there was e926 and the Discord, but not everybody uses either of those. A simple announcement saying “Hey, we’re testing a new layout that will be releasing soon! Come to e926 to check it out!” on the main website would have been nice, but putting this onto users without any warning is a bad move. Again, the update itself is fine, but the release could have absolutely been handled better.

cinder said:
What exactly is the issue though?
The site does not have a "search suggestions" feature. We do have autocomplete, but that does seem to function normally.

I'll try to be more specific. I'm using Kiwi Browser on Android and on the homepage of E621(https://e621.net/), when I click on the search bar, there are Autocomplete suggestions from searches I've done in the past. This used to also work in the searchbar on the Posts page (https://e621.net/posts) 2 days ago, but now it does not. The way that my very lengthy searches appear in the searchbar on the Posts page also appear differently; the words word-wrap. And when they do, the searchbar extends vertically. Used to, it would not word-wrap. I don't have a problem with the word-wrapping at all, but something changed here; just not quite sure what. The latest change to Kiwi Browser was 7 days ago, so it shouldn't be that. I also checked Chrome for Android, and the problem seems to exist there as well. Any ideas?

tamaneko said:
I'll try to be more specific. I'm using Kiwi Browser on Android and on the homepage of E621(https://e621.net/), when I click on the search bar, there are Autocomplete suggestions from searches I've done in the past. This used to also work in the searchbar on the Posts page (https://e621.net/posts) 2 days ago, but now it does not. The way that my very lengthy searches appear in the searchbar on the Posts page also appear differently; the words word-wrap. And when they do, the searchbar extends vertically. Used to, it would not word-wrap. I don't have a problem with the word-wrapping at all, but something changed here; just not quite sure what. The latest change to Kiwi Browser was 7 days ago, so it shouldn't be that. I also checked Chrome for Android, and the problem seems to exist there as well. Any ideas?

It might be easier to demonstrate visually rather than explaining in words if they are unaware of what is going on as a whole.

https://i.imgur.com/8lia3U4.png

I used that autofill a lot in order to search common things, the change ruined searching on the site for me.

deadoon said:
It might be easier to demonstrate visually rather than explaining in words if they are unaware of what is going on as a whole.

https://i.imgur.com/8lia3U4.png

I used that autofill a lot in order to search common things, the change ruined searching on the site for me.

This. This is exactly how I used it. Or used to. I had so many artists and tags bound to almost every letter on the keyboard, I can't remember even one.

Stop "fixing" what isn't broke.
Stop "fixing" what isn't broke.
Stop "fixing" what isn't broke.

This constant need to "update" things is a disease. The ideal software, or website, is one that, aside from minor compatibility tweaks, doesn't have to be changed for DECADES. I was watching a Youtube video recently by one of the main programmers of the old Mac port of Word from 98 or so, running it on an emulator, and pointing out that if you were to take someone now and drop them into that program, they'd have most of what they needed, and not much trouble finding it. In fact it might be easier in some cases, and probably more responsive too. In other words, for features the vast majority of users use, Word was feature complete almost 3 decades ago. All the fucking and fiddling since hasn't materially improved the UI, it's just made it more bloated and silly, and burned money in the process. So it goes with most things.

Every time there's another re-design like this I'm reminded of the Tom and Jerry short where the mouse glues all the furniture to the ceiling, then keeps switching it between floor and ceiling, making the cat think he's going insane. That's what these re-designs feel like, like someone's sneaking into your house when you're out, repainting the walls, bricking up windows, adding new ones, and replacing the hardwood with carpet. It makes me feel like I'm going insane. And that's what a lot of these comments miss: it's not just about the technical debate over whether this or that element is easier or harder to use, prettier or uglier. Changing things at all incurs a mental cost, because now everything's fucked with and you have to re-learn it all over again.

There's not justification for this. No. Stop. There isn't. "Mobile" isn't a justification. "Modernization" isn't a justification. You can change mobile design without messing with desktop. You can change backend and underlying code to work better in a modern browser environment without changing visual design. Changing the way the site looks and behaves is a deliberate decision, made ONLY on the basis of you not thinking the previous style was hip and trendy enough, like those people that buy beautiful old houses, tear out the insides because they're "dated" and replace them with the most cheap, hideous, bland modern slop available. So up to date!

A website is not "fast fashion." It's not about looking hip. It's about providing a service as effectively as possible. And that's not being served when everything is re-shuffled every couple years on a whim.

This happens over and over and over. These nonsensical, pointless changes are made, the users understandably complain and rebel, and the site admin tell them to stuff it, that they just aren't sophisticated enough to appreciate the clear genius of the new design. If you had any faith in the new version, if you REALLY believed it was better, you'd make using it voluntary. But you never do, because you know the only way to get people to use your darling new creation is to force them to.

And of course this is only for casual users. Power users get TURBO screwed, because your fancy new design breaks more complex usage cases left and right. Some of these usage cases might get sorted out in time, but they wouldn't NEED to be sorted out if you didn't update things for no reason.

And casting everyone who complains or criticizes as set in their ways or unable to handle change, as always happens in this situation, is slimy. Change is neither good nor bad. Sometimes it makes things better. Sometimes (more often than not) it makes them worse. This is why it shouldn't be undertaken on a whim: there's a cost for fucking around with stuff this massively, even when there IS a good justification for it.

The changes suck. They suck aesthetically, and on a practical level. If I was a UI expert I could go through and dissect all the ways this and other updates have made the site genuinely harder to use, but I'm not, and it's not worth the time. But I, and the other posters here don't need to be experts to know that it sucks, in the same way you don't need to be a gourmet to know when bread is stale, or meat is rancid, or that there probably shouldn't be a finger floating in your soup. Some things are just self-evident.

Three quarters of the comments here agree. But they'll be ignored, mocked or dismissed, like they always are. And that's your prerogative: you run the site. You pay for it (well, your boss does anyway). If you want to make it worse and worse, that's your privilege to enjoy. But screw you for making a tool so many of us have come to reply on uglier and harder to use.

gleeful_geko said:
Stop "fixing" what isn't broke.

I stopped reading after this.
Any feedback that includes these words is ignored, generally speaking.

cinder said:
Any feedback ... is ignored, generally speaking.

Thanks for proving his point.

busahou said:
Thanks for proving his point.

The point about how I shouldn't do anything at all?
Yeah, then I guess point proven.

ye_shi_qi said:
I also encountered the problem of not retaining the original search terms when clicking on a new search, which made me very distressed because I have always used this method to filter my favorite character images. Not retaining the search terms means that I have to spend more time copying and pasting the existing ones

This happened to me too, both in Firefox and MS Edge. I search some tag combinations almost every day, "equid -my_little_pony" for example. But now the search field doesn't remember them. Either I have to put them in manually every time or use browser history. Rather annoying.

It stopped working on e6ai.net, too.

cinder said:
The point about how I shouldn't do anything at all?

No, they did say:

gleeful_geko said:
You can change mobile design without messing with desktop. You can change backend and underlying code to work better in a modern browser environment without changing visual design.

[...]

And casting everyone who complains or criticizes as set in their ways or unable to handle change, as always happens in this situation, is slimy. Change is neither good nor bad. Sometimes it makes things better. Sometimes (more often than not) it makes them worse. This is why it shouldn't be undertaken on a whim: there's a cost for fucking around with stuff this massively, even when there IS a good justification for it.

They're not saying to not change anything. They're saying it can (largely) be done without changing the UI people are used to using, and in cases where the UI needs to change, it should be carefully weighed against the mental cost it's going to levy on users. This goes back to the issue of things changing with seemingly no justification. Yes, you said there's problems with the site on mobile, and this work is being done to fix it. But there's nothing about why the locations for various links changed, why things like the search bar no longer allow the browser to retain its own history (when autocomplete is off), why the desktop UI is changing, etc. Some of this could be chalked up to unintended consequences (in a large enough codebase, changing one thing often has unexpected effects on other things), which ideally would be fixed or at least explained why it can't be. But without any apparent reason for the change, or any indication it's being recognized as an issue to be looked at, it comes across as either an intentional change for the sake of change, or someone who's not taking responsibility to fix what they accidentally broke.

watsit said:
They're not saying to not change anything. They're saying it can (largely) be done without changing the UI people are used to using, and in cases where the UI needs to change, it should be carefully weighed against the mental cost it's going to levy on users. This goes back to the issue of things changing with seemingly no justification. Yes, you said there's problems with the site on mobile, and this work is being done to fix it. But there's nothing about why the locations for various links changed, why things like the search bar no longer allow the browser to retain its own history (when autocomplete is off), why the desktop UI is changing, etc. Some of this could be chalked up to unintended consequences (in a large enough codebase, changing one thing often has unexpected effects on other things), which ideally would be fixed or at least explained why it can't be. But without any apparent reason for the change, or any indication it's being recognized as an issue to be looked at, it comes across as either an intentional change for the sake of change, or someone who's not taking responsibility to fix what they accidentally broke.

It's not possible to change the mobile UI without affecting the desktop site in at least some way.
There are multiple reasons for that, both technical (how responsive mobile-first design works) and practical (maintaining two separate versions of the site takes up dev time that should be better spent elsewhere).
Despite what the current narrative in this thread is, I have done my best to maintain the look and feel of the desktop site as much as possible when making changes to the mobile site.

I've read the feedback, taken notes, and made changes based on it. Some of those changes had already been deployed in various patches, and some have not.
What I can't do is respond to every message. Nor do I think that responding to every comment to explain myself is a useful way to send my time.
In the future, I will do my best to give more insight into the upcoming changes in devlogs, like the one from earlier this week.

I also cannot immediately respond to every issue anyways.
I have a day job, typically working 10 hour days. I saw the feedback on the search bar's browser-specific autocomplete, but all I had time for was to ask a couple of questions asking for elaboration.
Today, I looked into it, but couldn't immediately come up with a reliable fix. The searchbar changed from being an <input> element to a <textarea> to allow it to expand vertically in response to a longer search query.
I will do my best to resolve the problem.

Why does the main menu have "lastest" and "popular" but popular actually sends you to hot (order:rank)

retry said:
Why does the main menu have "lastest" and "popular" but popular actually sends you to hot (order:rank)

That button used to send you to the popular page.
Then I thought that it might be a good idea to give users a way to quickly find the good posts, rather than the latest ones, so I made it so that if you type something into the searchbar and then pressed one of those buttons it would submit a search.
... only the popular page cannot be searched, so I had to go with the order:rank.

I would like to rename the "popular" to "top" at some point, since that's what it is.
People otherwise get confused over what the difference between it and "hot" is.

cinder said:
I also cannot immediately respond to every issue anyways.
I have a day job, typically working 10 hour days. I saw the feedback on the search bar's browser-specific autocomplete, but all I had time for was to ask a couple of questions asking for elaboration.
Today, I looked into it, but couldn't immediately come up with a reliable fix. The searchbar changed from being an <input> element to a <textarea> to allow it to expand vertically in response to a longer search query.
I will do my best to resolve the problem.

Appreciate you looking into it. Hopefully none of my descriptions of the problem came off as berating or anything. Simply just trying to detail a new issue I was running into. Thank you for your work.

cinder said: Today, I looked into it, but couldn’t immediately come up with a reliable fix. The searchbar changed from being an <input> element to a <textarea> to allow it to expand vertically in response to a longer search query. I will do my best to resolve the problem.

ahA! So THAT might the strange black magic fuckery that Apple Watch hates.

For context, over the last few years text input boxes have slowly become uneditable with Apple Watch (although that’s not something that website devs would really be concerned about), and one of the recent ui updates made the post search bar unusable. I made a forum topic on it :l

Edit: I wrote this at 1am using my Apple Watch. The only text box I can manipulate now is forum/comment replies.

It seems recently when you're on the page for a blacklisted post, clicking anywhere in the image area (even way off to the side, nowhere near the "Blacklisted" placeholder image) will reveal the image. This is quite unexpected. Just because I happen to click on the page doesn't mean I want to see a blacklisted image, it can often happen to be because there's another window with focus and I want to bring the browser window to focus by clicking on it, and that area where the image goes was otherwise a "safe" area where I won't accidentally click a link (something I do for non-blacklisted images too). This seems like a way-too-easy method to accidentally reveal what someone has explicitly blacklisted (which can be some pretty extreme stuff), especially when there's already the links on the left to explicitly disable the blacklist temporarily that's harder to hit accidentally. It also seems that, once the blacklisted image is revealed, clicking on it again doesn't hide it again, it remains visible until the page is reloaded.

watsit said:
It seems recently when you're on the page for a blacklisted post, clicking anywhere in the image area (even way off to the side, nowhere near the "Blacklisted" placeholder image) will reveal the image. This is quite unexpected. Just because I happen to click on the page doesn't mean I want to see a blacklisted image, it can often happen to be because there's another window with focus and I want to bring the browser window to focus by clicking on it, and that area where the image goes was otherwise a "safe" area where I won't accidentally click a link (something I do for non-blacklisted images too). This seems like a way-too-easy method to accidentally reveal what someone has explicitly blacklisted (which can be some pretty extreme stuff), especially when there's already the links on the left to explicitly disable the blacklist temporarily that's harder to hit accidentally. It also seems that, once the blacklisted image is revealed, clicking on it again doesn't hide it again, it remains visible until the page is reloaded.

That sounds like a bug report.
Not... whatever this thread is.

I'll look into it. The script is probably using the wrong element when listening to the clicks.

i can't stand the searched tag summaries. i don't need free_use explained to me, i'm the one searching for images of it.

skullcat said:
i can't stand the searched tag summaries. i don't need free_use explained to me, i'm the one searching for images of it.

.wiki-excerpt { display: none; }

in your custom css as a temp fix

Coming back after a while and seeing site broken is unpleasant. My extension doesn't work. Posts display only in two columns making most of the screen empty. Yup. I hate UI changes and trend of prioritising mobiles.
I also kinda miss welcome in different languages.

I will probably be less pissed when extension updates and thumbnails will display correctly for me again.

arter said:
Coming back after a while and seeing site broken is unpleasant. My extension doesn't work. Posts display only in two columns making most of the screen empty. Yup. I hate UI changes and trend of prioritising mobiles.
I also kinda miss welcome in different languages.

I will probably be less pissed when extension updates and thumbnails will display correctly for me again.

It is a little absurd to call the site broken when it's your extension that does it.
And if you are talking about re621, then it's already been updated.

I skimmed through the thread and didn't see anyone else mention this, but the post grid UI is broken on my tablet (iPad Air 2) for both Safari and Chrome. The grid overshoots at the bottom and covers up the page numbers and even the first few tag links (e.g., https://files.catbox.moe/opvik0.PNG ). The UI always worked fine on my iPad before the update.

Maybe this only affects legacy devices? Regardless, it's definitely been disruptive to my personal mobile experience.

brokenclock said:
Maybe this only affects legacy devices? Regardless, it's definitely been disruptive to my personal mobile experience.

I cannot replicate this bug, since I do not have this specific iOS device from over a decade ago.
It's possible that you are using a browser versions that is so old that it does not support the grid layout.
Safari 10.1 and Chrome 57 should support it, though. Both were released in early 2017.

brokenclock said:
I skimmed through the thread and didn't see anyone else mention this, but the post grid UI is broken on my tablet (iPad Air 2) for both Safari and Chrome. The grid overshoots at the bottom and covers up the page numbers and even the first few tag links (e.g., https://files.catbox.moe/opvik0.PNG ). The UI always worked fine on my iPad before the update.

Maybe this only affects legacy devices? Regardless, it's definitely been disruptive to my personal mobile experience.

Take this

#tag-box { padding-top: 200px; }

cinder said:
I cannot replicate this bug, since I do not have this specific iOS device from over a decade ago.
It's possible that you are using a browser versions that is so old that it does not support the grid layout.
Safari 10.1 and Chrome 57 should support it, though. Both were released in early 2017.

My iPad is on Safari 15 and Chrome 125, but I wouldn't be surprised if it's an issue with legacy devices.

brokenclock said:
My iPad is on Safari 15 and Chrome 125, but I wouldn't be surprised if it's an issue with legacy devices.

Use

.posts-container { padding-bottom: 200px; }

(change 200 to best fit your needs)

instead. CSS is hard :(

Something about result pages is slower now. It's like it's taking a few seconds to load in all of the frames before it starts displaying. Doesn't seem to be slowed down by the thumbnails. I can see the scroll bar moving as it's loading the page in but it won't display any images until it's done doing that.

I use 250 results per page but don't remember the slowdown before.

Just seems unnecessary. Like when they changed the interface to deviantart I like the old layout before

smartlewis said:
Just seems unnecessary. Like when they changed the interface to deviantart I like the old layout before

Banned for having bad opinions.
And also ban evasion.

gleeful_geko said:
Stop "fixing" what isn't broke.
Stop "fixing" what isn't broke.
Stop "fixing" what isn't broke.

The thing is it was broke. It was an extremely crusty UI inherited mostly from Danbooru and only marginally better than FA's coming from the same era, and required more clicks than necessary to access common things (doing Account -> Profile was particularly annoying). A lot of options were buried when they shouldn't have been. I've read your whole rant and I personally think it does indeed boil down to "old thing good, new thing bad." Not at all nuanced and mostly giving the illusion of competency through length, and I say that as a professional programmer capable of creating a UI like e621's, especially given the core layout of e621 is mostly unchanged.

And now, a bit of genuine feedback on the UI:
- The result count hugs the container it's in a little too much, making it difficult to read on desktop. On mobile it's not an issue.
- Margin/padding with the news item text on mobile has the same problem as the post count on desktop.
- A proper toggle for the wiki on search results. Apparently the big "X" in the top right corner was too hard for people to find, so a settings option under the Advanced tab in settings could be helpful for that, the themes page is not where I'd think to look for it.

Still wanna have the option to switch the 3 lines to the left but another thing I'd like to see is the option for a custom order for sets/pools and not just alphabetical and add an easier way to get to my own sets than three lines > sets > three lines > mine

I'd like to have some way of hiding the sidebar on a post's page. More space for the picture, would be especially useful on a tablet.

mklxiv said:
The thing is it was broke. It was an extremely crusty UI inherited mostly from Danbooru and only marginally better than FA's coming from the same era, and required more clicks than necessary to access common things (doing Account -> Profile was particularly annoying). A lot of options were buried when they shouldn't have been. I've read your whole rant and I personally think it does indeed boil down to "old thing good, new thing bad." Not at all nuanced and mostly giving the illusion of competency through length, and I say that as a professional programmer capable of creating a UI like e621's, especially given the core layout of e621 is mostly unchanged.

And now, a bit of genuine feedback on the UI:
- The result count hugs the container it's in a little too much, making it difficult to read on desktop. On mobile it's not an issue.
- Margin/padding with the news item text on mobile has the same problem as the post count on desktop.
- A proper toggle for the wiki on search results. Apparently the big "X" in the top right corner was too hard for people to find, so a settings option under the Advanced tab in settings could be helpful for that, the themes page is not where I'd think to look for it.

I'm not sure what you mean about the result count being hard to read. It seems fine to me, at least on the default theme.
Adding more padding to it might be controversial, since it'll shift the posts section even further down.

I will be working on the settings menu over the next few weeks, and I will integrate the themes menu further in there. Including (hopefully) a way to search the settings.
The reason why the themes are save locally in your browser and not on the account is because the majority of site visitors do not actually have an account.
I want to give them a way to customize their experience without having to sign up.

walkingspaghett said:
Still wanna have the option to switch the 3 lines to the left but another thing I'd like to see is the option for a custom order for sets/pools and not just alphabetical and add an easier way to get to my own sets than three lines > sets > three lines > mine

An option to move the menu toggle to the left is likely not going to happen. It's quite a bit of work for not a lot of gain.
I'll think about how to make navigating to your sets easier. Just some buttons on the mobile version of the sets page should save you at least one click, for example.

banhday said:
I'd like to have some way of hiding the sidebar on a post's page. More space for the picture, would be especially useful on a tablet.

I agree, and I will work on that in the future.

walkingspaghett said:
Still wanna have the option to switch the 3 lines to the left

I believe you should be able to change that with custom css

For example you could have this https://imgur.com/a/nWufI6G

cinder said:
The reason why the themes are save locally in your browser and not on the account is because the majority of site visitors do not actually have an account.
I want to give them a way to customize their experience without having to sign up.

That's good rationale. Thanks for thinking of it.

And I should say less "hard to read" and more jarring, since it hugs the border of the container.

New update! Only big notice I’ve seen is the new profile icon, which does look good, though I wish it had the profile image and the words “Profile”. On its own, the profile button being just the photo doesn’t make it clear what it is. This is a nitpick more than anything, but just wanted to give my thoughts.

My first thought with the new blatantly huge search bar was that I was put in a mobile mode on desktop. Imagine my surprise when mobile mode On/Off does apparently nothing different. And now the search bar with tags is its own panel that can be anchored to... nothing? Or put fullscreen which takes the whole 2160px of my monitor. Not to mention the search "panel" is being overlapped by the main panel, which gives the whole UI a feeling of weirdness.

I like new stuff, but that's not it. If you want to make a mobile-friendly UI/UX leave it to the mobile world only. Desktop did not need any new stuff like those displayed. Also isn't there a limit for search tags anyways? Wouldn't displaying the number of remaining tags be a better UI update than all this?

The whole website went from feeling like a very saucy an archive to someone's web design college project. It felt structured before, and now it feels uncertain.

chaoscontrl said:
If you want to make a mobile-friendly UI/UX leave it to the mobile world only.

No.

chaoscontrl said:
It felt structured before, and now it feels uncertain.

Lmao.

chaoscontrl said: isn't there a limit for search tags anyways? Wouldn't displaying the number of remaining tags be a better UI update than all this?

I mean, there is, but it's like 30 or something, so you're never going to hit it. having a number would be pretty much pointless. maybe it'd've been useful when the limit was 6, but now, not so much.

dba_afish said:
I mean, there is, but it's like 30 or something

It's 40, that is near impossible to hit without being so specific you're getting at most 1 or 2 posts in the results

donovan_dmc said:
It's 40, that is near impossible to hit without being so specific you're getting at most 1 or 2 posts in the results

oh. golly, I honestly though I was overshooting with the 30 guess. I even lowered it from an initial 32 because I thought it might've been like 25.

donovan_dmc said:
It's 40, that is near impossible to hit without being so specific you're getting at most 1 or 2 posts in the results

shaded 2022 krezz_karavan school_days edna_(school_days) adolescent mammal anthro biped bodily_fluids breasts day duo female female_anthro from_behind_position front_view genitals looking_at_another male male/female male_anthro nude nude_anthro nude_female nude_male penetration penis pussy sex text vaginal vaginal_penetration window artist_name cel_shading dated digital_drawing_(artwork) digital_media_(artwork) english_text

But to be more serious, you're much much much more likely to hit it by excluding things from search, and for that purpose 40 isn't enough

I’m a big fan of the new interface but i’d change two details about it.

1: Make the tag description collapsed by default.

2: Change the tiny pfp on the header back to the 👤 icon(maybe with cat ears), some pics just don’t work at that scale.

snpthecat said:
I believe you should be able to change that with custom css

For example you could have this https://imgur.com/a/nWufI6G

Yes that's what I want, can you send what to put in CSS?