o/

\o

@SonictheAnonymousHedgehog if it looks like a bug and smells like a bug, it's a bug.

aka following this "maybe bug" logic, all the bug reports should be tagged support instead. We can't know for sure whether something is a bug or not.

@ShadowWizardIsVaccinatedV3 Or a very well camouflaged tiger.

@Tinkeringbell bug tiger:

Lacks at least two 'legs' to look like a bug :P

@M.A.R. (failure)

@M.A.R. oops! blush

Well this is a secret room, after all..... :D

Anyway, turns out the move of my workplace is complex, we just split, leaving some people in the old place. As part of the move, "kitchen" was re-designed, now it's cleaner than ever! :D

It won't stay so organized for long, lol

I can already see a random empty glass :P

@ShadowWizardIsVaccinatedV3 don't make me link that horrible piece of merchandise here too.

@Tinkeringbell exactly! Over time, it just grows worse... ;)

@SPArcheon do link, please. :)

^ remember everyone: it was @ShadowWizard fault.

my comment is still the same

@ShadowWizardIsVaccinatedV3 It depends on the question phrasing. If it's making a statement that "this is a bug", then the bug tag fits best. On the other hand, this was phrased as a question, "is this a bug or is it intentional?", so the support tag was a better fit.

I generally prioritize the phrasing of the post over the tags, so I can retain the original intent of the author.

@SPArcheon :-)

To summarize: does the question author believe something is a bug, or are they unsure?

@SonictheAnonymousHedgehog most new users (new to meta) just don't know better. But if it's obvious enough something is a bug, I believe we should edit and let the OP know.

@ShadowWizardIsVaccinatedV3 You mean, rephrase it so it's a statement that it's a bug?

@SonictheAnonymousHedgehog if it was originally posted with bug then yes, rephrase the title/post itself. If the other way around, change the tag to bug.

Not always of course, there are support questions, it's case-by-case.

Bug logo becoming big all of a sudden.... well, my common sense yells "bug". :D

I've been called out before for not regarding the original author's intent when editing a post. Generally, especially with newer meta users who don't know what tags to use here, the phrasing they've put a lot of work into is their intent.

@ShadowWizardIsVaccinatedV3 But that might not have been obvious to the author

@SonictheAnonymousHedgehog true in most cases, yeah.

It wasn't quite obvious to me; I thought it was an intentional change that went awry

@SonictheAnonymousHedgehog went awry, that's the bug.

(as in, they meant to change the icon to that URL, but forgot to change a size attribute)

I can only guess, e.g. they tried to make it more pretty on mobile, not noticing the effect on the non-mobile site.

Again, the question was phrased as the author wasn't certain if it was a bug

@SonictheAnonymousHedgehog ok, I see your point of view now thanks for sharing.

And, time for lunch.

And, time for sleep.

@SonictheAnonymousHedgehog Time for coffee

sdc coffee Sonic

@Luuklag brews a cup of Ristretto for @Sonic

@Luuklag won't work.

you have to use the right bait.

!!/time for sleep

@ShadowWizardIsVaccinatedV3 No such command 'time'.

:(

oh. Time. That reminds me I have to bug Rand.

@SPArcheon looks good, send me some ;)

BTW, this is a good time liken another to remind the staff that since they avoided my request for a Twilight hat every single time, they could at least consider adding a Klee one for deleting blasting a question.

@ShadowWizardIsVaccinatedV3 You can try but sometimes they just delete their question, if they feel overwhelmed by a couple of comments and an edit. Their deleting of thier question kicked it out of the reopen queue, now it's up for undelete but is flying below the radar: meta.stackexchange.com/questions/371976/…

@Rob meh, this one won't fit in any site, no point to undelete IMO.

@ShadowWizardIsVaccinatedV3 Music Fans musicfans.meta.stackexchange.com/q/94/7249 or Law, possibly a couple of others.

@Rob grey area on music fans, dunno about Law, but overall, very big risk of question just getting downvotes, closed, and deleted. OP will get hurt anyway.

oh, someone voted an old answer of mine on a WB post

@ShadowWizardIsVaccinatedV3 So, your argument is that their first question is like soupless' first question; with all the downvotes and hurt.

@Rob not really, no.

Hey all! Is this tag excerpt appropriate: meta.stackexchange.com/tags/http/info?

Seems fine to me. Why do ya ask?

"differences between POST and GET requests and HTTP error codes".. sounds as if we can ask technical questions which are relevant on Super User..

Well, right before that it mentions "Questions about how StackExchange handles the HTTP protocol", though I see your point that the current wording could cause confusion.

If you think you could tighten it up, don't be afraid to suggest an edit to it.

Well, I am not much aware of the scope of the tag... so I don't think I would suggest an edit..

sigh Accidentally retracted my reopen vote on this question: meta.stackexchange.com/q/371976/622284

@RandomPerson Hm. I'm not much of an expert either, though that tag only has 30 questions. Have you noticed many off-topic questions being posted lately with that tag?

On this site, that is.

@Spevacus I am not much active on MSE..

Gotcha. No worries.

:)

@Rob Threw the last undelete vote at it, but I made a dumb move and retracted my reopen vote, which probably stopped it from being put in the reopen votes queue again.

@Spevacus Thanks for the undelete. The reopen was tossed out many hours ago, and it's still not reviewable: meta.stackexchange.com/review/reopen/80073 and probably can't be re-entered; but it has three reopens visible on the undeleted question, maybe it will get a couple more .... Thanks.

/o/

@Luuklag Unfortunately when using the report command you need to surround your reason with quotes.

That command would then become sdc report (link) "reason"

Probably not gonna let you do it now as it's already reported. I did leave a comment on the report, though, so don't worry too much 'bout it

qoutes and brackets arent same thing

"()"

Wohoo, finally someone read my post from this morning xD

@Luuklag Must be cold now

Why can't I put a bounty on this question? I have over 75 rep, and the question is two or more days old meta.stackexchange.com/questions/371918

@cocomac you can't? I tend to forget that the "start a bounty" link is under the comment section (one would expect it somewhere around share/edit).

@Glorfindel Oops. I was looking by the edit button. Found it! Thanks! As you said, yes, it was under the comments.

@Glorfindel You have given away your psychic powers. I will not be fooled.

:)

Except it's sorta not canon

Which makes you . . . Skynet

@Glorfindel Thanks! I put the bounty down

🥄

@SonictheAnonymousHedgehog that's what microwaves are made for

is it safe to put stainless steel in the microwave

I used a knife to scrape out some gunk in mine the other day, I was not burned or electrocuted, so yes. If you turn it on, with the door closed, the same rule applies to any metal; regardless of whether it's stainless or not.

i mean,

This is better than stainless steel:

Too much metal reflects too many microwaves back into the magnetron, burning it out.

@KevinB Another consideration, as mentioned in the comments on that video, is that the microwave uses a different technology than all other microwaves:

From their instruction manual: