(from #acspubsub-22)

From the logs there seems to be single JID that causes the most issue (ba…de@exploit.im) having ~1500 resources. Maybe we could use a queue here with fixed size (configurable) and support only x latest resources (let's say 5-10)? I'm not sure any sane user would need more...

Well, that is a good idea, but I would set this limit higher (at least 20 by default) and make it configurable on the server-side. I can think of a user having many web-based client instances opened in many tabs of the browser which could easily exceed value of 5.