# A case for downvotes and different ordering of replies

**URL:** <https://meta.discourse.org/t/a-case-for-downvotes-and-different-ordering-of-replies/33455>\
**Category:** Feature\
**Created:** [2015 年9 月 18 日 23:30 UTC](https://meta.discourse.org/t/a-case-for-downvotes-and-different-ordering-of-replies/33455 "2015-09-18T23:30:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

作者： ![Fabio\_Machado\_de\_Oli](https://avatars.discourse-cdn.com/v4/letter/f/48db29/32.png) [@Fabio\_Machado\_de\_Oli](https://meta.discourse.org/u/Fabio_Machado_de_Oli)\
发布日期： [2015 年9 月 19 日 01:20 UTC](https://meta.discourse.org/t/a-case-for-downvotes-and-different-ordering-of-replies/33455/3 "2015-09-19T01:20:12Z")

</div>

I have tested Telescope, and it just crashed when I uploaded 84000 rows into it. It also quickly toasted the 5K free limit at embedly. To be fair, I am using far less rows in my current Discourse instance, I droped the apps part of the catalogue. As the IAP aren’t as much annoying with apps than games, and games were just 10% of this list.

On the other hand, most users are using a 360x640 resolution, probably not a supported hardware for browsing Discourse, I should look for something simpler. But we can’t trust analytics on small websites, I probably have more bots than users hitting my server.

---

_[View the full topic](https://meta.discourse.org/t/a-case-for-downvotes-and-different-ordering-of-replies/33455)._