Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Given that it's already the most upvoted open Android framework bug, and the Google employee it's assigned to hasn't touched it in almost a year, it seems unlikely that more upvotes will make any difference whatsoever.


In such cases it's always better to just open a new identical bug and hope it gets assigned to someone more interested/competent, and no one notices it's a dupe before that.


Where's the meme of the guy who gets hired on to a tech company, fixes one bug that always annoyed them, then quits immediately


Geohot at Twitter



I agree, but chance favors the tickets that someone internally champions, and there are plenty of Googlers lurking here.


Another +1 comment under it is far more likely to make more people mute the issue if anything. Spamming "google pls fix" just adds to the noise at this point.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: