Toks said:
At the moment, the limit parameter is only supported on /posts and /notes.
I see, thanks
(amazing flash reply)
Posted under General
This topic has been locked.
I'm gonna put this here because someone might notice it and know of an easier fix than doing a null edit on every one of these posts. I tried the only thing I could think of (changing it to a character then back to a copyright) but that didn't do shit.
Log said:
I'm gonna put this here because someone might notice it and know of an easier fix than doing a null edit on every one of these posts. I tried the only thing I could think of (changing it to a character then back to a copyright) but that didn't do shit.
There are no results for that search, so it seems to be fixed. Maybe the category change took effect a little later than you thought? (Also, using the "Fix" option should work too, at least ideally. Actually that link isn't visible for tags with 1000+ posts...)
2.12.0:
Schrobby said:
Can this be undone? In the light of recent security breaches this seems quite dangerous.
It can't be undone. You do need to input your password to delete your account, but whether that would currently stop anyone is questionable.
Schrobby has a point. That problem is supposed to be fixed but we don't know for sure. Personally, I think that account deletions should be moderated, similar to name changes.
Edit: Well, issue #1651 may solve the problem, but I still think that this option should not be easily accessible. So making it moderated might be a decent idea.
Something seems wrong with pool #2093. I don't think it should be empty, there are no deleted posts in it, either.
Schrobby said:
Something seems wrong with pool #2093. I don't think it should be empty, there are no deleted posts in it, either.
What's the problem? Looking at the pool history, one post was added, removed, re-added, and re-removed, and there were never any other posts in it. Doesn't look buggy to me; just a useless pool.
When I first tried to upload post #1423152 I had a false positive on it being a duplicate: http://danbooru.donmai.us/uploads/64236
It was strange, but I managed to get around it by uploading only the image and not tagging it or linking a source. When it gave me the false positive I had the source input already. I'm not sure if the tagging would have made a difference or not.
Grahf said:
When I first tried to upload post #1423152 I had a false positive on it being a duplicate: http://danbooru.donmai.us/uploads/64236
It was strange, but I managed to get around it by uploading only the image and not tagging it or linking a source. When it gave me the false positive I had the source input already. I'm not sure if the tagging would have made a difference or not.
The first time you tried to upload it, were you letting the site download it from the source, or uploading it from your computer?
Grahf said:
Uploading from my computer.
This is just a shot in the dark, but is there any chance that the image it said it was a duplicate of (post #998510) was on your computer as well, and you mistakenly uploaded that image instead of the one you intended? (I ask because they have the same character in them, so maybe you had them in the same folder or something.)
Toks said:
This is just a shot in the dark, but is there any chance that the image it said it was a duplicate of (post #998510) was on your computer as well, and you mistakenly uploaded that image instead of the one you intended? (I ask because they have the same character in them, so maybe you had them in the same folder or something.)
It's possible, because I do have that image the same folder, like you mentioned. It just seemed unlikely since that's one of the first images in the folder, which I have as ordered by date modified in descending order. Still, I can't discount the idea that maybe something strange happened. If so then I apologize for the trouble.
Well, false positive is technically possible. Danbooru uses md5 hash of the image to find duplicates, and, like any hash, md5 is bound to have collisions at some point. It's just that it's very unlikely, as md5 has 2^128 possible values, and post count on Danbooru isn't even past 2^21. But since it uploaded normally the second time, you probably just selected the wrong source.
Type-kun said:
Well, false positive is technically possible. Danbooru uses md5 hash of the image to find duplicates, and, like any hash, md5 is bound to have collisions at some point.
Happened to me recently. I tried to upload an image from pixiv and got a message from danbooru saying the hash was already taken.