# ¿Cómo romper el límite de 99k caracteres?

**URL:** <https://meta.discourse.org/t/how-to-break-99k-char-limit/72418>\
**Category:** Support\
**Created:** [19 Octubre, 2017 14:44 UTC](https://meta.discourse.org/t/how-to-break-99k-char-limit/72418 "2017-10-19T14:44:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dylanh724](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dylanh724/32/119642_2.png) [@dylanh724](https://meta.discourse.org/u/dylanh724)\
**Post date:** [20 Octubre, 2017 15:43 UTC](https://meta.discourse.org/t/how-to-break-99k-char-limit/72418/3 "2017-10-20T15:43:30Z")

</div>

> [@codinghorror](#):
>
> I suggest you get users to post enormous logs at a third party service like pastebin. Or clip the logs to just the relevant parts.

How come, though, if it seems like simply a number? 80% of most logs are under the amount specified, but 20% are not, causing issues. It’d be way easier to change 1 number than change our entire streamline of post delivery.

If we’re happy to take the storage hit, what difference does it make? I’m really enjoying our solution – it fits perfectly with our daily use this way. DigitalOcean now offers those hard drive extensions, making storage extremely affordable. Since Discourse is most advertised to use with DO, this would only make sense if people wouldn’t mind bumping up things like this.

Plus, the option to go up without it effecting anyone unless they **want** it to go up (much like any other option with file size limit) always seems like a positive change. Choices = better

---

_[View the full topic](https://meta.discourse.org/t/how-to-break-99k-char-limit/72418)._