14

as of writing I have one previous question here on meta, which was a feature-request, it hasn't been well received and thus has downvotes (overall -6).


According to the help page:

Voting is different on meta.

On posts tagged feature-request, voting indicates agreement or disagreement

Considering asking a question just now I see:

warning after one question

Should the note in what's meta about meta stackexchange be further expanded? Right now it reads:

On other Stack Exchange sites, if you have an account on the main site, you have an account on its meta site. On Meta Stack Exchange, everyone must create a separate account.

Votes on Meta Stack Exchange directly affect your reputation on Meta Stack Exchange only; they do not affect your reputation on any other Stack Exchange site. Badges on Meta Stack Exchange are also separate from badges on any other site.

It gives no warning that you may find yourself in my current scenario (it's perfectly understandable, given that MSE is separate).

Or should the post-ban thresholds be adjusted on this meta site?

13

The threshold here is significantly higher. The current implementation is only likely to stop:

  • Those that repeatedly post duplicate, ill-researched, unfounded or extremely bizarre yet serious attempts at discussions, feature requests or support cases
  • Those here purely for creative lulz, well, most of the time

If you are blocked and you firmly believe that you don't fall into either category, or have fallen into the first and are serious about adjusting the way that you interact with this community, you can contact us and we can have a look. If you've got a whopper of a lead balloon or two holding you back from participating positively, we're generally going to be inclined to help you.

If this becomes a pattern for you, or if we couldn't hope to get you out of a block even with a crane, then this isn't the best place for you to participate - not everyone is well-suited to argue on capital hill, and you shouldn't feel bad about that.

We do not have automatic question blocks enabled on any other meta site.

You should not have seen the warning that you did - you're not in any danger of being blocked. What happened was, the setting for where the prompt kicks in was still at the level that it would be on Stack Overflow, even though the threshold here is much higher. I've adjusted it so that folks will see it only if they're approaching the higher threshold, which is quite difficult to do, but it'll kick in slightly sooner (by way of comparison) since voting here is quite, well, unrestrained :)

  • 6
    Since I know someone is likely to ask, the block threshold here is approximately six times higher than it is on Stack Overflow. It's excruciatingly hard to hit for someone that is here for the right reasons and actually learns from previous mistakes. – Tim Post May 24 '14 at 7:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .
https://meta.stackexchange.com/questions/232104/should-the-post-ban-threshold-be-adjusted-on-mse
meta.stackexchange.com
crawl=CC-MAIN-2019-30
128349
application/http; msgtype=response
sha1:OGPHJETQUONNA63WTXLNDEN7OYO42GK4
<urn:uuid:15671518-0cf8-471d-8b7e-12415f82d6bc>
2019-07-19T10:39:10Z
151.101.129.69
text/html
sha1:KZ3G6HRP73FSJNFRNJKKPS5GZOKUZI7E
<urn:uuid:2fae5628-3865-42a2-89d1-20136595e584>
https://meta.stackexchange.com/questions/232104/should-the-post-ban-threshold-be-adjusted-on-mse
response
<urn:uuid:c83d7acf-20b7-4ada-b20b-a9a1104d13c4>
isPartOf: CC-MAIN-2019-30
publisher: Common Crawl
description: Wide crawl of the web for July 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-95-236-185.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/