-8

This question already has an answer here:

I'm trying to be a helpful citizen and file a whole bunch of bug reports for the Android app. But the 20-minute limit is getting in my way; really unhelpful for everyone involved. I've got lots of tabs open ready to go...

marked as duplicate by gnat, Danubian Sailor, hims056, Martijn Pieters, psubsee2003 Jan 28 '14 at 12:52

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 12
    Given you can only post once every 20 minutes, you've submitted 2 straight questions that are "bugs" about bug reports. If you have "lots of tabs open ready to go", why did you waste 40 minutes submitting the bugs about bug reports? – psubsee2003 Jan 28 '14 at 10:18
  • @psubsee2003 I didn't waste 40 minutes, I spent them. I assume other people hit the same issues; as I say, I'm trying to be a helpful citizen. – Karu Jan 28 '14 at 10:32
  • It's not a bug though, you are making a feature request to change the behavior of the app. Rate limiting is an intentional feature. The App uses a public API and therefore requires rate limiting to protect the site from someone spamming the site via the API. – psubsee2003 Jan 28 '14 at 10:35
  • One man's bug is another man's feature request. It's not a cool feature that I wish the site had; it's existing behaviour of the site that's contrary to my reasonable expectations/desires as a user. That's a bug, intentional or not. – Karu Jan 28 '14 at 10:47
  • 10
    You and I disagree about what a bug is then. To me bugs are unintentional side effects and not design decisions. – psubsee2003 Jan 28 '14 at 10:48
  • To me bugs are deficiencies, feature requests are improvements. This is something that actively frustrated me during my use of the software - it's something that should get "fixed", not "implemented". – Karu Jan 28 '14 at 11:00
  • 1
    We're just going to have to agree to disagree, but historically, the SE community tends to favor the "unintentional side effects" definition. – psubsee2003 Jan 28 '14 at 11:03
  • 10
    If designer intended X, X happened, you don't like X --> feature request. If designer intended X, Y happened, you don't like Y but might like X --> Bug report. – Richard Tingle Jan 28 '14 at 11:18
  • It's not down to opinion, the term bug has a definition... ask yourself if it's really necessary to post all your feature requests back to back? – OGHaza Jan 28 '14 at 12:13
  • 1
    I can't judge the value of the contributions in the case at hand, but it shouldn't matter, either. People have been actively asked to submit their feedback to the new app on Meta, no? So putting up such an obstacle seems inane. – Pëkka Jan 28 '14 at 12:13
  • Congratulations, you are no longer rate limited. As identified by the Complete Rate Limiting Guide, your recent contributions have been valued enough that you are no longer limited to 1 post every 20 minutes. – psubsee2003 Jan 28 '14 at 12:50
4

This seems a fair point in general.

If you ask for feeedback on a new app:

So if there’s something you’d like to see in the app, let us know on Meta under the ‘android-app’ tag

(there's even a link.)

You shouldn't rate limit questions like this for new users. Feature requests and bug reports are prone to coming up in bursts, during the initial use of the app.

  • I agree to a point. It should take time to write a good question (even on meta). IMO, its not just throwing some words in a text box, so the limit does help reduce that for new users who don't know this. The level of this specific users contributions this morning certainly support some level of rate limiting. Maybe 20 minutes is too long, but I think it should be at least 10 min as I think it takes that long to put together a good question with the appropriate back (links, images, steps to reproduce, pros & cons, etc). – psubsee2003 Jan 28 '14 at 12:57
  • @psubsee2003 I agree with you for Meta's normal day-to-day operations, but if you actively ask the public to contribute their reports on a newly launched product, then you can't have them run into a limit like this. It's like a slap in the face, and comes across as arrogant beyond words. What about people who are in the habit of preparing their contributions elsewhere (like in Word)?... Meta is perfectly capable of handling whatever low-quality content comes in with the instruments at its disposal – Pëkka Jan 28 '14 at 13:00
  • Very true, and maybe the limit should be temporarily suspended only for posts using the android app tag so users can file their bug reports. – psubsee2003 Jan 28 '14 at 13:11

Not the answer you're looking for? Browse other questions tagged .