When publishing a frontend Joomla article, the ES content plugin generates a stream item. The issue is that the stream item generated contains the entire article HTML itself (encoded of course). Attached to this post is an example of a single stream item from #_social_stream that has a size of 155 Kilobytes. If users generate thousands of articles it's going to take up a lot of space fast. I understand that users will write smaller articles most of the time, however it would be ideal to save hundreds/thousands of megabytes of DB space. One of two methods could solve this for future article stream items:
1. Rather than caching the entire article text, simply cache the display character limit (default is 300 characters). Stream items would continue to display exactly as they do without using a ton of space.
2. Render the text from the article itself. Kunena stream items seem to do this as seen here:
https://dev.peakfun.com/stream/item/103
For the sake of investigating here's a link to the big stream item:
https://dev.peakfun.com/stream/item/102