strikerman said:
grabbing this direct from Chicobo's signature, for some reason the " (on" part gets absored into the URL, and it becomes https://www.furaffinity.net/user/chicobo/%C2%A0%C2%A0(on

Seems they have two non-breaking spaces in between the URL and (. C2 A0 is the UTF-8 byte sequence for U+00A0, which is a non-breaking space character, meant for a space that can't become a line break when a line needs to wrap, which the site's auto-URL parser takes as part of the URL.

The overlay for blacklisted avatars suddenly broke for me in responsive mode. It wasn't like this yesterday, then I had to log in today despite not having logged out.

The thumbnail is visible on top of a larger, tiling 'Blacklisted' square. (warning: slightly creepy pony thing)
Non-blacklisted avatars appear normal. When mobile mode support is disabled (via the link at the bottom of every page) or responsive mode is disabled (in Settings), everything appears as expected. Blacklisted images not appearing as avatars (in pools or the Comments feed, for example) seem to be blocked correctly.

Logging out/in again or changing themes didn't help.

This applies to Firefox and Safari on iOS 15.1. I have no custom CSS or e6-related extensions.

deleuzian_cattery said:
The overlay for blacklisted avatars suddenly broke for me in responsive mode. It wasn't like this yesterday, then I had to log in today despite not having logged out.

The thumbnail is visible on top of a larger, tiling 'Blacklisted' square. (warning: slightly creepy pony thing)
Non-blacklisted avatars appear normal. When mobile mode support is disabled (via the link at the bottom of every page) or responsive mode is disabled (in Settings), everything appears as expected. Blacklisted images not appearing as avatars (in pools or the Comments feed, for example) seem to be blocked correctly.

Logging out/in again or changing themes didn't help.

This applies to Firefox and Safari on iOS 15.1. I have no custom CSS or e6-related extensions.

Noted. There was a change to blacklisting. I will make a fix for this problem.

EDIT: Earlopain beat me to making the fix. Fix deployed.

kiranoot said:
Noted. There was a change to blacklisting. I will make a fix for this problem.

EDIT: Earlopain beat me to making the fix. Fix deployed.

Thank you both!

kiranoot said:
Noted. There was a change to blacklisting. I will make a fix for this problem.

EDIT: Earlopain beat me to making the fix. Fix deployed.

Only (1) spot this fix has not functioned as planned: the "Popular" post tab now shows all posts that my blacklist filters in the annoying little "Blacklisted" overlay box; all other "Posts" pages, as well as the "Hot" tab are fine (I have a fairly extensive list :3 ) Just a little bug, y'all rock!

sharp_coyote said:
Just a little bug, y'all rock!

Thanks!

I'm aware, the popular page probably has css that overwrites something necessary for the hiding to work correctly, it's special that way. At least the posts aren't visible instead of being shown like for the other bug. I'll fix it sometime and wait for Kira to push out the fix.

Would it be considered a bug that blacklisted tags appear at the top of the sidebar when I'm viewing a submission, but the tags are totally unrelated to the submission and instead refer to the icon of a user in the comments under that submission?
While I appreciate being able to toggle my blacklist on and off from the sidebar even when it's the icon of a user that's triggering it, it was *extremely* confusing to have the blocked tags showing up in the sidebar since that's usually reserved for tags applying to the image I actually came by to view.
This also happens when there is a parent or child post that has blacklisted tags on it but the image currently being viewed does not.
It's entirely possible this is an unintended effect caused by my ancient browser (Chrome 49 on WinXP) but since I finally realized what was causing this, I thought you should be aware.
Thank you for your time and the efforts you make to improve the site!

I did actually consider it a bug that it wasn't counted, since you would have no way of toggling your blacklist for user avatars when the post itself was not blacklisted, but also other things like posts embedded in comments, wiki pages or the comment index without finding another page where it offers you to disable your blacklist. I though about just having the toggle visible without incrementing the counters but I that would have been just as confusing, if not more.

_{Sidenode: Please, update your OS and browser if you are able to.}

earlopain said:
I did actually consider it a bug that it wasn't counted, since you would have no way of toggling your blacklist for user avatars when the post itself was not blacklisted, but also other things like posts embedded in comments, wiki pages or the comment index without finding another page where it offers you to disable your blacklist. I though about just having the toggle visible without incrementing the counters but I that would have been just as confusing, if not more.

The old version of the site had a setting to never apply the blacklist to user avatars, but it disappeared with the upgrade. Is there any chance of getting this back? It is both a feature I would like to actually use, and would conveniently solve the persistent annoyance of blacklist entries on post pages which have nothing to do with the actual post or any of its relatives.

earlopain said:
Thanks!

I'm aware, the popular page probably has css that overwrites something necessary for the hiding to work correctly, it's special that way. At least the posts aren't visible instead of being shown like for the other bug. I'll fix it sometime and wait for Kira to push out the fix.

Just an addition: same thing happens on other peeps' favorites page, also

Thanks for the reply, y'all rock just a tad more, now!

EDIT:

@bitWolfy just posted this CSS addon fix in a topic for the same concern:

#c-explore-posts #a-popular article.blacklisted { display: none; }

https://e621.net/forum_topics/31798

Huh, another one. I made it so you need to explicitly add pages where the blacklist thumbnails are supposed to be hidden and somehow forgot that there are other pages apart from the post index where that is supposed to happen. Let's see if I finally got all of them. If not keep reporting and I'll add them back. Mind you, the changes are not deployed yet but that'll happen eventually.

Tickets are excluded from the blacklist, it was that way even before the change.

Not sure if this is a bug or known limitation, but the Post Changes page stops showing the user of changes made about 13 years ago. 123:5 shows a change made by Shiitake 13 years ago, while 124:4 and later just says a change was made 13 years ago. post #124 and post #3082 also have changes where the name stops showing around 13 years ago. Also, with post #123, it shows the first set of changes being made 13 years ago, but the post's Posted date says "almost 15 years ago", maybe the missing names are due to those changes made 14+ years ago and the page getting a bad user/date to show?

millcore said:
Post the bugs you've found here. Please be as specific and as constructive as possible; the more info about the issue you include the easier it will be for us to fix it.

Other forums you can check:
https://e621.net/forum_topics/25717 - List of changes that are NOT bugs
https://e621.net/forum_topics/25748 - Quick FAQ/Q&A thread
https://e621.net/forum_topics/25718 - For documentation problems
https://e621.net/forum_topics/25716 - The theme/aesthetic issues (please read the main post before using)

If you find other bugs floating around in the forum you can post a link to those forums here so they don't get lost.
If you already made another thread for a bug then please go edit [Bug] at the start of the title so it's easy to spot.

Why am I suddenly getting the desktop version of e621 on my mobile phone? I have a samsung s9 and I'm using DuckDuckGo for my browser.

earlopain said:
Thanks!

I'm aware, the popular page probably has css that overwrites something necessary for the hiding to work correctly, it's special that way. At least the posts aren't visible instead of being shown like for the other bug. I'll fix it sometime and wait for Kira to push out the fix.

Er, now posts in pools are doing the thing I originally described. Everywhere else seems to be OK.

Oh well, this is becoming kind of awkward for me. I fixed it adding !important to the rules, it kept getting overwritten from other places. I probably should have done it like this from the beginning. It's not live yet, pending deploy.

earlopain said:
I did actually consider it a bug that it wasn't counted, since you would have no way of toggling your blacklist for user avatars when the post itself was not blacklisted, but also other things like posts embedded in comments, wiki pages or the comment index without finding another page where it offers you to disable your blacklist. I though about just having the toggle visible without incrementing the counters but I that would have been just as confusing, if not more.

_{Sidenode: Please, update your OS and browser if you are able to.}

I don't know about it being more confusing to have an always-available toggle sans the counters, it sounds pretty convenient!
Granted, leaving the counters still implemented apart from such a toggle would be best, perhaps putting the toggle someplace else.

_{Oh yes, I hope to get around to it some time next year, circumstances/finances permitting. I'm pretty tired of having half the internet incompatible with my browser in some fashion! Gonna move to linux probably. Does 'sub' stack? Edit- It does! XD}

I can't see most of the flags that I have made in the flags section of my profile.

Some of my blacklists don't seem to be working.

Anything violence/death/vore/specific_author related I'd rather not see.
Any idea how to fix the blacklists?

Trying to use the date syntax but the majority of the functions are broken. If I try to search in date:2013 then it just rerouts back to the latest posts. The only function that I know of that works with date: is doing a specific date like 2019-12-26. Trying to search for a range doesn't work.

toranimage said:
Trying to use the date syntax but the majority of the functions are broken. If I try to search in date:2013 then it just rerouts back to the latest posts. The only function that I know of that works with date: is doing a specific date like 2019-12-26. Trying to search for a range doesn't work.

Try date:2013-01-01..2013-12-31.
The date:<year> format is not in the specification

praisetheroyalplot said:
Some of my blacklists don't seem to be working.

Anything violence/death/vore/specific_author related I'd rather not see.
Any idea how to fix the blacklists?

1. Is the blacklist on? Check the "Blacklisted" section in the sidebar - if the tag is crossed out, it will not be filtered out: https://i.imgur.com/ZP5zgul.png
Click on it to re-enable it, or click on "Re-enable all" to turn all of the filters back on. On mobile, that section would be near the bottom of the page, under all the posts.

2. Make sure that your blacklist is formatted correctly. Most users' blacklists would have every tag on its own line. Having more than one tag on a line means that in order to be filtered out, the post would have to match all of them: https://i.imgur.com/tbd30PS.png

More information is available here: https://e621.net/help/blacklist

For filtering out most content related to violence, death, or vore, your blacklist should include the following tags (on separate lines): snuff, death, dying, imminent_death, violence, gore, vore, imminent_vore, etc.

kyiiel said:
I can't see most of the flags that I have made in the flags section of my profile.

I only see 2 flags that you made. Both of them invalid.
Can you provide another example of a flag you made that does not show up in that list?

bitwolfy said:
I only see 2 flags that you made. Both of them invalid.
Can you provide another example of a flag you made that does not show up in that list?

Pretty much all flags made in December 1 2018, and Dec 23 2018 that had the reason "Contains real-life pornography". Mostly on December 16th and 17th. IIRC it was over 20, before I added posts to a pool, and just opened a ticket on the pool, so staff could review (I did this once I was finished flagging everything that was confident was going to get deleted, and used the pool for content I wasn't sure of). I was able to see the flags on my profile before the site moved codebases. It's been broken for a while, not that it really matters though.

This link is only present on https://e621.net/users/home, but re621 also adds this to your profile page https://e621.net/users/370094. bitWolfy already released an update to the script, fixing the issue [1]. This was introduced in yesterdays update and also briefly broke the the vanilla link.

I was unable to send a comment on topic #32048, because CloudFlare or e621 was blocking me from sending it. The "Preview" to see the comment with formatting wasn't working either, the error was "Unable to fetch DText preview.". I tried to remove half of the text and I could finally send it, then I fiddled with the other half of my text a little bit and found that what was blocking me from sending it was typing "comment #5223238" which seems to work now. But it still isn't working in the original text.

sieghelm_lockayer said:
I was unable to send a comment on topic #32048, because CloudFlare or e621 was blocking me from sending it. The "Preview" to see the comment with formatting wasn't working either, the error was "Unable to fetch DText preview.". I tried to remove half of the text and I could finally send it, then I fiddled with the other half of my text a little bit and found that what was blocking me from sending it was typing "comment #5223238" which seems to work now. But it still isn't working in the original text.

Got blocked by CloudFlare/e621 again, this time while sending a report and also experiencing not being able to preview the text with the same error. Tried troubleshooting it and the problem solved when I removed a parathensis symbol, specifically the right parathensis: ) <- This one, not this one -> ( .

[09/01/22|DMY] Edit: Just got blocked AGAIN. For the same thing a left parathensis, even though there are left parenthesis in other parts of my text, this one for some reason was making CloudFlare/e621 to block me.

fav:69011 no longer returns only my favs, but acts like there is no search whatsoever. votedup:69011 still works though, as does fav:FoxPuff

I usually prefer the ID, because the username can be changed.
I'm sure this still worked a couple of days ago, so I think the new update broke it.

Nothing I remember was changed in that regard in the last few months. Searching favorites by id requires and exclamation mark before the numbers, in order to avoid confusion with entirely numeric account names. You would need to search for fav:!69011 instead. votedup works because it doesn't actually matter what you put behind the :, as you always only see your own votes.

Oh! Both of these are good to know. I always used simply the number, but having an indicator for an actual ID does make a lot of sense. Unlike the upvoted link I put on my profile when no one can actually view them. Woops!

earlopain said:
Nothing I remember was changed in that regard in the last few months. Searching favorites by id requires and exclamation mark before the numbers, in order to avoid confusion with entirely numeric account names. You would need to search for fav:!69011 instead. votedup works because it doesn't actually matter what you put behind the :, as you always only see your own votes.

That should definitely be added to the User-Based Metatags section on the cheatsheet. Edit: Added.

The tag for the artist gekasso currently reports on the sidebar that it has only 12 posts, but I clicked it and there are actually hundreds. Many of these posts are years old, so it's not that somebody uploaded hundreds all at once and the post count didn't update.

furrykef said:
The tag for the artist gekasso currently reports on the sidebar that it has only 12 posts, but I clicked it and there are actually hundreds. Many of these posts are years old, so it's not that somebody uploaded hundreds all at once and the post count didn't update.

It reports 239 posts for me now.

Custom titles for the tag search syntax don't seem to work properly. It is used as-is for both the search and label/title.

https://e621.net/help/dtext

{{a list of tags|Some Text}}

Result: Some Text

In my list of favorites (Posts > Favorites), a mysterious post shows up (as one of the last few) that I don't remember ever favoriting (unless potentially I did by accident at some point, I guess?). But then when I click on the actual post, it doesn't appear to be favorited at all, so I can't actually remove it from my favorites.

If I try to favorite it just so I can actually un-favorite it, then I get "Error: you have already favorited this post." So basically, a random post somehow wound up in a strange limbo state between favorited and not favorited.

cerv said:
In my list of favorites (Posts > Favorites), a mysterious post shows up (as one of the last few) that I don't remember ever favoriting (unless potentially I did by accident at some point, I guess?). But then when I click on the actual post, it doesn't appear to be favorited at all, so I can't actually remove it from my favorites.

If I try to favorite it just so I can actually un-favorite it, then I get "Error: you have already favorited this post." So basically, a random post somehow wound up in a strange limbo state between favorited and not favorited.

To unfavorite it, follow the steps here: https://e621.net/forum_posts/316652
I'm still not entirely sure how this even happens.

bitwolfy said:
To unfavorite it, follow the steps here: https://e621.net/forum_posts/316652
I'm still not entirely sure how this even happens.

Thanks, didn't notice that was an option, that took care of it. Unfortunately I can't remember any further specifics as far as reproducing it, just that it shouldn't have been there.

bitwolfy said:
To unfavorite it, follow the steps here: https://e621.net/forum_posts/316652
I'm still not entirely sure how this even happens.

I'm not knowledgeable about such things in the slightest, but could it be a glitch in the function that transfers likes and favorites to the surviving version when duplicates are deleted? Assuming that's still a function that is in use.

I would like this CSS to be made official:

#wiki-page-body {margin: 2em 0 2em 0;}

It looks better and less squashed.

I'm repeatedly getting "Error: Unknown error! undefined" when trying to upload a webm - this is despite changing up my methods of obtaining the file - the filesize for all iterations has been between 50-100mb and I don't think it's the tags. I even tried re-rendering it in Vegas and uploading but that also yielded the same result.

TAGS:

2019 artist:studio_venti sheridan_college police_officer police_uniform fetch ambient_fish death catnip drugs beanie scared dachsund cat german_shepherd poodle eating coffee coffee_shop inside outside chase car aquarium toronto protest crowd labrador interrogation ball sneakers skateboarding lake truck van magikarp blobfish muzzle handcuffed arrest better_version_at_source 2d_animation frame_by_frame dabbing

DESCRIPTION:

I've had this error pop up once before, but it resolved itself when I refreshed the page. Refreshing didn't seem to work in this case.

Here's a gdrive link to the file: https://drive.google.com/file/d/16YdpWVi3orXDcuTBF0dige-E0_itp_zq/view?usp=sharing

achtungmaybe said:
I'm repeatedly getting "Error: Unknown error! undefined" when trying to upload a webm - this is despite changing up my methods of obtaining the file - the filesize for all iterations has been between 50-100mb and I don't think it's the tags. I even tried re-rendering it in Vegas and uploading but that also yielded the same result.

Here's a gdrive link to the file: https://drive.google.com/file/d/16YdpWVi3orXDcuTBF0dige-E0_itp_zq/view?usp=sharing

The file you linked is 106 MB, and thus to large to upload. Cloudflare limits uploaded files to 100 MB, which means that the request doesn't even reach the e6 servers and the error handling code doesn't account for that. I'll fix that sometime.
Not sure about your problems with the smaller files. Can you provide me an example?

got this captcha when trying to submit tag changes to /posts/3166916 :
https://i.imgur.com/RXPJ1PY.png
problem is, after clicking the button, my changes weren't saved, neither against the post nor in the post_versions.

i'm sure you'll understand that if for any given edit attempt there's a chance the request will disappear into the void with no way of retrying or recovering the content of the request, a user would feel highly discouraged from attempting to contribute. so i'd consider this a fairly severe defect

using firefox 91.4.1esr on windows

The URLs listed on artist #5620 do not match the history of the page. The page has the author's status as deleted so I cannot fix this manually. As an aside, could you add https://www.deviantart.com/kannoswd and https://kannosart.tumblr.com/ to that URL list?

earlopain said:
The file you linked is 106 MB, and thus to large to upload. Cloudflare limits uploaded files to 100 MB, which means that the request doesn't even reach the e6 servers and the error handling code doesn't account for that. I'll fix that sometime.
Not sure about your problems with the smaller files. Can you provide me an example?

swear I posted a reply to this earlier, guess I forgot to hit submit..

in any case it was just a problem on my end - I didn't actually have a version that was under 100mb, so I guess that was the issue - thanks anyways!

user2003 said:
The URLs listed on artist #5620 do not match the history of the page. The page has the author's status as deleted so I cannot fix this manually. As an aside, could you add https://www.deviantart.com/kannoswd and https://kannosart.tumblr.com/ to that URL list?

I have unlocked the page so you can add the links there yourself. I noticed myself that the artists history can be a bit wrong sometime, nothing that can be done about it now though. The information is just missing. Once you make an edit it'll look a bit better.

achtungmaybe said:
swear I posted a reply to this earlier, guess I forgot to hit submit..

in any case it was just a problem on my end - I didn't actually have a version that was under 100mb, so I guess that was the issue - thanks anyways!

No worries. I actually fixed the error message you were supposed to be getting in cases like these, so it'll be clearer whats actually going on in the future.

Switched mobile browsers to Opera, however, when on normal mode only, the menu bar disappears and I have no way to navigate the site unless I use a private tab or desktop view. I've attempted to meddle with my browser settings to replicate my incognito tabs with no success.
Any help would be greatly appreciated.

Idk if this is the right thread to be asking this but I can't upload an animation from Ekas Portal for some reason. It's saying it's too large, I'm hopeless with this stuff so I don't know what to do.

jez2 said:
Idk if this is the right thread to be asking this but I can't upload an animation from Ekas Portal for some reason. It's saying it's too large, I'm hopeless with this stuff so I don't know what to do.

You could start by scrolling just a teensy bit upwards there and reading the posts explaining what the file size limit is.

Blacklisting doesn't seem to work on android chrome anymore

Blacklisting isn't working on windows Firefox or ios chrome for me either

Is blacklisting working for you guys? Not working for me on windows as well as android both

The blacklist is definitely functioning correctly.
It has been explained time and time again in this very thread.

1. Is the blacklist on? Check the "Blacklisted" section in the sidebar - if the tag is crossed out, it will not be filtered out: https://i.imgur.com/ZP5zgul.png
Click on it to re-enable it, or click on "Re-enable all" to turn all of the filters back on. On mobile, that section would be near the bottom of the page, under all the posts.

2. Make sure that your blacklist is formatted correctly. Most users' blacklists would have every tag on its own line. Having more than one tag on a line means that in order to be filtered out, the post would have to match all of them: https://i.imgur.com/tbd30PS.png

More information is available here: https://e621.net/help/blacklist

bitwolfy said:
The blacklist is definitely functioning correctly.
It has been explained time and time again in this very thread.

1. Is the blacklist on? Check the "Blacklisted" section in the sidebar - if the tag is crossed out, it will not be filtered out: https://i.imgur.com/ZP5zgul.png
Click on it to re-enable it, or click on "Re-enable all" to turn all of the filters back on. On mobile, that section would be near the bottom of the page, under all the posts.

2. Make sure that your blacklist is formatted correctly. Most users' blacklists would have every tag on its own line. Having more than one tag on a line means that in order to be filtered out, the post would have to match all of them: https://i.imgur.com/tbd30PS.png

More information is available here: https://e621.net/help/blacklist

I found the problem, for some reason, my blacklist was all on one line. It used to be formatted correctly, and I’m pretty sure I didn’t change it, so I’m assuming a bug messed up the formatting somehow, without anyone editing it, seems likely since it happened to multiple people at the same time

Getting an issue on Android Google Chrome browser. Any time I click an image instead of taking me to the link it just gives me an error at the top of the screen with no added info. Started happening about two or three days ago, works fine if I have it in desktop mode.

Nvm I somehow managed to put everything in "add to" mode instead of view

Bug: The "Kitsune" tag autocorrects to "Fox".

A Kitsune is a Japanese mythological creature with many tails, typically nine, typically with mystical powers of some variety.

A Fox is a real-world animal found in many places.

Not all Foxes are Fennec Foxes, but is whoever damaged the Kitsune tag going to ruin that tag next by making that species tag autocorrect to Fox?

Bug: Replying with a quote to a blip containing the superscript function appears to break it.

Expected behaviour: Respond to blip as normal.

Actual behaviour: Response is included in quoted text and is also set to the same superscript value as the original blip.

Can this bug be replicated?: Yes.

Bug: The tag for Kitsune is still autocorrecting to Fox. Not implying Fox, but autocorrecting to Fox.

This means people cannot specifically search for Kitsunes without having their search results flooded with Foxes.

a Fox is a real-world animal with one tail.

A Kitsune is a mythological creature with numerous tails.

What, are we just supposed to search "Japanese_Mythology Fox"? That still floods the results with pics of onis and other japanese shit that happens to have random foxes in it.

dragonfox69 said:
Bug: Replying with a quote to a blip containing the superscript function appears to break it.

Expected behaviour: Respond to blip as normal.

Actual behaviour: Response is included in quoted text and is also set to the same superscript value as the original blip.

Can this bug be replicated?: Yes.

You probably mean blip #118303? This doesn't work as expected because the dtext isn't quite right, [sup][sup][sup]I’m starting to love my new job. :v[/sup] is missing two closing tags. Would it instead have been [sup][sup][sup]I’m starting to love my new job. :v[/sup][/sup][/sup] quoting would work fine.

phoenixrisesinbed69 said:
Bug: The tag for Kitsune is still autocorrecting to Fox. Not implying Fox, but autocorrecting to Fox.

This means people cannot specifically search for Kitsunes without having their search results flooded with Foxes.

a Fox is a real-world animal with one tail.

A Kitsune is a mythological creature with numerous tails.

What, are we just supposed to search "Japanese_Mythology Fox"? That still floods the results with pics of onis and other japanese shit that happens to have random foxes in it.

This is not a bug, which people already told you. topic #32888 topic #23085. Use fox_spirit instead.

earlopain said:
You probably mean blip #118303? This doesn't work as expected because the dtext isn't quite right, [sup][sup][sup]I’m starting to love my new job. :v[/sup] is missing two closing tags. Would it instead have been [sup][sup][sup]I’m starting to love my new job. :v[/sup][/sup][/sup] quoting would work fine.

Ahh, cool. Thanks for clearing that up. :)

Since at least 2 months I've noticed the wildcard on the autocomplete isn't working properly. In fact, it doesn't work at all. The * character doesn't affect the results. It's simply ignored.
However, the wildcard still does work as it should on the tag search here.

Example: Let's do a search for *ing_breasts (i.e. tags ending with ing_breasts):

Results of a simple tag search (ordered by count):

Results of the autocomplete:

_{^ the same results are when wildcard is not used}

As you can see, the results of the autocomplete are completely irrelevant.

This was already discussed in the discord some time ago. In short: just autocomplete amounts to about 1/4 of all requests, which is why we had to optimize it somewhat, and removing the ability for wildcard results was one of those steps. This is not a bug and won't be changed back unfortunately.

I cant log in on my phone. I tried multiple browsers, but it only works on my Pc.

earlopain said:
This was already discussed in the discord some time ago. In short: just autocomplete amounts to about 1/4 of all requests, which is why we had to optimize it somewhat, and removing the ability for wildcard results was one of those steps. This is not a bug and won't be changed back unfortunately.

Couldn't you just handle wildcarded and non-wildcarded requests separately? I mean how much of these autocomplete requests are the ones having a wildcard? I guess 99% of them are coming from normally typed tags (it doesn't happen very often when you need to do a wildcard search). In this case, processing the hypothetical 1% of requests differently from the rest shouldn't noticeably affect server performance.

Ratio metatags can't be negated.
1:1 -ratio:1

The upload form allows some preview URLs from pixiv: https://e621.net/forum_topics/33044

The regex matches img-master immediately after pximg.net but as you can see in the example above, the img-master can also be in the later part of the URL.

Description searches in Japanese seem to produce false positives, and it'd probably do this for a few other languages if I bothered to test them.
description:らくがき returns anything with either ら, く, が, or き.

I've been using spectags: to try to narrow my searches to specific species. I test a few numbers above and below to see if I can find any mistags, especially older images. I have noticed some images pop up in results for lower numbers despite having the correct n umber of tags for single species. Tiger is 4, felid, mammal, pantherine, tiger. Despite showing up with spectags:3 search, most of the images here do have 4 tags. I tried deleting and then re-adding the species to see if that "fixes" it, but they still come up under the wrong number. This happened with a few others, since I keep seeing it I figured it might be worth reporting/looking into, curious why these specific pics have 'broken' tags. https://e621.net/posts?tags=tiger+spectags%3A3

Please put order:rank in the cheatsheet with a description of what it does, because I don't know.

lance_armstrong said:
Please put order:rank in the cheatsheet with a description of what it does, because I don't know.

I guess the rank is the number of upvotes the post receives per unit of time (i.e. how fast the post is being upvoted). It only takes posts uploaded in the last 2 days, so it was most likely made specifically for the Hot page and not for general use.

Am I screwing something up, or is the limit parameter not working for either the /pools.json or the /pools/<id>.json endpoint?

https://e621.net/pools/6004.json?limit=10

https://e621.net/pools.json?search[id=6004]&limit=10