Posted under General
One issue I'd like to report that I haven't seen mentioned is that comments (both ones you've made and replies) don't show up if the comments are on images with blacklisted tags. There is a way to view them, by clicking said blacklisted tags at the top of the screen. However, that also shows the image itself rather than the "Blacklisted" thumbnail.
Even stranger is that, for comment replies, if the user has a blacklisted avatar, that still shows up as the "Blacklisted" thumbnail.
Why in the hell are favorites capped? Is that your way of saying that it’s now okay to have as many accounts as you want? Add that to the fact that this format hurts my eyes and I think I’ll be gone from this site for a good while.
It would be nice if you at least addressed WHY favs are capped.
Edit: As for useful feedback, it would be a HUGE help if you could make the buttons bigger for mobile users. Especially the up/downvote buttons. I must have hit a separate link a dozen times before getting it right.
Edit 2: What’s up with the edit function? It doesn’t automatically bring up the keyboard when I click it anymore; it’s got tags separated on different lines for some reason; and instead of submitting when I press “return,” I need to scroll to the bottom of the screen. Such a bigger hassle than before.
Updated
Change it back.
No. The beta was open and public for nearly 5 months. We gave ample warning and opportunity to chime in with the feedback, including a news item for a month \
No, that was your fault for hiding the beta in the news bar that wasn't open by default. (Also failure to notify users that the website is changing)
If you want it the new one, create a domain for legcy e621 we preferred that way
most of the user base come from a subreddit furry_irl and failure to notify us
Updated
What exactly is in the public blacklist at the moment?
twobrains said:
lol at these "forced to make an account" jackasses. imagine publicly admitting that you're upset that e621 made it _slightly_ harder for pedophiles to get off
I thought that it was funny because I made a account a while ago just so that I could comment on posts...
bleph said:
What exactly is in the public blacklist at the moment?
gore
scat
watersports
young -rating:s
loli
shota
tokaitori said:
Bruh. Cub isn't pedophilia.
It isnot? How do you figure?
twobrains said:
lol at these "forced to make an account" jackasses. imagine publicly admitting that you're upset that e621 made it _slightly_ harder for pedophiles to get off
Pretty rich of you to look down on other people for liking cub art, while also using the same website that hosts cub art and thus implicitly supporting it. And also having feral art in your favs. Hate to break it to you but normal people look down upon zoophilic art about as much as pedophilic art.
If you think that cub art is morally unacceptable, live by your own standards and don't use this website. Otherwise you have no pedestal to stand on.
qwazzy said:
Thanks. "young -rating:s" is pretty questionable, that tag gets applied to characters that are not underage. And it's going to continue getting used that way regardless of the description of the tag, since 'young' IRL covers a broad range.
bleph said:
"young -rating:s" is pretty questionable, that tag gets applied to characters that are not underage. And it's going to continue getting used that way regardless of the description of the tag, since 'young' IRL covers a broad range.
I'm guessing their reasoning for adding it is that to the uninformed first viewing of someone new to the site, it would appear to be underage content even if in actuality it isn't. Just like how they enforce the tagging system - in many cases it's more about how it appears to be rather than how it actually is.
The entire mandatory blacklist is arbitrary and stupid. You hide all watersports from anyone without an account, but rape is perfectly fine? Default filters are fine, but you shouldn’t need an account to turn them off.
bleph said:
Pretty rich of you to look down on other people for liking cub art, while also using the same website that hosts cub art and thus implicitly supporting it. And also having feral art in your favs. Hate to break it to you but normal people look down upon zoophilic art about as much as pedophilic art.If you think that cub art is morally unacceptable, live by your own standards and don't use this website. Otherwise you have no pedestal to stand on.Thanks. "young -rating:s" is pretty questionable, that tag gets applied to characters that are not underage. And it's going to continue getting used that way regardless of the description of the tag, since 'young' IRL covers a broad range.
LEGALLY, bestiality is technically legal across the United States is is fully legal is 5 states (D.C., Hawaii, New Mexico, West Virginia, and Wyoming). The sentence per state ranges from $500 fine, to $20,000 fine plus 3 years in prison.
A full gambit pedophilia conviction will land you a heafty fine and incarceration between 15 and 30 years.
While common people _*might*_ view this things equally, the (US) law certainly does not.
How do I resize images that are too large?
I'm not the only one missing no longer being able to see who +fav'd a given artwork as we could
a) discover new art +fav'd by others with similar tastes which would've been missed otherwise.
b) find friends whom we hadn't seen for years!
As upvotes and +favs are now both "anonymous" the former now seems to be superfluous which is a pity as before it was possible to anonymously hat-tip good art for those who preferred to do so rather than add their names visibly to the +favs.
This shouldn't really be an issue as accounts here don't tie into anything IRL, anyhow, unless the user wishes. (Had all these discussions on FA way back in 2005... :)
Cheers!
how come you can't search tags among your favorites anymore?
Now get rid of the cub porn.
oh you've fucked the API too haven't you
god damn it e6
I'm wondering whether or not some changes are here to stay:
1. Will links to the parent posts stay at the bottom of the post currently being viewed. It seemed more convenient when they were next to the post's top left corner.
2. When I click on the comments section there's no longer a link for me to go directly to "comments on your posts". I know there are other non-complicated routes to get there, but it was a convenient shortcut if you were already on the comments page.
3. Someone probably brought this up already, but the posts don't show the name of the uploader anymore.
4. The message inbox is now organized so that older messages are on page one. Is there a way to reverse the order in settings?
To all the people mentioning the auto blacklist and suggesting it's all cub porn lovers, you realize that only half of the block list is young, right? Watersports is somewhat common, scat.... Sadly is too... But my main issue is that randomly blocking crap will stop me finishing comics I'm reading. Gore is blocked too, that could class as "mutilation" to anything as little as a nasty scratch. Ergo, anything dark and violent (which there is some cool creepypasta style artwork on here) or even remotely violent will be blocked too if tagged like that.
A forced blacklist forces us to log in to continue viewing things as simple as a fight scene. It's not always about porn, even if this site is full of it.
Oh, and obligatory "IT'S FAKE" comment. And bestiality isn't on that list so.... If people complaining about auto blacklists are pedos, by your own logic you're suggesting those who aren't complaining shag their pets. Just say, maybe don't throw stones in this glass house we're all stuck in. We're all gonna come out of it badly, so let's TRY and be civil, ya?
getagrip said:
3. Someone probably brought this up already, but the posts don't show the name of the uploader anymore.
Can't speak for the other points, but this one was intentional - there's a stickied forum thread listing changes that are intentional.
qwazzy said:
Can't speak for the other points, but this one was intentional - there's a stickied forum thread listing changes that are intentional.
Which is honestly sad, between that, favorite cap, and other stuff being INTENTIONAL it's clear they don't intend to go back to how the old site was at all.
murrsuit said:
how come you can't search tags among your favorites anymore?
That seems to be a change made in response to another issue. I'm neither on the E6 staff nor a coding genius but I'm guessing that with the updated website, any kind of search was always set to list things in order of upload date. The favorites list, with the ability to search tags, was essentially just a tag search itself (fav:"user"). As a result, everyone was having an issue with their favorites being sorted by upload date rather than order favorited. As a work around, all direct links to one's favorites was changed to a specific page with no search option.
That said, you can still tag search your favorites by typing "fav:user" and then your tags but as mentioned, that will change the sorting until everything is cleaned up.
Updated
Hello, not sure where to post this;
I went to try and upload something and noticed everything looked different (think i liked the old uploader better), but with the new one; i couldn't even notice i had "pressed" the different buttons since the "pressed button" color was almost the very same as the "not pressed button" and it took me some bunches of clicking and glaring intensely at my screen to notice; there was a difference.
-Could you change the color of the clicked button to be more obvious when clicking it?
or just make it some 2-3 times darker when clicked so it's easier to tell.
Reading through this and seeing the complaints about the favorites cap shocks me a bit. I thought I faved things on a whim way too often (~23k apparently) for things I appreciated, but 80k? Holy crap!
Granted, I'm also interested in more detailed information about why the cap was implemented (stability is awfully vague), but still!
qwazzy said:
Can't speak for the other points, but this one was intentional - there's a stickied forum thread listing changes that are intentional.
Has there been any explanation for why?
I really think it's odd that the only nod to violence in the default blocklist is "gore". Rape, torture, vore, snuff - perfectly fine on the homepage, as long as it's not bloody!
Epilepsy_warning probably ought to be on the list too, simply for safety's sake.
felisae said:
Reading through this and seeing the complaints about the favorites cap shocks me a bit. I thought I faved things on a whim way too often (~23k apparently) for things I appreciated, but 80k? Holy crap!
I also thought that I should start pruning my favs, and I only have 8,000... I've been on this site for years. 80,000 seems like an unreachable number.
e: now that I think about it there's no way someone like Karackas actually fav'd 92,000 posts in 9 years. That has to be via a bot or something automatically faving posts without looking at them, nobody is legitimately faving over 10,000 posts in one year
Updated
felisae said:
Reading through this and seeing the complaints about the favorites cap shocks me a bit. I thought I faved things on a whim way too often (~23k apparently) for things I appreciated, but 80k? Holy crap!Granted, I'm also interested in more detailed information about why the cap was implemented (stability is awfully vague), but still!
I'm kind of shocked, too. IMO if you're favoriting tens of thousands of things, you should just download them and have an organization system based on artists, content, whatever. You're going to be in a world of hurt if several artists suddenly do a DNP or the site has an error and loses data.
Unrelated: There's a dude on Derpibooru who literally favorites *every single image* ever uploaded.
so what was wrong with the old layout that had been working for years
so what was wrong with the old layout that had been working for years
livinginadeadworld said:
Now get rid of the cub porn.
No. They won't. Please go away or use your blacklist.
bleph said:
I also thought that I should start pruning my favs, and I only have 8,000... I've been on this site for years. 80,000 seems like an unreachable number.e: now that I think about it there's no way someone like Karackas actually fav'd 92,000 posts in 9 years. That has to be via a bot or something automatically faving posts without looking at them, nobody is legitimately faving over 10,000 posts in one year
10K posts per year is only 27-28 posts per day. Even that might seem like a lot but someone who heavily uses the site wouldn't have much trouble reaching that on their own. In fact, a bot would probably be much higher over that time frame.
blackasnight said:
It isnot? How do you figure?
Ask the moderators and janitors and they will happily explain to you the difference between a drawing of a furry and irl CP, and why Cub porn is not going anywhere off this site. It is too late in the day for me to get into a debate about this.
The short version is, because it's pictures of smol animal people which obviously don't exist irl, there's no real way for somebody to go "omg it's literally irl child pornography" without sounding like you've got a screw loose and stretching so far you could be a human bridge spanning the Grand Canyon, and there is literally no law on the books in the U.S that deals with "anthropomorphic artwork", so it's allowed here, while human-based loli and shota are more of a debatable topic that could get someone in trouble depending on the state they live in.
If you want a better explanation because I'm fucking tired and it's almost midnight, ask a mod or a janitor or just go on but remember that insulting other users for liking cub art or calling them "pedophiles" is against the rules.
Updated
Seems harsh to just obliterate the mascots, Esix was one of the things that made the site.
Just realized another complaint I have. Being dumped RIGHT into the images is jarring, while I wouldn't recommend your average user to go pulling up e621 on the bus it still might create some awkward situations.
potatopleaser said:
so what was wrong with the old layout that had been working for years
Nothing was wrong with the layout itself. But the site is working on a completely redone codebase now, and the old themes unfortunately can't work on it. The current layout is only temporary though, and it will become more like it used to as the site is worked on.
watsit said:
Nothing was wrong with the layout itself. But the site is working on a completely redone codebase now, and the old themes unfortunately can't work on it. The current layout is only temporary though, and it will become more like it used to as the site is worked on.
You absolutely certain that it will? Personally I think the new site look reminds me of New Reddit.
gbillybob said:
You absolutely certain that it will? Personally I think the new site look reminds me of New Reddit.
That's what the admins are saying, and I don't have reason to doubt them right now. If there aren't any notable changes in the coming days or weeks, I might get concerned about it, but for now it's only been little more than a day.
notmenotyou said:
How do I get the old themes back?
You don't. Those are no longer compatible with the new site and had to be axed. Though we do want to bring them back one by one as soon as possible. However right now they're on the bottom of the list of things that need doing.
The current layout is terrible.
It will be improved and polished as time goes on. Getting the new codebase up and running had a higher priority than making it look pretty, simply because the old codebase was basically held together by wishes and duct tape, and was vulnerable to a few things on top of having atrocious performance.
If you're good at CSS have a look at this thread and feel free to provide feedback or CSS snippets, that'll help us get things polished that much quicker.
Change it back.
No. The beta was open and public for nearly 5 months. We gave ample warning and opportunity to chime in with the feedback, including a news item for a month. It's also straight up impossible to change it back because of the massive incompatibilities between the old software and the new one. However, the end goal is to have the current layout prettied up that it will be as good as (or even better) than the old one.
Please change this shit back. Lack of Feedback is a BAD thing, you idiots. If you aren't getting enough Feedback, that means it's bad and people don't want it! You only push things through when you have GOOD Feedback.
As for getting it working, before it looks pretty, works with Video Games, but NOT with a Website, as there is literally NO BUGS that can exist! Either a button is working cause you went to that page and coded the button to work. Or you didn't code the button and so it doesn't exist. You're talking basic HTML foolproof coding here to get a website 'Bug Free'. But visuals on a Website are much more needed, cause if a site doesn't look good, people will just go else where.
Change it back. No one reads the news, no one does 'beta testing', no one even goes on the forums rarely. Most people visit the site to look at porn, most of the time without needed an account as it was simple and basic, and they can't do that now. You've literally forcefully HID some of the porn away, and now my friend can't even access the porn he likes searching for on this site cause of it and will be moving on.
And YOU, are 100% to blame, not us Users. YOU made the update, YOU pushed it forward, YOU went from hosting a good solid website for YEARS to disgusting website the people that don't want to make an account can't enjoy or use. You are LITERALLY following Youtube's example, making a change no one wants, forcing it to happen, and refusing to change it back! What the fuck man?!
Did you ever think, just maybe for a moment, that the reason nobody talked about the beta was because few people saw it, and of those that did, they didn't like it, care about it, or want it?
You know how the common policy is, if you don't like an image, don't comment about how shitty it is, just tab away? Maybe that mindset carried through to your shitty redecoration. Blaming it on the userbase for not giving you feedback about shit this obvious is incredible. What kind of brick wall, unassailable in its stupidity, actually says this shit to excuse a downgrade? Generally the type of dev that makes a downgrade knowingly, I suppose.
This is not a redecoration. The layout is largely an afterthought. As was stated in OP.
The fact that users primarily interact with the frontend, and thus conclude that a downgrade in UI is a downgrade full stop, is a problem.
UI is the 10% of the thing that you staple onto the backend when you have time. That is especially the case when your entire team is volunteers.
It wasn't a secret that this change was primarily about fixing the backend (making things -- the technical underpinning of the site -- work better), AFAIK.
I just want to say thank you for just updating it. Sure there are some problems around, but it's not like the site's unusable. Hate it, when old software does not get updated because it needs to "just run" and it just gets more spaghetti as time goes on. So thank you for just publishing it, appreciate the work that went into that.
notmenotyou said:
Because the codebase was done for a few months now and nobody wanted to provide additional feedback on the layout during the beta.
Like, we gave ample notice and options for people to chime in. Both threads were in the stickies for ages.
My Biggest problem is that I cant see a single picture on my ipad. I set the setting to show the lowest amount at the smallest thumbnails possible and it still doesn't work. this ipad has been able to view this site for years until now. I don't know what else to do and its my only source of this site.
savageorange said:
This is not a redecoration. The layout is largely an afterthought. As was stated in OP.The fact that users primarily interact with the frontend, and thus conclude that a downgrade in UI is a downgrade full stop, is a problem.
UI is the 10% of the thing that you staple onto the backend when you have time. That is especially the case when your entire team is volunteers.
It wasn't a secret that this change was primarily about fixing the backend (making things -- the technical underpinning of the site -- work better), AFAIK.
When the layout is almost entirely what the userbase interacts with and sees, it's a lore more than 10%. The people defending this, and the team here really show just how little they actually know about how anything works. Doesn't matter if no one wants to interact with it, or are willing to wait for it to get back into what they see as a usable state.
savageorange said:
This is not a redecoration. The layout is largely an afterthought. As was stated in OP.The fact that users primarily interact with the frontend, and thus conclude that a downgrade in UI is a downgrade full stop, is a problem.
UI is the 10% of the thing that you staple onto the backend when you have time. That is especially the case when your entire team is volunteers.
It wasn't a secret that this change was primarily about fixing the backend (making things -- the technical underpinning of the site -- work better), AFAIK.
The frontend is literally the only thing that matters. The entirety of the backend is to facilitate the frontend working. This is why there are so many thousands of ways to create a backend, but you still have to have text on the frontend in English (or whatever language you're marketing at) regardless of how you coded it to happen.
User interface is 10% of the work, but the entire point of the other 90%. If the users want to interface less, then it is a downgrade, full stop. Websites don't exist just to exist.
bug_sis said:
The frontend is literally the only thing that matters. The entirety of the backend is to facilitate the frontend working.
The frontend can't do anything if there isn't a backend to do the work. And a good frontend means little if the backend is crap, so no, the frontend isn't the only thing that matters. A good frontend with a bad backend is still a bad site, while a serviceable frontend with a good backend is still useful. So it's important for the backend to be stable before worrying too much about the frontend (this is FA's main problem, that they have a problematic backend and can only try to hide it with changes to the frontend that doesn't actually fix the core problems). The old site's backend may not have been "bad" in the sense of being unusable, but it had its limits that required an update like this to fix.
blackasnight said:
LEGALLY, bestiality is technically legal across the United States is is fully legal is 5 states (D.C., Hawaii, New Mexico, West Virginia, and Wyoming). The sentence per state ranges from $500 fine, to $20,000 fine plus 3 years in prison.
A full gambit pedophilia conviction will land you a heafty fine and incarceration between 15 and 30 years.
While common people _*might*_ view this things equally, the (US) law certainly does not.
Actually, zoophilia was deemed illegal on a federal level not that long ago. So That is outdated information.
watsit said:
The frontend can't do anything if there isn't a backend to do the work. And a good frontend means little if the backend is crap, so no, the frontend isn't the only thing that matters. A good frontend with a bad backend is still a bad site, while a serviceable frontend with a good backend is still useful. So it's important for the backend to be stable before worrying too much about the frontend (this is FA's main problem, that they have a problematic backend and can only try to hide it with changes to the frontend that doesn't actually fix the core problems). The old site's backend may not have been "bad" in the sense of being unusable, but it had its limits that required an update like this to fix.
You seem not to have read my comment very well, so I'll reiterate; the only point of the backend is to facilitate the frontend, therefore the buck stops with the frontend's quality. If the user experience is worse, then it is a total and complete downgrade. If the backend was serviceable, then the update to the site layout is unnecessary and pointless. No limits had to be surpassed because everything was working. If the backend wasn't serviceable, then the admins are absolutely incapable of communication, because they spent most of their time being catty, blaming the userbase for not liking the update, and making information hard to find rather than explaining themselves.
The user experience is literally the only thing that matters, and so what the user interacts with is the only thing that matters. If the site was gonna fuckin' die because of the old layout for some reason, then yes, sure, that would be a worse user experience than the current update. But if things were going steady and they were just "limiting" some """upgrades""" ala Youtube style pointless updates, then no one cares. The backend exists solely to facilitate user interface. This crap about "think about the mess of code behind the scenes, we must sacrifice some of the UI in order to fix it" is backwards logic. Sacrificing user interface to make dev interface more pretty is stupid.
Found another issue that happened. The location of notes (or whatever the grey boxes of text that are used to hold translations or spelling fixes are called) have gone to incorrect places on a number of images.
hello there is no way to work on internet explorer?
Okay. I will try to be understanding that you had little choice but to change the site or else end up with a mess down the line. I can accept that. Good for you coders and volunteers that worked to make that happen. I understand that you are still working on the site to make it more functional and that you could not do a direct 1:1 change over to the UI. This sucks and I wish that the coders and volunteers had put in a few more months getting it to the as close to a 1:1 interface as they could, instead of me personally having to use the site in its current state. It's selfish, greedy, and undercuts the hard work you all put in but welcome to the world of trying to please a user/customer/client.
All that said here are my criticisms of the current site/UI:
*Bring back the start page - people liked it and miss the mascots, I am among them. I really don't see how not having it saves much for site resources and bring it back would quite *some* complaints.
*Bring back the "+" and "-" signs by the tags - It really simplified usage of the tags. I won't claim to know the coding effort required for that but please try at least.
Also, just for clarification can you all explain some changes that were made and why? Namely: "- Uploader name is not shown on the posts page." Just curious, not angry.
Thank you all for your hard work. You are under appreciated (and will likely remain so) and easy targets of spite when the users are unhappy (I suspect some of you are masochists). Please continue doing your best to return the UI feel to the old design as best you can. We will continue to complain and let you know when we feel you've screwed up.
bug_sis said:
This crap about "think about the mess of code behind the scenes, we must sacrifice some of the UI in order to fix it" is backwards logic.
Strawmen often are backwards logic.
The backend exists not only to facilitate the frontend but also to facilitate the developers and administration. If all your coders are volunteers (which is the case for e621) and you decide against making their lives easier, well, you might end up with less coders and less maintenance.
(BTW, the admins are ALSO volunteers...)
I think that it's obvious here that treating ordinary user experience as a benchmark of usability is inadequate, especially in the period immediately after a transition. Even though it should be a major *factor*.
Would you believe my browser got revamped the same day than the site, and I only knew of the first?
At least I can expect both the browser and the site to get better
But in the meantime, would it be too much to ask to get back the Front Page?
Is there any way to resize an image as you're looking at it?
houseofire said:
Is there any way to resize an image as you're looking at it?
You might find that right click -> view image will let you use the browser's zooming (mouse scroll wheel) on a given image, if that's the kind of thing you mean.
This is probably dependent on whether you are using the 'reduced samples' option or not.
Personally I prefer to hover over the image with Imagus, but that's a browser addon (and requires some setup for e621).
I gather that the Download link is going to be swapped back to open in the same tab, in which case it will be functionally equivalent to 'View image'
Edit: oh, the hexagons are back.
Feedback:
- I never found anything lackluster about the previous layout.
- The pool name "Search: (empty)" provides a useless bar that gets in the way when viewing an image from the front page.
- The purple text for pool names makes no sense (where is purple used as a primary color on this site?) and is hard to read.
- I dislike the pool and search navigation being ABOVE the image; I clicked on the image to view it, not to view the pool navigation bar. It would almost be better tucked away in the sidebar where it's readily available without pushing the image down.
- The text seems much less readable than the previous theme. Almost as if it's missing antialiasing/sub-pixel hinting. This is particularly noticeable on tag names and the "Account | Posts | Comments ..." nagivation bar.
- The fave button below the post looks out of place, and is redundant with the favorite link in the side bar by the up/down vote buttons. I think it makes more sense near the vote buttons anyway.
Overall it mostly seems the same, a little less childish, but with a few more annoyances.
Updated
houseofire said:
Is there any way to resize an image as you're looking at it?
Under the image, there should be a Change Size Mode (...) link. Clicking that switches between Sample, Scale To Fit, and Original.
Logged in after months to say that the change isn't welcomed. I didn't see no beta like others. There is a lot to improve if you want this site better than it originally was.
If you need some assistance creating an architecture wherein the codebase can be upgraded arbitrarily without any noticeable alterations to the user interface, I could offer some pointers.
For now, I'll just point out that the login process does not navigate back to the page that the user had logged in from. Which is... really, really basic.
dieselwzl said:
Actually, I just remembered another one that annoys me.When doing certain searches, I like to disable my blacklist (or at least certain parts of it) temporarily to see things that are borderline for me (hit and miss subjects that I like in specific circumstances). Used to be, that was page-specific and refreshing or looking at another page would reset it to hidden. Now? It's disabled permanently site-wide until I re-enable it, meaning browsing different pages/searches in different tabs will result in seeing things I don't want to see. This may be a niche complaint, but still, the old way was better. Also, the blacklisted tags being shown all the time is a poor decision compared to the hidden drop-down that it used to be.
I would like to second this. I'm fine with most of the changes so far, but the way the blacklist seems to be working globally and not site-specific is really annoying to me. If only for thecase that it can still blacklist a picture after I opened it. I mean, I think it's safe to assume that, once I click on the image, I actually want to see it.
Is there a specific reason why the blacklist is still getting applied on an image post itself? (see https://www.screencast.com/t/HcAXQn24XZ )
Actually that makes sense to me, it should just be special-cased a bit based on where you came from.
Consider the case where you click on the Random link (or trigger it via keyboard) and hit a post that would be blacklisted. You probably don't actually want to see that. But when you click in from a post/index page, user avatar, or forum/comment embedded thumbnail, you *would* want to see that.
(TBH an 'auto-repeat' option would also make sense for when you hit Random and get a blacklisted image)
EDIT: this is a slightly complicated problem because in the cases where an image should be shown, the blacklist should still apply to all other images (such as user avatars and post thumbnails in comments). If I was implementing it I'd probably add a bit of data which would be 'id of an image that should be temporarily whitelisted', and make that a normal part of blacklist processing.
Updated
Guys, stop panicking and freaking out. It's hard to transition to a new UI, but it gets better.
I remember when Microsoft office completely overhauled their UI from Office 2003 to Office 2007. Like, they changed absolutely everything. I hated all of it. I was really pissed for a long time. And then I got used to it. And then I was like, oh, this is fine, what was I so mad about?
So I stopped being mad when software UI changes, because you'll forget all about it next month.
So, seriously, take a deep breath and go look at some porn.
toboe said:
Guys, stop panicking and freaking out. It's hard to transition to a new UI, but it gets better.I remember when Microsoft office completely overhauled their UI from Office 2003 to Office 2007. Like, they changed absolutely everything. I hated all of it. I was really pissed for a long time. And then I got used to it. And then I was like, oh, this is fine, what was I so mad about?
So I stopped being mad when software UI changes, because you'll forget all about it next month.
So, seriously, take a deep breath and go look at some porn.
There's a lot more being complained about than just the UI appearance.
shishigumi said:
imagine posting a livid wall of text on an online forum complaining about a fetish porn site undergoing maintenance. some of you need to seriously reevaluate your lives since this is clearly something that makes a notable effect on you.
Maintenance? This isn't maintenance, this is a complete redesigned of the entire website with tons of changes that nobody wanted and nobody likes, after putting in the bare minimum effort required to warn people. Literally 90+% of the userbase had no idea there was a beta in the works, let alone that the entire site was going to be changed out of the blue with no way to go back to the old version.
"90+% of the userbase?"
Yeah, you pulled that out of your ass.
Nobody knows what percentage of the users knew. If we counted up the users who are actually complaining (that is - users for whom we have positive evidence that they didn't know), we wouldn't even reach 1% of the user base (stats page is broken ATM, but from memory, 1% would be about 3000 users). It would be a bad sample though, because it would actually be testing 'AMONG THE USERS WHO ARE VOCAL, how many didn't know?'; that's an example of self-selection producing a biased sample.
Here's another bullshit stat:
98% of people who post statistics are not statistically literate enough to understand the actual implications of the statistics they are posting.
mrjohnson said:
I rate this: Yikes/10.Edit: And before I forget, I don't recall any warning about this 'Beta'.
Edit 2: 'Search' no longer keeps previous info, and as such, it is a pain to look up tags for every 'Daily' scan.A Shameful Display!
Your problem with the search bar is the auto complete function, you can get back your last searches by disabling it in the account settings under the advanced tab
Can we not turn off the post statistics on our Favorites page any more?
hungfox said:
Can we not turn off the post statistics on our Favorites page any more?
I've never tried this option before, but I think I can confirm this bug.. the setting doesn't seem to have any effect on favorites, though it works fine on normal /post/index pages.
(I'd kind of like an option to disable the 'trending tags' / tag histogram too.. that was my initial guess at what this option did.)
abscondler said:
Maintenance? This isn't maintenance, this is a complete redesigned of the entire website with tons of changes that nobody wanted and nobody likes, after putting in the bare minimum effort required to warn people. Literally 90+% of the userbase had no idea there was a beta in the works, let alone that the entire site was going to be changed out of the blue with no way to go back to the old version.
Speak for yourself. I am happy with the new features so far. I have been waiting for privacy mode on e621 for years. I haven't been comfortable adding NSFW images to my favorites until this option became a thing. I'm looking forward to the new lore tags as well. They will expand the ways we can find the images we want to see, and make less people pissed off that their art is featured on the site. I'm sure that is one of the drivers of the motivation to get the new site launched as soon as possible.
If I could make a request, I'd prefer if the indicator that the post I'm looking at has a child/parent/sibling was somewhere closer to the top. On a 1080 pixels high monitor at 100% scaling, using the 850px resized "default image width" setting, with portrait shaped images it's never visible without scrolling down.
Also I don't like that you have to click twice to see, and then open the related post. Can you make it a setting where we can change that tab to always be open by default, just like the "Description collapsed initially" setting, or just make it globally remember whether I like that tab open or closed?
I'm a lot more concerned with the attitude and approach than the results. I barely even notice a difference. But recognizing what they could have done, and just... didn't? And to pass it off as some necessity to people who might fall for that? That hurts my pride as a developer. People should be better than this.
And for the record, I also did not receive any notification of a beta. Not even in the news bar at the top, which I checked as recently as last month.
Edit: lul I just noticed where parent/children links have moved and WOW. I... wow.
_raven_ said:
Your problem with the search bar is the auto complete function, you can get back your last searches by disabling it in the account settings under the advanced tab
Oh thank you for this, I was hoping someone had information about that, or else I'd have a lot of browser history to surf through to get my normal search terms to bookmark for quick searching instead of using the search field.
As to the whole "you had 5 months", I'm gonna echo a lot of other voices that I didn't see shit about it. Last news header before this dropped that I saw was from July about there not being a Facebook for the site(s)... you know, the "July 3rd: Because this..." that is directly below the "March 6th" stuff about "Welcome to the new e621".
When you get the codebase/design functional for a landing page, please slap the landing page and your plethora of mascots back up? I liked that over the generalized booru "here's a bunch of thumbnails" landing your new temporary design has as a landing.
digitalman said:
But recognizing what they could have done, and just... didn't?
The majority of the work done is on the backend, not stuff we can immediately see. Stuff like the server not bursting into flames when using more than 5 search terms. The current layout is known to be basic and will be improved after more serious issues are dealt with.
digitalman said:
And to pass it off as some necessity to people who might fall for that? That hurts my pride as a developer. People should be better than this.
It hurts me a little every time someone thinks any code improvement must have an immediately visible and tangible positive effect to be worthwhile. Having a clean codebase that you can easily maintain and build upon is just as important as having a working codebase. Having something that won't randomly fall over on Tuesdays when the wind blows 10 degrees north on a crescent moon night is good, even if most people may not be personally affected by the problem. Similarly if some people want new features, having a codebase that can easily handle them would be beneficial even if other people won't care. A working codebase is important, but if it can't be easily fixed when problems come up without something else breaking, can't have new features added that people want, and is under constant threat of collapsing in on its own weight, it's not in a good position (FA being the exception to prove the rule; the only reason they manage to hold on is largely social inertia, not because the site manages to stay stable and get features people want).
watsit said:
The majority of the work done is on the backend, not stuff we can immediately see. Stuff like the server not bursting into flames when using more than 5 search terms. The current layout is known to be basic and will be improved after more serious issues are dealt with.
See, this is actually my point. The CSS, JS, and HTML are separate files - the latter of which contain only very basic variable parsing, and a foreach loop for comments and tags. In no way did fixing the backend require altering the UI in a noticeable way, even if they were changing programming languages entirely. In fact, it is easier to handle them separately, so that you're not trying to figure out "why is pagination off by three" and "why is Firefox messing up vertical alignment" at the same time. And the UI didn't change in any functional way, it contains all the same information (image location, metadata, tag array, comment array) so they just needed the backend to call the existing UI files with the same variable names. Or, at worst, if they changed languages, add or remove a couple characters from syntax to match the new language. Even if I find the UI passable, the attitude that completely recreating these render files was somehow crucial to the codebase update is not. That is not how this type of code works.
One thing I dearly miss is the name of the user who uploaded an image. It would make sense to put it under the "information" section. Right now it just shows who approved it, and not who uploaded it.
digitalman said:
... nonsense ...
Your point would be presented a lot better if you knew what you were talking about.
CSS, JS, and HTML being completely separate... Yeah, right.
Foreach loops in HTML, that's just funny.
Changing the backend does not require changes in the frontend, if only.
Or the idea that the only way a back-end changes dramatically is if you switch languages.
You don't see too many functional changes because the front-end that you do see is essentially the old theme that was forced to work with the new back-end. It splits apart at the proverbial seams exactly because the back-end changed so much. It's not just the image serving portion - that works just fine, for the most part. It's... well, pretty much everything else that is a little janky at the moment.
