The Smiling Pony 
( ͠° ͟ʖ ͡° )
@Kurozu
Best way is to report the image; mods can handle the image malarkey in the background.
Best way is to report the image; mods can handle the image malarkey in the background.
Posts
Search Results
Uploader Discussion » Found higher res of existing image, but can't upload » Post 3
Kurozu 
How should regular users go about this? Just by making a post about it in a thread, as opposed to reupload/merge?
I’m having a similar issue from the same artist, or was when I tried to upload a few days ago.
Picture in question: >>1569822
Full res from source
@The Smiling Pony
Picture in question: >>1569822
Full res from source
@The Smiling Pony
(original image updated now; is preferred way to handle tumblr_raw shenanigans)
How should regular users go about this? Just by making a post about it in a thread, as opposed to reupload/merge?
Uploader Discussion » Found higher res of existing image, but can't upload » Post 1
The Smiling Pony
( ͠° ͟ʖ ͡° )
Unsure what was going on; an outright block like that only happens if the image hash is identical, so at some point we either had the large image and it was replaced (can’t find a report to explain that), or Tumblr did something weird.
(original image updated now; is preferred way to handle tumblr_raw shenanigans)
(original image updated now; is preferred way to handle tumblr_raw shenanigans)
Uploader Discussion » Found higher res of existing image, but can't upload » Topic Opener
Seiken
Picture in question is >>1572678
Source higher res: https://kuroran.tumblr.com/post/166907468602
I get there are lots of optimization stuff going on in the background to keep everything smooth, though a simple resolution comparison would fix the issue, which shouldn’t be that taxing in addition to the match-finding that is already going on.
So pretty much the title, i get following error:
This image has been uploaded before, sorry!
Picture in question is >>1572678
Source higher res: https://kuroran.tumblr.com/post/166907468602
I get there are lots of optimization stuff going on in the background to keep everything smooth, though a simple resolution comparison would fix the issue, which shouldn’t be that taxing in addition to the match-finding that is already going on.
Showing results 1 - 5 of 5 total
Default search
If you do not specify a field to search over, the search engine will search for posts with a body that is similar to the query's word stems. For example, posts containing the words winged humanization, wings, and spread wings would all be found by a search for wing, but sewing would not be.
Allowed fields
| Field Selector | Type | Description | Example |
|---|---|---|---|
author | Literal | Matches the author of this post. Anonymous authors will never match this term. | author:Joey |
body | Full Text | Matches the body of this post. This is the default field. | body:test |
created_at | Date/Time Range | Matches the creation time of this post. | created_at:2015 |
id | Numeric Range | Matches the numeric surrogate key for this post. | id:1000000 |
my | Meta | my:posts matches posts you have posted if you are signed in. | my:posts |
subject | Full Text | Matches the title of the topic. | subject:time wasting thread |
topic_id | Literal | Matches the numeric surrogate key for the topic this post belongs to. | topic_id:7000 |
topic_position | Numeric Range | Matches the offset from the beginning of the topic of this post. Positions begin at 0. | topic_position:0 |
updated_at | Date/Time Range | Matches the creation or last edit time of this post. | updated_at.gte:2 weeks ago |
user_id | Literal | Matches posts with the specified user_id. Anonymous users will never match this term. | user_id:211190 |
forum | Literal | Matches the short name for the forum this post belongs to. | forum:meta |