Danbooru 2 Issues Topic

they can downvote my comments all they want...but I don't see why it has to be hidden from everyone else simply becouse some troll downvoted it...next to no other site has this systum and they're just fine...its irritating to see my comments get hidden from everyone else just becouse a few trolls decided to downvote my comments simply becouse they can...its something that a troll can easily take advantage of...therefore I believe its a huge problem and so therefore I believe it should be removed.

evazion said:

Are you hitting the enter key in the tag edit box more than once? That's the only way I can reproduce a double upload.

Nope, I only hit once and sometimes I manually clicked "Submit" button.

evazion said:

Where do you see this error? Sometimes I see errors inside the fetch source data box, but that only affects fetching the translated tags, not the actual upload.

It happens in the middle of uploading process, everytime after I clicked "Submit"/ Enter button.

My internet connection is fine, btw.

I think ugoiras are broken

this one for example

edit: I discovered that they do not work from safebooru, from danbooru it's fine

shujito said:

I think ugoiras are broken

this one for example

edit: I discovered that they do not work from safebooru, from danbooru it's fine

Indeed. @albert, judging by network inspector ugoira_player.js is loaded separately from application.js and returns 404 on safebooru, that's the reason. Why isn't it merged into application.js, I wonder...

Just blazing through my usual tag script edits, in this case adding greyscale to the proper images in a multi-tag search based around monochrome and specifically removing simple_background from posts with transparent_background and now any tag script edit I try is simply returning "There was an error updating post #". Did I actually manage to go so fast as to flood it out or did something break?

OOZ662 said:

Just blazing through my usual tag script edits, in this case adding greyscale to the proper images in a multi-tag search based around monochrome and specifically removing simple_background from posts with transparent_background and now any tag script edit I try is simply returning "There was an error updating post #". Did I actually manage to go so fast as to flood it out or did something break?

Have you generated an API key for your profile? There was a problem with this a few months ago that involved the site defaulting to an incorrect edit rate limit if the user didn't have a key, and I don't know if that got fixed yet

I have not. Interesting.

fossilnix said:

Have you generated an API key for your profile? There was a problem with this a few months ago that involved the site defaulting to an incorrect edit rate limit if the user didn't have a key, and I don't know if that got fixed yet

To tell the truth...
API limits have been unlimited in both reads and writes for all account levels for the last few months... well, not really unlimited, but they are no longer be counted correctly, so they might as well be unlimited. See issue #2693 for more information.
So that's probably not your issue...

Is the Saved Searches function bugging for someone as well?

"undefined method `check_availability' for #<SavedSearchesController:0x007f547a3a1cd8>"

Yes, I'm getting the same error...

Looks like there were two recent commits to the "Saved Searches" controller that are most likely causing the issue.

https://github.com/r888888888/danbooru/commits/master/app/controllers/saved_searches_controller.rb

Edit:

It's an error with the function call not being the same name as the function definition.

check_availability (Line 3)
check_availabililty (Line 51)

Created issue #2795.

Recent changes:

• Possible fix for Sacriven's double uploading issue.
• Fixed the issue with the preview image on the upload page sometimes displaying at full size and not being resizeable (IIRC was mentioned a few months back).
• Fixed blacklisted video with sound posts from autoplaying.
• Fixed safebooru ugoiras.
• Fixed saved searches.
• The text in the appeal dialog box is now taken from help:appeal notice.
• API keys are now on a separate password-protected page instead of in your profile. You can also change your API key.

evazion said:

Recent changes:

• Possible fix for Sacriven's double uploading issue.
• Fixed the issue with the preview image on the upload page sometimes displaying at full size and not being resizeable (IIRC was mentioned a few months back).
• Fixed blacklisted video with sound posts from autoplaying.
• Fixed safebooru ugoiras.
• Fixed saved searches.
• The text in the appeal dialog box is now taken from help:appeal notice.
• API keys are now on a separate password-protected page instead of in your profile. You can also change your API key.

Hey, thanks a lot. That double-upload thingy now fixed.

I just tried something in post #2576993 since a Moderator posted there something.
And I voted down their comment simply to see if this is possible. And to my surprise, this is possible.

So, now imagine that a moderator wants to stop a discussion in the comments but their comment gets downvoted. Then thee mod's comment will have no impact, since no body is reading hidden comments.

Long stor short: Make comment's from Moderators immune from being downvoted. It is already in place for Admins, so it should be the same for Moderators.

Provence said:

Long stor short: Make comment's from Moderators immune from being downvoted. It is already in place for Admins, so it should be the same for Moderators.

Agree... created issue #2799.

Provence said:

Long stor short: Make comment's from Moderators immune from being downvoted. It is already in place for Admins, so it should be the same for Moderators.

Even if the comment holds no deeper meaning, like what Saladofstones said in your example?

To be frank, I don't like that ALL my comments are immune to downvotes now. It's actually somewhat restricting, since making bad jokes or controversial statements feels like abusing my authority.

Is there any way to stop images that aren't huge from resizing themselves to a tiny size in the upload screen (using the bookmarklet)? It's annoying having to have the image you're uploading in a separate window and keep flicking back and forth so you can actually see what tags to add, and I swear it didn't use to do this all the time.

The upload page scales images down to a max of 400px high. It's always done this, except in the past it didn't work for images that took longer than 2 seconds to download due to a bug.

You can try this custom CSS to make images resize to fit your screen:

#c-uploads .ui-wrapper {
    width: auto;
    height: auto;
}

#c-uploads #image {
    width: auto;
    height: auto;
    max-width: 100vw;
    max-height: 100vh;
}

...but it breaks resizing using the resizer handle. After Christmas I'll have more time to look into this.

Oh there's a resizer handle? I didn't even know that existed as I never had reason to use it before. Having it resize to the window is much better though, thanks.

Sacriven said:

Even if the comment holds no deeper meaning, like what Saladofstones said in your example?

It just was an example. Like always.