Below is my best attempt to put everything I've been working to compile into a list for the past week or so. Tried to keep it brief and constructive. My philosophy centers around the efficiency and ease of which I can work with many posts and their sets. I spend many hours, which is likely not wise, on managing my sets. Unfortunately the redesign has crippled me in that area in a few ways. I'll be following this post closely and I'm willing to work with people to see things improve. I'm also curious who else shares these opinions.

Anyway, here's the list of every bug and grievance I have with the redesign:

* Adding-To-Set notifications need to be always accurate; I have had a few times where I've realized that it said it added it to the set, but it did not. It is rare, but has happened a few times. To fix this, I believe the notifications should be changed to be more verbose and accurate. For example, the order should be: Attempt to add to set > If failed, give error and reason > Otherwise, verify that post is now in the set > If true, then display "Added to set". Also It'd be nice if it had some kind of short-term log instead of only being able to show one message at a time at the top. If all of this could be realized then that'd be amazing.

* Sometimes when adding to a set, I get "error: " (blank) and it cant add to the set. This seems to only be on e621.net/post pages WHILE the URL contains previous search information. Happens fairly often to me, but not always.

* The 'add to set' button when viewing a post places the set selector in the middle of the screen which is very inconvenient, personally.

* I'd love a hotkey for adding to the currently selected set or the last-added-to set.

* Larger thumbnails when searching would be nice, but I can understand this not happening. It's a low importance nit-pick.

* I'm unable to edit or work with any set which is full/over 10k posts.
(Edit:)
* Also, sets are no longer listed in alphabetical order when adding to a set.

frans7 said:
* Larger thumbnails when searching would be nice

did something about thumbnails change when the site was upgraded?

bipface said:
did something about thumbnails change when the site was upgraded?

I dont know but I used to use a userscript to enlarge them which does not work anymore.

Can confirm that removing a post from a set with >10k posts just gives "Error: Sets can have up to 10,000 posts each". The post is not removed.

frans7 said:
I dont know but I used to use a userscript to enlarge them which does not work anymore.

which script?
(if you're lucky it might be an easy fix)

bipface said:
which script?
(if you're lucky it might be an easy fix)

Might be. I havent checked yet. Just depends on if it broke because of the layout or if it was because of a change in how the backend works.

frans7 said:
Might be. I havent checked yet. Just depends on if it broke because of the layout or if it was because of a change in how the backend works.

… can we see it ?

bipface said:
… can we see it ?

Oh, sure. I didnt want to derail far from the topic is all.
https://pastebin.com/HXh6cjc2

Hoping to not have this get lost in the forums though..

frans7 said:
Oh, sure. I didnt want to derail far from the topic is all.
https://pastebin.com/HXh6cjc2

The code is horrifying. It's also clever... but mostly just horrifying.
Not an easy fix. The API changed, the html for previews changed.
I could probably fix it, but I don't really want to, mainly because not only does it effectively load each image twice - once as a thumbnail, second as full-sized, but it also sends an API request for every single animated image on the page to replace the thumbnail with an animated version. Some people, who I will not name, kind of look down upon this kind of thing.

I used a bit of custom CSS to get the thumbnails to fit the page a little better.

div#posts-container {
    display: grid;
    grid-template-columns: repeat(auto-fill, 150px);
    justify-content: space-between;
}

article.post-preview {
    margin: 0 0 0.5rem;
    height: auto;
    width: 150px;
}

article.post-preview img {
    width: 150px;
    height: 150px;
    object-fit: cover;
}

But I don't think that this is what you are looking for.

bitwolfy said:
The code is horrifying. It's also clever... but mostly just horrifying.
Not an easy fix. The API changed, the html for previews changed.
I could probably fix it, but I don't really want to, mainly because not only does it effectively load each image twice - once as a thumbnail, second as full-sized, but it also sends an API request for every single animated image on the page to replace the thumbnail with an animated version. Some people, who I will not name, kind of look down upon this kind of thing.

I used a bit of custom CSS to get the thumbnails to fit the page a little better.

div#posts-container {
    display: grid;
    grid-template-columns: repeat(auto-fill, 150px);
    justify-content: space-between;
}

article.post-preview {
    margin: 0 0 0.5rem;
    height: auto;
    width: 150px;
}

article.post-preview img {
    width: 150px;
    height: 150px;
    object-fit: cover;
}

But I don't think that this is what you are looking for.

No worries. Not the purpose/focus of this thread anyway. I'll give your snippet a try though.

Bumping once.