Matrix events have a size limit; may interact badly with snapshots

[reivilibre]

The title describes it all really, but Matrix events have a 65536 byte size limit (with the server-side attributes included), so this currently places an upper bound on the size of a snapshot (and thus presumably on the size of a document?) as they are encoded as events.

Do you have anything in mind to work around this; e.g. encoding snapshots as (encrypted) media?

[YousefED]

@reivilibre You're right. Have you run into this? The solution I have in mind would be fairly straightforward indeed; to send messages / snapshots that exceed the size limit as attachments (media). Afaik that approach shouldn't have any downsides

[reivilibre]

I haven't ran into this yet, but an application I was looking to make would do quite easily so I thought I'd be smart for a change and check first :-)

[vintprox]

@reivilibre You're right. Have you run into this? The solution I have in mind would be fairly straightforward indeed; to send messages / snapshots that exceed the size limit as attachments (media). Afaik that approach shouldn't have any downsides

Ah, that's one way of surpassing that limit... as an option for size-intensive apps!

[ysds]

I ran into this problem with my own project as well.
Do you have a plan to tackle this problem? I really hope this problem will be solved.

[jchoi2x]

Ran into this issue as well.