Over the past few months we've been working quietly away at modernizing the internals of the e621 site, and it is finally at a point where it's ready for others to come try it out.

https://beta.e621.net/

This beta is the first public iteration of our planned overhaul of the site proper.
To temper expectations: The current status of the beta site is about as feature complete as it's likely going to be for the time being, so the focus is on finding and fixing any remaining bugs. Though if you have any idea for small quality of life features we're open to them.

Please be sure to have a quick look at the changelog as well as the changes by design threads on the forum to see a quick overview of things that have changed so far.

Most rules concerning spamming have been lifted so that the page can be rough handled. DNP, Harassment, Illegal Activities, and similar rules are still in full effect, though. If you do something malicious we will ban you, potentially also from the live site. Don't use the beta for confidential information either, since the purpose is to test things, and test them well, expect that you have no privacy.

Once the beta has concluded all beta information will be destroyed, and we will start converting the data of the live site to work with the new site. We don't have an estimate how long the beta will run, right now it's going to last as long as needed.

If you have any questions feel free to ask them below and we'll try to answer them as best as we're able.

Please report beta related bugs on the forum for the beta site so that they can be more easily managed. If you absolutely cannot make an account on the beta, or otherwise refuse to, you may post your bugs here.

First bug, I believe, but this (1) (2) is what I enter into when I view the site while my phone is vertically aligned. When horizontally aligned, it looks rather normal, hence why I believe this is a bug. Is this a bug?

Siral_Exan said:
First bug, I believe, but this (1) (2) is what I enter into when I view the site while my phone is vertically aligned. When horizontally aligned, it looks rather normal, hence why I believe this is a bug. Is this a bug?

This is the mobile layout that prioritizes the images over other pieces because of the limited horizontal space allowed on mobile devices. This is normal.

KiraNoot said:
This is the mobile layout that prioritizes the images over other pieces because of the limited horizontal space allowed on mobile devices. This is normal.

Then, could there be a way to force desktop mode? I immediately tried that and couldn't.

Siral_Exan said:
Then, could there be a way to force desktop mode? I immediately tried that and couldn't.

I will see what I can do. The only checks in place right now are viewport width because the site tends to collapse in on itself when at very narrow widths. The "Request Desktop Version" checkbox should prevent the viewport meta tag from being used(which is what the user setting for this disables as well), so it theoretically should achieve the same effect.

Edit:
I have tried this on a few phones now and all of them show the desktop site when using the desktop site mode in the browser menu. I'm not sure I can reproduce the problem that you're having here of being unable to access a non-mobile version of the site using the the built in methods for disabling it.

I'm getting a lot of 429 Too Many Requests errors.

JAKXXX3 said:
I'm getting a lot of 429 Too Many Requests errors.

It appears that your browser is making a large number of requests to external resources that are blocked by the site security policy and it is flooding the server trying to report these infractions. This is most likely due to browser extensions attempting to load things from off site.

I created a new account to test the beta site (on desktop). I am not a UI designer, but here are a few questions that immediately sprung to mind:

This is everything I have noticed so far. I am sure there are other possible nits if I dug deeper, but this post is pretty long already.

Edit:
For the sake of getting more eyes on the beta site, I'd recommend announcing its opening on the e621 Discord under the announcements channel.

I would much prefer it if people with accounts on the beta would please post their feedback on the beta itself. There are several threads that cover various topics set up to help organize this feedback so that each topic can be addressed individually. Big dumps of feedback are hard to work with from a task list viewpoint, and harder for people to look through when seeing if something has been brought up before.

These great big lists are also extremely difficult to give feedback on because there are so many items grouped together in one place, that the only good way to providing feedback is through edits or lengthy replies, which obfuscates what has and has not been addressed.

If you would like to start a topic on the beta related to the settings page and the lack of documentation, that would be immensely helpful.

KiraNoot said:
I would much prefer it if people with accounts on the beta would please post their feedback on the beta itself.

Ah, whoops. I somehow managed to gloss over the last paragraph of the original post completely (was that there initially?). I'll go ahead and report these in the right channels, then.

Aegis29 said:
When toggling your entire blacklist on/off with "disable all" on the post index, it takes a few seconds to apply said action. (usually around less than a second on the main site) Is this delay expected?

I am not seeing long delays on this on my end, but I have a generally fairly fast workstation I use for development. If there are more reports of this I will look into profiling the blacklist code and seeing if it can be made more efficient.

Is this on mobile or desktop? I believe that mobile devices add a small delay(about .5 to 1 second) to click events before processing them in order to detect long touches. If this is on a desktop device it may be related to an extension.

KiraNoot said:
I am not seeing long delays on this on my end, but I have a generally fairly fast workstation I use for development. If there are more reports of this I will look into profiling the blacklist code and seeing if it can be made more efficient.

Is this on mobile or desktop? I believe that mobile devices add a small delay(about .5 to 1 second) to click events before processing them in order to detect long touches. If this is on a desktop device it may be related to an extension.

Desktop, I should have specified. If I find anything further I will post about it in the Beta Forum. (Where I should have posted this in the first place, my apologies)

https://beta.e621.net/static/terms_of_service

Danbooru?

Clicking Hot, on the top bar, then Popular on the sidebar gives:

felix_nermix said:
https://beta.e621.net/static/terms_of_service

Danbooru?

Whoops, that page should redirect to the wiki like it does on the current site. Thank you for pointing it out.

I don't get the whole 'crawlers, public username' thing. Why should I be worried about an anonymous name spreading over the internet?

MyNameIsOver20charac said:
I don't get the whole 'crawlers, public username' thing. Why should I be worried about an anonymous name spreading over the internet?

Because there are people who use exactly the same nickname all over the internet or possibly their real life name that's easy to connect to them, thinking that nobody else will see it as long as you do not interact with the website in any meaningful way other than favoriting etc. - which is false.

Some websites and especially forums have disabled bots from crawling stuff like userprofiles. So it's nice notice that "hey, don't be stupid, everyone can see everything you do, including google which then brings your names search results here".

The thumbnail for this does not indicate it's animated.

https://beta.e621.net/posts/40

It does for others, like.

https://beta.e621.net/posts/72

Mairo said:
Because there are people who use exactly the same nickname all over the internet or possibly their real life name that's easy to connect to them, thinking that nobody else will see it as long as you do not interact with the website in any meaningful way other than favoriting etc. - which is false.

Some websites and especially forums have disabled bots from crawling stuff like userprofiles. So it's nice notice that "hey, don't be stupid, everyone can see everything you do, including google which then brings your names search results here".

Using exactly the same nickname all over the Internet. Sounds like me, except I've used a different nickname on here, to save me some future embarrassment.

Mairo said:
Because there are people who use exactly the same nickname all over the internet or possibly their real life name that's easy to connect to them, thinking that nobody else will see it as long as you do not interact with the website in any meaningful way other than favoriting etc. - which is false.

Some websites and especially forums have disabled bots from crawling stuff like userprofiles. So it's nice notice that "hey, don't be stupid, everyone can see everything you do, including google which then brings your names search results here".

Ah, no worries then ^.^ thx for clarifying!

This happens here too I jut noticed.

post #2032666

furballs_dc said:
This happens here too I jut noticed.

Posts here only indicate they're animated if they have the animated tag.

Watsit said:
Posts here only indicate they're animated if they have the animated tag.

Oh, it doesn't detect it. Derp.

Checking the "Hot" page on mobile gave a long error:

not sure if it's small enough but there is a feature I'd thought of before but felt like it wasn't a good fit at the time.

one of the new feature's that's really cool is the ability to move between posts(a/d) from a post's viewing page. a detractor from this is that the blacklist posts are left in the list so if you move left or right and the next post is blacklisted you mostly just get a blank entry. blacklisting simple_background in the beta gives an idea of what that might look like in practice. a nice fix for this would be if the site looked for the next non-blacklist post and jumped to that but something tells me that would be hard to implement.

so the alternative might be to have a permanent blacklist of like 5-6 tags you know you just always or never want to see that would be auto added to any search. in the past this probably wouldn't have worked but now with the addition of another cool feature, a max of 40 tag entries for searching(YAY!! ^_^), it wouldn't be too big of a deal to just delegate up to like 6 of them to cut out stuff you always wanted hidden. an option to toggle even those on/off would be nice if it got implemented since it helps for tagging/wiki editing(I'll usually toggle off my filters if I'm tagging, researching something, or looking for example pics), but if this wouldn't be too much trouble I feel like it'd be pretty worthwhile.

https://beta.e621.net/iqdb_queries

The iqdbs link points to 127.0.0.1

Pupslut said:
https://beta.e621.net/iqdb_queries

The iqdbs link points to 127.0.0.1

It is currently only set up to accept searches for posts. There were some pretty obvious problems related to accepting arbitrary links. File upload is coming, but I need to write a proxy for it into the application, as it currently just points you at the server, and I don't want to expose the backend service to the internet(and it doesn't make sense to either.)

the window for adding posts to a pool should have a button to go back so i dont need to close the window and open it again. also, the menu shown after clicking "see all posts" is too wide, making appear a slide bar. maybe thats because my screen is too narrow? is 1360 wide yes i know is small.

GUNNER_24 said:
the window for adding posts to a pool should have a button to go back so i dont need to close the window and open it again. also, the menu shown after clicking "see all posts" is too wide, making appear a slide bar. maybe thats because my screen is too narrow? is 1360 wide yes i know is small.

I am seeing a close button for the add to pool dialog in the top right corner, does this not appear for you? I wonder if this might be an extension touching the class for it.

Also can you please give me more information for where the "show all posts" menu is, I'm having trouble finding what you are referring to.

KiraNoot said:
I am seeing a close button for the add to pool dialog in the top right corner, does this not appear for you? I wonder if this might be an extension touching the class for it.

Also can you please give me more information for where the "show all posts" menu is, I'm having trouble finding what you are referring to.

i meant see full list, sorry.

yes, i see the button too but if i click see full list, close the window and open it again it remains the same. updating the page fixes it but i thought a previous button (like ← on phones) would be better than closing the window and re opening it to go back.

If I could wish for any feature, it would be relational tags/ontologies. Especially on a site like this, it would be great if we could not just tag "female, male, human, fox, anthro, feral, blue_hair", but add context to them. "female<>anthro<>fox male<>blue_hair<>feral<>human" (what even is that).

Currently, relationships like that can only be expressed by making new tags, which inherently limits what you can do. Would make searching and blacklisting much easier.

Eww. It better makes up with functionality and features.

I don't know if it's intentional but I can do searches with more than 6 tags on the beta.

Zenti said:
I don't know if it's intentional but I can do searches with more than 6 tags on the beta.

If I remember correctly users can use 40 tags to search.

I remember seeing somewhere (search help, maybe?) that ~40-tag searches were allowed.

It's probably a temporary setting to help with debugging the site. No harm in it since the total number of posts that have to be queried is very small.

savageorange said:
I remember seeing somewhere (search help, maybe?) that ~40-tag searches were allowed.

It's probably a temporary setting to help with debugging the site. No harm in it since the total number of posts that have to be queried is very small.

I believe that it's intended to stay, I think Kira said the one fall back is that it can take longer for search inquiries to load

savageorange said:
I remember seeing somewhere (search help, maybe?) that ~40-tag searches were allowed.

It's probably a temporary setting to help with debugging the site. No harm in it since the total number of posts that have to be queried is very small.

Nope, this is an intended change. If there are enormous problems with search time, it may be lowered, but I don't expect to see any problems at only 40 tags.

If you click Blacklist and add a new tag, then close and re-open the blacklist, it doesn't show as being updated without reloading the page.

It's not a major bug but it made me wonder if it'd actually saved, and it could be awkward if someone wants to add more tags as they scroll down the page, as they'd presumably need to re-add the previous tags as well as the new one.

Pupslut said:
If you click Blacklist and add a new tag, then close and re-open the blacklist, it doesn't show as being updated without reloading the page.

It's not a major bug but it made me wonder if it'd actually saved, and it could be awkward if someone wants to add more tags as they scroll down the page, as they'd presumably need to re-add the previous tags as well as the new one.

You should say that on the beta site buddy so it doesn't get glossed over.

Retard said:
You should say that on the beta site buddy so it doesn't get glossed over.

I think Kira checks here, but I'll probably make an account soon, so I can test the other bits :)

Are we talking beta version or Sankaku-Complex-beta version?

post #70009

KiraNoot said:
Nope, this is an intended change. If there are enormous problems with search time, it may be lowered, but I don't expect to see any problems at only 40 tags.

was pretty sure it was a feature, nice to have it confirmed. again, yay ^_^

Myself and others have already suggested this feature in the Feature Requests forum (for years now), but I'll go ahead and put this here since it would be great to see in this new beta site:

Make the blacklist prevent, not just hide.

Even with making use of Extend and getting faster internet, blacklisted images will still appear (and still be clickable) for a short moment when loading a new page. One solution to this is simply bookmarking pages that have the search loaded with the minus key (-tag) to prevent the results of that page from having tags you don’t want to show up, and sticking with that bookmark’s set of searched tags.

The problem is the moment you leave and go to a page without your bookmarked search settings, the -prevented tags still appear for that short moment.

You could just stick with the bookmarked page with -prevented tags and never leave, but that’s no fun.

The feature I’d suggest is making the blacklist function like the minus key in a search, so blacklisted images don’t appear in the first place. And, you'd be able to turn it on/off if you prefer.

Why would it be useful?

It would make the blacklist really DO what its purpose is for: Making so you don’t see anything on that list at all. For more casual users or people with slower internet, it’ll help them more effectively avoid seeing things they don’t even want a glance at. For more compulsive users, it’ll help them avoid wasting time and break bad habits more successfully.

What part(s) of the site page(s) are affected?

All post/index pages, according to what you put in your blacklist.

And since they've explained that this feature idea is a server-side vs. client-side issue, these are my layman's ideas for making it technically work with the current limitations:

1.) Make every post/index page's search bar always have whatever tags (or minus tags) you always want active. You could bounce around to different artist pages, and the -tag you want always blacklisted won't ever pop in because it's default on the search bar.

Or...

2.) Only show the page when it's done loading. Until then it could just be an image of a blank e621 page (or whatever image you want), and by the time it's done loading the blacklisted thumbnails are already gone.

I’ve run searches for doing that sort of thing (making ‘loading screens’ to make sure a page is fully ready each time), but I’ve only found people talking about that for making websites, not changing current ones.

Human-Shaped said:
Myself and others have already suggested this feature in the Feature Requests forum (for years now), but I'll go ahead and put this here since it would be great to see in this new beta site:

Not wanting to be rude, but Kira replied to the main thread on this site about that, and it's also on the beta forum.. I just don't quite get why you posted it here when they're obviously aware of it..

Pupslut said:
Not wanting to be rude, but Kira replied to the main thread on this site about that, and it's also on the beta forum.. I just don't quite get why you posted it here when they're obviously aware of it..

It's all good, I thought the link you gave me was a good opportunity to put it in other places where more folks could see it. I know Kira knows, but I figured not everybody does so why not~

KiraNoot said:
Don't use the beta for confidential information either, since the purpose is to test things, and test them well, expect that you have no privacy.

It's like you are implying that we have some kind of privacy here. A delete account function would be perfect in the new website, apart from a better control of the data for every user.

e621 will not disclose the IP address, email address, password, or DMails of any user except to the staff.

e621 is allowed to make public everything else, including but not limited to: uploaded posts, favorited posts, comments, forum posts, wiki edits, and note edits.

e621 privacy policy is horrible to everyone in here, and leave everything to the good faith of the staff. So an option to hide things from at least from other people/bots that are not even users would be perfect.

AphoticEscapade said:
It's like you are implying that we have some kind of privacy here. A delete account function would be perfect in the new website, apart from a better control of the data for every user.

It's already possible to delete your account on the beta site:

Delete Account

You can delete your account. This will not actually remove your account from the database, but it will do the following things:

Rename your account to a generic string
Scramble your password
Remove all your favorites
Blank out your settings (including email)

[/quote]

AphoticEscapade said:
Privacy Policy

e621 will not disclose the IP address, email address, password, or DMails of any user except to the staff.

e621 is allowed to make public everything else, including but not limited to: uploaded posts, favorited posts, comments, forum posts, wiki edits, and note edits.

e621 privacy policy is horrible to everyone in here, and leave everything to the good faith of the staff. So an option to hide things from at least from other users would be perfect.

Firstly, there's a private mode on the new site, where you can hide your favourites, secondly, what else is there that you'd want hidden?

I'd agree it's a bad policy, saying "we can share anything else", but E6 doesn't keep any other private data, such as banking info, your real name (unless you set that as your username or disclose it yourself), your address, phone number, etc.

The only thing linking this account to you is your ip address, which is hidden and changes for most people and then still would need a lot of work to specifically find you, your email address, which is hidden, and your username, which you chose and can change.

The only thing I can think of that might be missing is that they won't disclose hidden forum posts, but people could easily quote you before you hide a message.

It'd be better to discuss the privacy policy in another thread though, if you want to create one.

Edit:
I completely missed the link, it would make it better, but it's already been said by staff somewhere that they don't keep data outside of general web logs and I'm sure someone's said that don't sell data before.

I'd suggest making a thread to get clarification though.

I liked having a bit smaller text on the left for tags, if only for the sake of fitting more things onto the screen. ^^

Will these changes apply to e926 as well?

Kodanis said:
Will these changes apply to e926 as well?

I believe they will, as they're swapping the whole site over, I can't see them running two different web servers for the different versions.

Kodanis said:
Will these changes apply to e926 as well?

Yes. It will be the new codebase for both sites.

It would be a cool if you could follow artist and have a "following" tab. So instead of typing in and going to each of your favorite artist. There would just be a tab that would show new post from all your selected artist. It could also show up on your profile as well.

(Feature) WebP thumbnails
In category: Site Bug Reports & Feature Requests

Requested feature overview description.
WebP is a digital image format based on VP8 wich can compress images better than JPEG can. I also propose changing the maximum thumbnail size from 150 pixels in either direction to 160 pixels in either direction in order to match the block size in at least one direction.
Why would it be useful?
Pages will load faster and users with a pay per use connection will pay less.
What part(s) of the site page(s) are affected?
All thumbnails and avatars.

Please don't cross post feature requests here.

We're aware of your request, please don't spam.

NotMeNotYou said:
Please don't cross post feature requests here.

We're aware of your request, please don't spam.

Sorry.

Hello, as I am developing a downloader that sends requests to e621's API, I would like to know if there are any changes that may happen to the API when this leaves beta? I want to make sure that my program is okay as it is right now, or if I need to start developing changes for when this releases.

McSib said:
Hello, as I am developing a downloader that sends requests to e621's API, I would like to know if there are any changes that may happen to the API when this leaves beta? I want to make sure that my program is okay as it is right now, or if I need to start developing changes for when this releases.

As far as I'm aware there's changes to the JSON data returned, XML probably won't be supported, and when updating posts only the changed tags should be returned, such as:
canine -feline

And although not implimented yet, I'm pretty sure the endpoints are planned to be changed to a dedicated /api/ path, rather than appending .json to the URL.

Here's an api page for a post, so you can see the data that's currently returned:
https://beta.e621.net/posts/190.json

Overall it's probably best to wait till the api's more finished to develop for the new/beta site, as things are likely to change a bit.

Pupslut said:
As far as I'm aware there's changes to the JSON data returned, XML probably won't be supported, and when updating posts only the changed tags should be returned, such as:
canine -feline

And although not implimented yet, I'm pretty sure the endpoints are planned to be changed to a dedicated /api/ path, rather than appending .json to the URL.

Here's an api page for a post, so you can see the data that's currently returned:
https://beta.e621.net/posts/190.json

Overall it's probably best to wait till the api's more finished to develop for the new/beta site, as things are likely to change a bit.

Thanks for the reply, from what I can see, I will need to update the urls for the requests I am sending, and then update the objects I use to map the JSON to. That's all I needed to know. I will be working on getting that implemented when this is released fully.

Here's an api page for a post, so you can see the data that's currently returned:
https://beta.e621.net/posts/190.json

Very detailed, nice.

That source field seems slightly broken (most lines have one url, but in one instance there are 2 urls on one line, separated by a space), unless that actually means something special.

savageorange said:
That source field seems slightly broken [..]

Good catch, that was apparently my fault, there were two urls on one line in the sources on that post, so the api was correct with what it was returning.

I apparently just forgot to add a newline when pasting in more sources.

How have I not seen this thread yet?

Cons: No more themes. Bye, bloodlust :(

Pros: Hot key for favoriting, hotkeys for going to the next/previous post from your search, General tags that are only tagged once (i.e. likely typos) have a red number to make them stand out, lots of improvements to adding translation notes. All of these are awesome and much appreciated.

I don't see the point of the new ui look. It's just a more boxy version of the previous with bigger font that looks like it's more scrunched up. It doesn't look better to me.

Although I think the pictures are scaling better, they are no longer being blown up wider than my screen.

Leon_Neon said:
I don't see the point of the new ui look. It's just a more boxy version of the previous with bigger font that looks like it's more scrunched up. It doesn't look better to me.

Although I think the pictures are scaling better, they are no longer being blown up wider than my screen.

It's more that the codebase of the current site is pretty old, and really awkward to maintain, so they've updated to a later version of danbooru and are modifying/fixing it.

Pupslut said:
It's more that the codebase of the current site is pretty old, and really awkward to maintain, so they've updated to a later version of danbooru and are modifying/fixing it.

so the ugly ui is not their fault?

Leon_Neon said:
so the ugly ui is not their fault?

Pretty much, it used to be white before they added the E6 colours, since then it's more been functional changes, bugs and whatnot.

I'm pretty sure the styling will be worked on in the future, but it's a long way off yet.

For anyone that wants to, there's this thread for how you can help with the styling/css:
https://beta.e621.net/forum_topics/3

There's also a "custom css" box under the user settings, so people will be able to have custom themes.

So is this beta UI going to appear on the main website?

Yes it will, but it will be improved further. The styling itself is the least important part currently.

KiraNoot said:
Please be sure to have a quick look at the changelog as well as the changes by design threads on the forum to see a quick overview of things that have changed so far.

Forgive my ignorance, but where do I actually find those? I'm not sure whether those are any of the stickied forum posts or if they exist elsewhere.

ForThePlot said:
Forgive my ignorance, but where do I actually find those? I'm not sure whether those are any of the stickied forum posts or if they exist elsewhere.

They are stickied in the forum on the beta.

Ooh, it's mobile friendly!

Though I'm gonna wait and lower my expectations on this.

Beta UI is VERY ugly. It looks like it is literally regressing back to Web 1.0 graphics.

is everything supposed to be so square, flat and chunky?