Topic: 25.11.05 Update Discussion

looking through posts looks messier than usual now, but more importantly why does Norton pop up saying the ads that show up were a "secured threat"? i feel like im using r34 now

I also hate that on my phone browser it doesn't display the amount of comments on a post's thumbnail anymore. Why the hell would they update the website to have thumbnails display LESS information?

This new thumbnail UI hurts my eyes, genuinely. I dunno if it's an issue on my end but the font size of Likes/Dislikes under thumbnails/posts is so tiny I have to literally squint. (On PC, Mobile mode off).

l-pop said:
looking through posts looks messier than usual now,

The devs pushed out a new UI update, see forum #471352.

but more importantly why does Norton pop up saying the ads that show up were a "secured threat"? i feel like im using r34 now

People have also experienced this issue with Avast, see also topic #60286.

I can't recall if "ads.e621.net" was used in the past, but it might have triggered some kind of global spam blacklist due to having the word "ads" in the name.
Alternatively, it could just be shitty automated blacklisting by anti-viruses.

thegreatwolfgang said:
The devs pushed out a new UI update, see forum #471352.

People have also experienced this issue with Avast, see also topic #60286.

I can't recall if "ads.e621.net" was used in the past, but it might have triggered some kind of global spam blacklist due to having the word "ads" in the name.
Alternatively, it could just be shitty automated blacklisting by anti-viruses.

It was previously ads.dragonfru.it, it's been ads.e621.net for a few weeks though

twilicorn said:
This new thumbnail UI hurts my eyes, genuinely. I dunno if it's an issue on my end but the font size of Likes/Dislikes under thumbnails/posts is so tiny I have to literally squint. (On PC, Mobile mode off).

Same, something about it is just entirely off
the main info section is rounded inside the overall footer so the rating color bleeds over a bit, and because the blacklist and explicit colors are the same if a post is both blacklisted and explicit then it's the same color across except for a big enough to be noticeable but small enough to not even be able to tell what color the little curved sliver separating the two is

Are we really doing this again, so soon?

Alright, I'll just wait until somebody releases a CSS pack to unfuck it back to where I already had it unfucked to after the last update. This is getting tiresome.

I have nothing insightful to say, but I do not like this.

The ui designers should get an ig nobel prize lmao

I don't mind it really, I'll just need to get used to it.
I'm generally more a fan of giving people the option to use either the classic Interface or switching to the new one, so everyone can decide for themselfs what they like better.

Especially when it comes to functionality on different devices

my only issue is that posts aren't aligned as well and there's wasted space on the right side on mobile/desktop, unlike before

Yeah, there's a lot of asymmetry going on here and I can't put my finger on what it is exactly, but I've been finding myself having to squint a bit more to see the numbers

Why do UI designers think that they need to get rid of all asymmetry? In a layout designed to convey a lot of information at a glance, size and shape is faster than words and letters.

Score was presented very well under thumbnails before. It's easy to tell 1435 apart from 140 at a glance, but not 1.4k from 140. The restyle of the score and fav count under thumbnails to be very similar also makes it hard to focus on just one.

ponporio said:
I also hate that on my phone browser it doesn't display the amount of comments on a post's thumbnail anymore. Why the hell would they update the website to have thumbnails display LESS information?

Yes, the removal of the number of comments is the main thing I dislike about this change. If I'm browsing through a pool or set and I want to see what people have to say about certain images, it's good to be able to see at a glance which posts have comments, without having to edit the search to include order:comment or order:comment_count.

Personally, I find being able to see the score and the comment count more useful than seeing the score and the number of favorites.

chemistrynoisy said:
Yes, the removal of the number of comments is the main thing I dislike about this change. If I'm browsing through a pool or set and I want to see what people have to say about certain images, it's good to be able to see at a glance which posts have comments, without having to edit the search to include order:comment or order:comment_count.

Personally, I find being able to see the score and the comment count more useful than seeing the score and the number of favorites.

What are you referring to? The new UI has score, favorites, and comments.

scth said:
What are you referring to? The new UI has score, favorites, and comments.

On desktop it shows all three, but on mobile it only shows the first two.

pawsta said:
I don't mind it really, I'll just need to get used to it.
I'm generally more a fan of giving people the option to use either the classic Interface or switching to the new one, so everyone can decide for themselfs what they like better.

Especially when it comes to functionality on different devices

Aacafah said:

Let me just put this out here so I can link it the next time.

I am a huge proponent of user choice & freedom. I'd love to allow users (myself included) to customize changes to their heart's content; I think that's an ideal worthy of striving towards.

That being said, I'm not the head honcho, so there's that.

The problem isn't a lack of desire; we already have some theme customization (I'm still rocking the pride logo myself w/ the Bloodlust color scheme as my theme; go here & you can do the same). The problem is how to expand that practically.

Here's a little inside baseball for you; e621ng (which is open source btw; you're more than welcome to contribute to the direction the site takes) is written with Ruby On Rails, or just Rails for short. Rails is a multi-page app framework that renders everything on the server. We'll circle back to this.

The main problem is that e621 has 1 dedicated developer (that's Cinder) & a motley crew of volunteer contributors (such as myself). Having Cinder validating that these hobbyists work isn't going to make the system explode is already a ton of work. Separating out UI changes, many of which are also tightly tied to changes in how the backend server works (because everything is handled on the server, Rails & many MPA's tightly couple front-end & back-end) even further shrinks the time he can spend adding new things to the site. Adding some kind of beta site/granular UI toggle for every potentially contentious change is a herculean task that would completely halt development for weeks at the very least, probably closer to months. For a beta site, it would also require approval from & cooperation with the technical staff at Bad Dragon (the site's owners). For a granular toggle system, it would implicitly demand supporting deprecated UI elements & styles, with users rightfully imo getting very angry when we break their specific combination of UI settings while iterating the site's design & features. I'll also remind you that any & all bug fixes need to be handled by him too, meaning either those also need to be put on hold, or those will eat away at the dev time for our solution.

On top of that, because Rails is rendered on the server & has tooling to facilitate that, all of the HTML (& some of the JS iirc) is embedded in .erb files that need to be processed by the server, & a lot of the JS also is tightly coupled to changes in the backend logic. Therefore, we'd need to update the server itself every single time there's a UI update regardless of whether or not the backend logic actually changed. We shouldn't lose uptime everytime, but in software development, you learn not to rely on what "should" happen pretty quick. So, instead of developing & updating the server logic & the UI at the same time, we'd have to develop the UI independently of the backend logic for much as possible, & update the server logic & UI separately. This is simply not practical, at least for the time being.

Besides, with the Settings -> Advanced -> Custom CSS option, we've already given more user customization than any other site on the planet; you can almost always get back to exactly what you want yourself without placing this burden on development.

Tl;dr, we'd love to have our version of Discord PTB, or the Steam Client Beta, but that is simply not a task we have the resources to undergo, & we place greater priority on moving the site forward than carving out exceptions so users can avoid changes.

Edit

Firstly, to include Donovan's excellent point,

donovan_dmc said:

nacre said:
So make those changes for the mobile site and not the desktop one.

before anyone says "oh but it's more to maintain" It's two buttons that worked fine for 15 years before this.

You're applying that logic to just this change when it really applies to the entire site, consider that mobile first changes are made in various places of the site, each may be just a few things on their own but combined it's a lot of things

Additionally, since I first wrote this, I've found cases where the best choice of how the user's customizations are stored is also user-dependent.
The user settings pane stores all of its data on the server, & therefore all of it is uniform across all devices you sign in on; all other options (e.g. the searchbar's settings menu, the themes menu, your currently deactivated blacklist items, keyboard shortcuts, etc.) are stored in Local Storage (to be simple, inside your browser), & therefore it can be customized for each browser (/device) you use.
Server storage:

• Eats up server bandwidth to update
• Eats up server storage & processing even if unused by most people (we still need to store NULL in empty SQL columns/a BOOLEAN value for a toggle, & we still need to handle empty/unchanged columns in our ORM)
• Requires a page refresh every time it's changed in order to reflect updates
• Increases the memory load on the server for every loaded user, which decreases performance
• Increases chances of mandatory server downtime every time it changes (b/c the database must be updated as well)
• Is persistent across all browsers used to access the site

Local Storage:

• Is persistent on the browser it's set on
• Virtually zero storage on users' machines
• No mandatory page update when changed
• Reloading the same page is also faster b/c the previously cached value is the same as the new one (as the changes only occur client-side)

Obviously, granular UI customization would be best served by being stored locally; it's specific to each browser, it adds no extra server load, & (unlike custom CSS) you can see the results as you tweak them without needing to reload the page (which obviously also decreases server load). However, the point of incognito/private windows is that they don't persist local data created during the browsing session (including Local Storage) across sessions, & many users are using incognito/private windows when accessing e6. As such, these users are limited in their options (although I'd recommend installing the PWA from an incognito/private window, as that stores its data separately from the main browser, & its initial data would be copied from the mostly empty local data from that session). Even a granular system can fail to appease everyone.

aacafah said:
Tl;dr, we'd love to have our version of Discord PTB, or the Steam Client Beta, but that is simply not a task we have the resources to undergo, & we place greater priority on moving the site forward than carving out exceptions so users can avoid changes.

Sorry if I sound dense, but aren't you guys already using e926 as a test grounds of sort?

thegreatwolfgang said:
Sorry if I sound dense, but aren't you guys already using e926 as a test grounds of sort?

You're good, that's a good point to raise.

For some features, we push exclusively to e926/our other sister site & only push to e621 on the next update, yes.

But the number of people who use e926 on purpose is clearly not enough for that to be effective. You all saw how colossal the complaints were about the TOS? That went live a week prior on e926, & we didn't hear a peep about it until it went live on e621. In order to actually get enough people to test the changes (& consequently generate feedback), we'd have to either aggressively push it (which also would require making this a more consistent process) or allow users to incrementally toggle changes on-site (which is untenable as said prior). Even if we pushed it hard, you can imagine what percentage of our userbase would use a version of the site that only shows posts rated Safe.

Additionally, because e926 uses the same database as e621, any changes that are coupled to database migrations can't be held back no matter what. This deeply limits the feasibility of this as is.

To be fair, we do have some workflow difficulties with soliciting, categorizing, & processing feedback, but an ideal system would likely take a lot of dev time to add, & we're already stretched thin.

Guys, I think I figured it out, the E621 is preparing to be sold to some company specializing in predatory monetization (or already was secretly sold to them). There's no other way to explain this level of enshittification.

taruyuv said:
Guys, I think I figured it out, the E621 is preparing to be sold to some company specializing in predatory monetization (or already was secretly sold to them). There's no other way to explain this level of enshittification.

...you know business records are public, right? Is it too much to ask for you to spend 2 minutes Googling before broadcasting your conspiratorial shower thoughts?

e621 is owned by Bad Dragon & its parent company Dragonfruit Ventures, & has been for years.

If you don't like the development of the site, perchance the fact it's being developed by 4 unpaid volunteers (at least 2 of which have fulltime jobs of their own to worry about) is more to blame than the Illuminati or Bill Gates wanting to ruin your jerk-off session. Besides, in the current political climate what business in their right mind would view buying a site that hosts pornographic content & is hosted in the US as a wise financial decision?

I like new icons. However, they are a bit too large compared to the text (or the text is too small). Not a big fan of new rating either, I don't think it's something that everyone always needs to pay attention to, but its background would suggest otherwise. I think it would work better if it was simply a colored letter in the corner. The gaps between everything are a bit too large, too.

Overall, this is how I would address above-mentioned issues:

/* (Post index/Thumbs) Makes description text larger and icons smaller, reduces gaps between them depending on card size, only shows color in small mobile card 25-11-06-preview */
body[data-st-size="l"], body[data-st-size="m"] {.thm-desc {font-size: .90rem; .thm-desc-a {column-gap: .3rem; .thm-desc-m {gap: 0} svg {scale: 95%}}
@media (max-width: 50rem) {font-size: .80rem; .thm-desc-a {column-gap: 0; .thm-desc-m {gap: 0} svg {scale: 80%; margin-right: -.1rem}}}}}
body[data-st-size="s"], #c-posts #a-show {.thm-desc {font-size: .80rem; .thm-desc-a {column-gap: 0; .thm-desc-m {gap: 0} svg {scale: 80%; margin-right: -.1rem}}}}
@media (max-width: 50rem) {body[data-st-size="m"] .thm-desc {grid-template-columns: auto 1rem}
body[data-st-size="s"], #c-posts #a-show {.thm-desc {grid-template-columns: auto .3rem; font-size: .70rem; .thm-rating {display: none}}}}

/* (Post index/Thumbs) De-emphasizes rating by changing background and text colors, except on small mobile cards 25-11-06-preview */
body[data-st-size="l"], body[data-st-size="m"] { .thm-desc {background-color: var(--color-section-lighten-5); .thm-desc-a {box-shadow: none} .thm-rating {padding: .25rem 0}}
.thm-rating-s .thm-rating {color: var(--palette-text-green)} .thm-rating-q .thm-rating {color: var(--palette-text-yellow)} .thm-rating-e .thm-rating {color: var(--palette-text-red)}}
@media (min-width: 50rem) {body[data-st-size="s"] .thm-desc {background-color: var(--color-section-lighten-5); .thm-desc-a {box-shadow: none} .thm-rating {padding: .25rem 0}}
.thm-rating-s .thm-rating {color: var(--palette-text-green)} .thm-rating-q .thm-rating {color: var(--palette-text-yellow)} .thm-rating-e .thm-rating {color: var(--palette-text-red)}}

/* (Post index/Thumbs) Restores comment count on medium and large mobile cards 25-11-06-preview */
body[data-st-size="l"], body[data-st-size="m"] {.thm-comments {display: flex}}
@media (max-width: 50rem) {body[data-st-size="m"] #page .thm-desc-a svg {margin-right: -.2rem}}

/* makes post index grid symmetrical */
.posts-container {justify-content: space-evenly}

Better version can be found in CSS library

It's terrible, especially the borders. They are extremely distracting and harming my experience.

waydence said:
Overall, this is how I would address above-mentioned issues...

I thank you for your continued efforts to help less technically-minded users customize their experience. If you'd like to make development contributions that we stand a better chance at not losing in the fray (& we can better credit you), I'd recommend making a PR on the GitHub repository.

I'm really not a fan of 1.0k instead of 1000. The font is too small, too.

Also, on the user profile page that shows uploads/favorites, the comment amount gets cut off by the "E" if a post has more than 10k favorites.

pizzadelivery42 said:
It's terrible, especially the borders. They are extremely distracting and harming my experience.

the borders? the green/yellow/blue ones around post thumbnails?

those have been there since, like, 2009.

votp said:
Are we really doing this again, so soon?

Alright, I'll just wait until somebody releases a CSS pack to unfuck it back to where I already had it unfucked to after the last update. This is getting tiresome.

i'm not sure that's allowed. i posted some custom css i used to improve visibility of the stats in response to another comment about the smaller font, but it got deleted (or hidden?).

Ahh! Here we go again

Especially frustrating is that it was one of the better elements of the old design, it used to be simple, sleek and lightweight, but now it looks tasteless, garish and cluttered, plus hard to read

- The worst thing is changing the font and reducing the size of the numbers, before the readability was almost excellent, now you have to squint your eyes hard

- All those new colors and new icons make the interface super cluttered, also disharmonize with the rest of the design

- Putting the rating in a separate box does not help as it only increases the overload and overclutter, therefore it gets lost in all of this.
Also its bright color is very distracting and makes it hard to look at the art in the thumbnail

- The lack of symmetry further degrades the aesthetics

- The old style looked great on all sizes of thumbnails, now the small (classic) thumbnails are just an eye-bleeding horror. Additional height decrease of the thumbnail in this size makes it even worse.
Also when a post has more than a thousand upvotes, the information about the number of comments becomes unreadable at all, because it does not fit in the bar

- Pushing the thumbnails to the left side instead of spreading them out looks really ugly, instead of a nice adative layout we have a lame empty space on the right side of the page. It becomes obvious when you change the resolution and aspect ratio of windows/screen

May someone help me? I was playing with custom CSS for a while and finally did it looking somewhat good for me after the update. Now I'm interested can I make the scoreboard stick to the bottom of the thumbnail?
To get rid of dark space like in this example: https://imgur.com/ICJpdix

sps said:
i'm not sure that's allowed. i posted some custom css i used to improve visibility of the stats in response to another comment about the smaller font, but it got deleted (or hidden?).

It's allowed, just not clogging up the thread for reporting bugs. This is a more appropriate venue for it.

The complete lack of negative space makes everything harder to parse. It's suffocating, especially with the clutter beneath each thumbnail.

aacafah said:
It's allowed, just not clogging up the thread for reporting bugs. This is a more appropriate venue for it.

alright, thanks. i wasn't given a reason for the removal (and this venue didn't exist at the time), so i could only speculate.

for anyone having trouble with the smaller stats under thumbnails, here's what i did on my end to improve visibility:

i used this custom css to restore the fonts size:

.thm-desc {font-weight: 700; font-size: inherit; line-height:inherit; font-family: inherit;}

just increasing the font size can cause things to overlap when numbers get too many digits, so i also added this custom css to remove the icons and space the numbers better (because there isn't enough room for the text and icons at the larger font size when the numbers get big)

.thm-desc-a {column-gap:inherit;justify-content:space-around;}
.thm-score svg {display:none;}
.thm-comments svg {display:none;}
.thm-favorites svg {display:none;}

it still looks a little weird with small numbers, but it's good enough for me.

dfn-451 said:
the borders? the green/yellow/blue ones around post thumbnails?

those have been there since, like, 2009.

Pretty sure this is the first time I've seen it.

In Posts (and similar sections), the UI design of the statistics under the posts could be better.

1. The numbers should never be shortened.
When the numbers are not shortened, it's easy, at a glance, to notice how popular a post is. Whether a post has 5, or 50, or 500 upvotes, it's easy to perceive, simply from width of the number, how popular a post is. But now, you got these "k"s at the end of numbers. Now, I have to READ every single number to first determine whether it's been shortened to kilos or not, before I'm able to know whether the number is big or small. Basically, if you studied UI design in college like I did, you'd know why this is worse UI design.
To begin with, there's no point in shortening, because whether a post has "1234" favs, or it has "1.2k" favs, both of these are 4 characters long. So shortening the numbers didn't even save any space.
Therefore, I suggest that the statistics numbers should either never be shortened, OR use a more noticeable format for posts that have over 1000 favs/upvotes, for instance, by making that little "k" larger, bolder, have a different color, glow, have the whole number outlined, etc. You get the idea.

2. Post's rating could yet be better presented
Tucked over there in the corner, it's hard to notice. It's better than it was before, when it was just a colored letter, but it still doesn't pop out enough for an average user to be able to spot it without looking at it directly.
You could try with the thm-desc-a span having transparent background (add font outlining), or simply not taking up most of the statistics row.

... Did it always cut shit off and I just never noticed?

Edit: Aw man, what the fuck it gets worse every time I look

I can't see deleted posts in my favorites aside from the new UI for the images stats unless it has a parent or child post and that's a tiny dot. Hard to delete something I can't click on.

Why do they keep trying to change the ui. There's absolutely no reason to change it. If its not broken don't fix it.

I cant even see comment numbers anymore on mobile, it's a pure downgrade for no reason

While I don't mind the look of the font/icons, I'm not overly keen on getting the rating block if it means losing the comment count on mobile. Desktop font size could stand to be bumped up a bit, though,

It looks much nicer now! Maybe the font under the thumbnails on desktop could be made a bit bigger/bolded, but at least in my 1080p monitor, it's still readable.
I also enjoy the smaller thumbnails on mobile, to minimize scrolling, but I think there is enough space to fit the comment count like some people are asking, and the font is fine there since a phone is held much closer to the eyes than a 23" monitor

Overall nice update :3

i dislike the new ui, can we have options instead of pushing this on us?

My only feedback on this is, why not using FontAwesome for the icons?

It'd be easier to manage alignment and weight with the text/span used for the infos.

I've been using it like this:

<i class='fa fa-heart'></i> <span>${post.score.total}</span>
<i class='fa fa-bookmark'></i> <span>${post.fav_count}</span>
<i class='fa fa-comment'></i> <span>${post.comment_count}</span>

With a font size of 16px.

And a plus is that FA icons are very clear and bold (if i am not mistaken it uses 400 of font weight).

But that's only how i like them (also as i noticed some people complaining about the current icons visibility), if using the SVGs is lighter and/or more convenient for the devs, that's more than okay.

Would anyone be willing to please take a stab at updating the "Unfuck the UI" CSS script for the new build? Looks like it broke again.

For reference, this is the old script:

@media (min-width: 474px) {
article.thumbnail {
    width: min-content;
}
}

article.thumbnail {
    max-width: 150px;
    min-height: unset !important;
    min-width: unset !important;
}

article.thumbnail a {
    height: unset !important;
    max-height: unset !important;
    max-width: unset !important;
    width: unset !important;
    flex: unset !important;
}

article.thumbnail img {
    max-height: 150px;
    max-width: 150px;
    height: unset !important;
    object-fit: unset !important;
    pointer-events: none;
    width: 100%;
}

@media (min-width: 474px){
article.thumbnail:not(.deleted) img {
    width: unset;
}
}

section.posts-container {
    grid-template-columns: repeat(3,1fr) !important;
    --thumb-image-size: 150px;
}

@media (min-width: 474px) {
section.posts-container {
    grid-template-columns: repeat(auto-fill,minmax(var(--thumb-image-size),1fr));
}
}

article.thumbnail .desc {
    height: unset !important;
}

.post-thumbnail.dtext img {
    max-height: 150px;
    max-width: 150px;
    width: auto;
    height: auto;
}

#image-container.blacklisted img.post-thumbnail-img, 
#image-container.blacklisted video, 
.post-thumbnail.blacklisted img.post-thumbnail-img, 
.post-thumbnail.blacklisted video {
    padding: 150px 150px 0 0!important;
    background-size: contain;
}

article.thumbnail.deleted img{
    width: calc(90vw / 3);
    max-width: 150px;
}

toastwithjam said:
Would anyone be willing to please take a stab at updating the "Unfuck the UI" CSS script for the new build? Looks like it broke again.

For reference, this is the old script:

@media (min-width: 474px) {
article.thumbnail {
    width: min-content;
}
}

article.thumbnail {
    max-width: 150px;
    min-height: unset !important;
    min-width: unset !important;
}

article.thumbnail a {
    height: unset !important;
    max-height: unset !important;
    max-width: unset !important;
    width: unset !important;
    flex: unset !important;
}

article.thumbnail img {
    max-height: 150px;
    max-width: 150px;
    height: unset !important;
    object-fit: unset !important;
    pointer-events: none;
    width: 100%;
}

@media (min-width: 474px){
article.thumbnail:not(.deleted) img {
    width: unset;
}
}

section.posts-container {
    grid-template-columns: repeat(3,1fr) !important;
    --thumb-image-size: 150px;
}

@media (min-width: 474px) {
section.posts-container {
    grid-template-columns: repeat(auto-fill,minmax(var(--thumb-image-size),1fr));
}
}

article.thumbnail .desc {
    height: unset !important;
}

.post-thumbnail.dtext img {
    max-height: 150px;
    max-width: 150px;
    width: auto;
    height: auto;
}

#image-container.blacklisted img.post-thumbnail-img, 
#image-container.blacklisted video, 
.post-thumbnail.blacklisted img.post-thumbnail-img, 
.post-thumbnail.blacklisted video {
    padding: 150px 150px 0 0!important;
    background-size: contain;
}

article.thumbnail.deleted img{
    width: calc(90vw / 3);
    max-width: 150px;
}

I mentioned this in a different thread, but everything got fixed for me after adding "aspect-ratio: 0 !important;" to the "article.thumbnail a" properties. Not sure if this will cause any other issues.

votp said:
Are we really doing this again, so soon?

Alright, I'll just wait until somebody releases a CSS pack to unfuck it back to where I already had it unfucked to after the last update. This is getting tiresome.

Why is e621 going through enshittification? The UI thumbnails were fine for years.

soskem said:
I mentioned this in a different thread, but everything got fixed for me after adding "aspect-ratio: 0 !important;" to the "article.thumbnail a" properties. Not sure if this will cause any other issues.

@media (min-width: 474px) {
article.thumbnail {
width: min-content;
}
}

article.thumbnail {
max-width: 300px;
min-height: unset !important;
min-width: unset !important;
}

article.thumbnail a {
height: unset !important;
max-height: unset !important;
max-width: unset !important;
width: unset !important;
flex: unset !important;
aspect-ratio: 0 !important;
}

article.thumbnail img {
max-height: 300px;
max-width: 300px;
height: unset !important;
object-fit: unset !important;
pointer-events: none;
width: 100%;
}

@media (min-width: 474px){
article.thumbnail:not(.deleted) img {
width: unset;
}
}

section.posts-container {
grid-template-columns: repeat(3,1fr) !important;
--thumb-image-size: 300px;
}

@media (min-width: 474px) {
section.posts-container {
grid-template-columns: repeat(auto-fill,minmax(var(--thumb-image-size),1fr));
}
}

article.thumbnail .desc {
height: unset !important;
}

.post-thumbnail.dtext img {
max-height: 300px;
max-width: 300px;
width: auto;
height: auto;
}

#image-container.blacklisted img.post-thumbnail-img,
#image-container.blacklisted video,
.post-thumbnail.blacklisted img.post-thumbnail-img,
.post-thumbnail.blacklisted video {
padding: 150px 150px 0 0!important;
background-size: contain;
}

article.thumbnail.deleted img{
width: calc(90vw / 3);
max-width: 300px;
}

bdanimare said:
Why is e621 going through enshittification? The UI thumbnails were fine for years.

Isn't enshitification related to harming user experience for financial reasons? If they started adding side banner ads for LLM brainrot ERP subscriptions for or something then I guess it would be. The term doesn't really apply here

soskem said:
I mentioned this in a different thread, but everything got fixed for me after adding "aspect-ratio: 0 !important;" to the "article.thumbnail a" properties. Not sure if this will cause any other issues.

Well that made it a little bit less ass, at least.

difficult to look at

my main issue is that it's just so cluttered now that it's difficult to see what's going on. i don't wanna always be wearing my glasses just to see the damn favorite count. the text and icons are just so tiny and inaccessible now. the ui was fine before i dunno why it keeps changing every month

(on desktop, Firefox) I don't know that I would agree that anything is tiny. But the lack of negative space is .. possibly a useful compromise for mobile? But it does feel like an over-optimization.

Maybe RE621 goes too far in the other direction, but I'm definitely glad I can just toggle that back on and get 3 thumbnails per row with spacing of about (30% of displayed thumbnail dimensions). It feels like that is in the right ballpark, though I'm sure mobile layout can't be quite that generous.

oneohthrix said:
Isn't enshitification related to harming user experience for financial reasons? If they started adding side banner ads for LLM brainrot ERP subscriptions for or something then I guess it would be. The term doesn't really apply here

It has multiple definitions